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.
File log locations
The LemonLoader wiki documents logs under /sdcard/MelonLoader/<package name>/MelonLoader/Logs. It also documents the latest-start log at /sdcard/MelonLoader/<package name>/MelonLoader/Latest.log.
When logs help
- Repeated first-launch crashes.
- A mod loads on one platform but not another.
- Stripping or IL2CPP-related errors.
- Installer says patched but runtime behavior fails.
Realtime logging
The wiki also provides ADB logcat filters for normal and verbose realtime logging. Use those exact commands from the wiki when you need live diagnostics rather than copying an unrelated Android logcat recipe.
Share carefully
Before posting logs publicly, review them for usernames, paths, device identifiers, tokens, or other information you do not want to disclose.
Use evidence before reinstalling
A good troubleshooting sequence is: reproduce once, capture the relevant message/log, reduce optional mods, verify release and environment, then change one thing. Reinstalling immediately can remove useful logs and can make the next failure look different without explaining why.
Classify the failure stage
- Installer cannot see device/app: focus on ADB authorization, device selection, detection, or package structure.
- Patch fails: focus on installer output, storage, split APK handling, and current release fixes.
- Patch succeeds but app fails: focus on first-run permissions, runtime compatibility, and LemonLoader logs.
- App works until a mod is added: focus on that mod, its runtime assumptions, AssetBundles, and platform differences.
This classification prevents unrelated fixes from being applied to the wrong layer.
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.