Compatibility

LemonLoader Compatibility Guide: What Is Actually Documented

A fact-first compatibility page covering IL2CPP, arm64-v8a, and why game-by-game support should not be assumed.

Illustration for LemonLoader Compatibility Guide: What Is Actually Documented

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.

Verified compatibility facts

  • Project focus: Android support.
  • Documented scripting runtime: IL2CPP.
  • Documented Android architecture: arm64-v8a.
  • Wiki base MelonLoader version: 0.6.5.

What is not verified

The wiki does not provide a universal “all games” compatibility list. Its FAQ describes Lemon as unstable and says individual games may or may not work. Therefore this site does not publish made-up compatibility badges.

How to judge a target app

Start by confirming the app uses a supported environment and architecture. Then check project issues and community reports for the exact app/version. Treat anecdotal success as app-specific, not proof of universal support.

Mod compatibility is a separate question

Even when the app itself launches, a PC mod may still fail because of AssetBundle differences or IL2CPP assembly differences. The project wiki calls out both exceptions.

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

  1. Start from a clean app and known backup.
  2. Patch with the current verified installer.
  3. Test the app before adding mods.
  4. Add one mod at a time where practical.
  5. 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.

Primary project references
Main repository ↗ · Releases ↗ · Wiki ↗