Requirements & Limitations
System requirements
| Requirement |
Details |
| Unity Editor |
Modern LTS or Unity 6 (Mono backend) |
| Scripting backend |
Mono (Editor default) |
| Platform |
Windows, macOS, Linux |
| Scope |
Play Mode in the Unity Editor |
Not supported
| Item |
Reason |
| IL2CPP player builds |
No Editor patching runtime in builds |
| Standalone / mobile players |
Editor-only tool |
| Editor-folder scripts |
Not attached to GameObjects at runtime |
| Package Cache scripts |
Outside user Assets/ tree |
Types
| Supported |
Not supported |
| Classes |
Interfaces |
| Structs |
Enums (as patch targets) |
| Generic classes |
Attribute types |
| Generic structs |
[Obsolete] types |
Methods
| Supported |
Not supported |
| Instance methods with body |
abstract methods |
| Static methods with body |
extern methods |
| Property accessors with body |
async / await methods |
| Indexer accessors with body |
Methods with ref/out/in parameters |
| Generic methods (call-site) |
Bodyless partial method declarations |
| Operator methods with body |
|
Fields
Hot Patch has limited field support compared to full hot-reload solutions:
| Supported |
Not supported |
| Adding new instance fields during Play Mode |
Editing/deleting existing serialized fields with Inspector sync |
| New fields available inside patched methods |
Re-running field initializers on existing instances |
|
Static field additions |
|
Full Inspector integration for hot-added fields |
New instance fields are stored in a patch-state holder. Existing object state is not migrated.
Overloads
Method patching resolves by name only. Multiple overloads with the same name are ambiguous, use distinct method names in hot-patchable code.