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.
Project FAQ position
The LemonLoader FAQ describes Android emulators such as BlueStacks as highly unstable for mod-loader use and says success can vary by environment.
How to interpret that
That is not a compatibility guarantee or a definitive ban. It means emulator use should be treated as experimental and unsupported rather than expected to work.
Reduce variables
- Test a real supported-device environment when possible.
- Do not use emulator success as proof a physical device will behave the same.
- Keep the target app, LemonLoader version, and mod set constant while testing.
Reporting issues
If reporting a problem, state clearly that an emulator is involved because virtualization can affect native libraries, graphics, file paths, and Android behavior.
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.