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.
What the wiki says
A mod built for the PC version of a game can sometimes work on Lemon when the scripting runtimes match. The wiki gives BONELAB as an example, but that example should not be generalized to every game.
Two explicit exceptions
- AssetBundles may need to be compiled for Android.
- IL2CPP assemblies may differ enough to produce stripping errors on one platform and not another.
Practical test sequence
- Confirm the game uses IL2CPP on both platforms.
- Verify the mod’s documented platform support.
- Test without optional AssetBundles first when applicable.
- Read LemonLoader logs if loading fails.
Do not promise portability
“Same game” is not enough evidence. Treat each mod build as platform-specific unless the mod author or successful technical testing establishes compatibility.
Keep loader problems and mod problems separate
Once the patched app launches, introduce mods gradually. The documented Mods and Plugins folders tell you where files belong, but they do not guarantee that every DLL is suitable for Android or for the exact game build.
Record mod provenance
Keep the mod name, version, source, and any platform notes with your setup. A file copied from an old PC mod pack can fail for reasons unrelated to LemonLoader itself. When a failure appears immediately after adding one mod, remove that mod and retest before rebuilding the entire loader installation.
For configuration changes, preserve the previous preferences file so you can distinguish a bad setting from a loader or mod binary problem.
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.