Source note: LemonLoader is independent. Project-specific facts below are limited to information published by the LemonLoader repository, releases, or wiki; general troubleshooting advice is identified by context.
The documented runtime
The project wiki lists IL2CPP as the supported Unity scripting runtime. That is a narrower statement than “supports every Unity game.”
Why runtime matching matters
The mod-installation wiki explains that PC-built mods can sometimes work on Lemon when the scripting runtimes match. Runtime alignment is therefore a key compatibility check before testing a mod.
Known exceptions
- Mods using AssetBundles may need Android-built bundles.
- IL2CPP assemblies can differ between platforms, which may cause stripping errors on one platform but not another.
Use the runtime as a filter, not a guarantee
If a target app is not using the documented runtime, compatibility should not be assumed. If it is using IL2CPP, further testing and app-specific evidence are still required.
Compatibility is a stack, not a single yes/no field
At minimum, separate device architecture, Unity scripting runtime, target app build, LemonLoader release, and the individual mod. A match at one layer does not guarantee the next layer. For example, arm64-v8a hardware does not by itself prove that a target game or a PC-built mod will work.
The project FAQ’s unstable-compatibility warning is a reason to prefer exact evidence: the same package name, same app version, same LemonLoader release, and similar device environment. Reports that omit those details are useful leads, but weak guarantees.
How to test responsibly
- Start from a clean app and known backup.
- Patch with the current verified installer.
- Test the app before adding mods.
- Add one mod at a time where practical.
- Capture logs at the first reproducible failure.
Recommended next step
For a clean path through the project, use the verified download page, follow the installation guide, and keep the logging guide available for troubleshooting.