IL2CPP Strip Guard

📄 Documentation

IL2CPP bugs are painful because they often show up only after you build.

A script works fine in the Editor. Then you make a WebGL, Android, iOS, VR, or console build, and suddenly a type, method, serializer, save system, or reflection call stops working.

IL2CPP Strip Guard helps you catch those risks early.

It scans your Unity project and shows places where IL2CPP managed stripping, reflection, serialized type names, or AOT generics may break your build.

Use it when your project has:

• Reflection
• Save systems
• Custom serializers
• Runtime type loading
• Command systems
• Dialogue systems
• Event systems
• Dependency injection
• Addressables
• Generic factories

What it helps you do:

• Find risky IL2CPP code before shipping
• See clear Critical, High, Medium, and Low risk findings
• Check if risks are already covered by [Preserve] or link.xml
• Generate a reviewable link.xml suggestion
• Export JSON and Markdown reports
• Run checks in CI so bad builds can fail early
• Ignore known safe findings when needed

This tool does not promise that your whole project is 100% IL2CPP safe.

It gives you a practical safety scan, clear warnings, and useful fixes so you are not debugging blind after a broken build.