Known Limitations for Unity

While Shield provides comprehensive protection for Unity games, there are some limitations to be aware of.

Compilation Mode Limitations

IL2CPP Limitations

When using IL2CPP compilation:

• Invalid Code protection is not compatible
• Some reflection-based protections may not work as expected
• Virtualization requires thorough testing
• Certain anti-debugging techniques may be limited

Mono Limitations

When using Mono compilation:

• Some protections may have higher performance impact
• Memory protection capabilities may be limited
• Anti-tampering measures may be less effective

Protection-Specific Limitations

Control Flow Protection

• Should be applied selectively to avoid performance impact
• May affect debugging capabilities
• Can impact hot-reloading in the Unity Editor
• May interfere with certain Unity features

Virtualization

• Requires thorough testing with IL2CPP
• May impact startup time
• Can affect debugging capabilities
• May interfere with certain Unity features

Constants Encryption

• May impact hot-reloading in the Unity Editor
• Can affect debugging capabilities
• May interfere with certain Unity features

Platform-Specific Limitations

Mobile Platforms

• Performance impact may be more noticeable
• Memory protection capabilities may be limited
• Anti-debugging techniques may be less effective
• Battery impact should be considered

Desktop Platforms

• Anti-tampering measures may be less effective
• Memory protection may be limited by OS restrictions
• Anti-debugging techniques may be less effective

Best Practices for Working with Limitations

1. Test thoroughly on all target platforms
2. Monitor performance impact
3. Use selective protection for critical code
4. Verify compatibility with your Unity version
5. Consider platform-specific limitations

For protection recommendations, see Recommended Protections.