You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on May 11, 2026. It is now read-only.
Games now are starting to adapt HybridCLR, as it claims: 'high performance, low memory'. It introduces some AOT changes of Unity into 'AOT + Intrepreter' to aim for 'C# Hot Update Technology'. This HybridCLR is also called as 'hotfix update': HybridCLR
Problems
Currently, GGIL2CPP fails to obtain classes, fields, and methods information directly from the game memory. It also breaks all IL2CPP dumpers, even that executed in runtime, like: Zygisk-Il2CppDumper. Pointing fields / methods with specific offset still works, looks like the changes breaks the 'string' correlation as most dumpers also include function names, etc.
*This issue is reserved as templates once the workaround to this issue is widely adopted.
Background
Games now are starting to adapt HybridCLR, as it claims: 'high performance, low memory'. It introduces some AOT changes of Unity into 'AOT + Intrepreter' to aim for 'C# Hot Update Technology'. This HybridCLR is also called as 'hotfix update': HybridCLR
Problems
Currently, GGIL2CPP fails to obtain classes, fields, and methods information directly from the game memory. It also breaks all IL2CPP dumpers, even that executed in runtime, like: Zygisk-Il2CppDumper. Pointing fields / methods with specific offset still works, looks like the changes breaks the 'string' correlation as most dumpers also include function names, etc.
*This issue is reserved as templates once the workaround to this issue is widely adopted.