Troubleshooting and Logs
Important paths
Section titled “Important paths”- Game log: GameRoot/games/<version>/Latest.log.
- Older MelonLoader logs: GameRoot/games/<version>/MelonLoader/Logs/.
- Installer logs: the Launcher’s OS application-data
Anomaly/installer_logs/. - Patch audit: the Launcher’s OS application-data
Anomaly/patch_audit.json. - Client crash artifacts:
<MelonLoader UserData>/Anomaly/CrashReports/for the selected game instance. - Launcher trust quarantine: the selected loadout runtime’s UserData/Anomaly/Quarantine/.
Launcher logs/audits retain their own application-data locations. Client profiles and crash artifacts use the selected game’s MelonLoader UserData directory on Windows and Proton; protected identity material is still tied to that game’s Windows user or Wine prefix.
Copy a diagnostic summary
Section titled “Copy a diagnostic summary”Run anomaly.status in the client console, or anomaly.status --copy to copy its summary. It includes versions, connection/readiness state, feature status, and relative diagnostic locations. It excludes identity values, server addresses, and arbitrary mod health details. A persistent connection-failure dialog includes a diagnostic code and suggested next action; capture these with your reproduction steps.
Common failures
Section titled “Common failures”Unsupported game version
Section titled “Unsupported game version”The v1 core accepts 14.2.7 through the remainder of the 14.2 patch line. It rejects versions before 14.2.7 and versions at or after 14.3.0.
Official core verification failed
Section titled “Official core verification failed”A missing file, wrong size or hash, untrusted signing key, invalid signature, dependency mismatch, or incompatible SupportedGameVersion blocks launch. Reinstall or sync from an official release. Do not disable the gate.
Restoring a quarantined DLL
Section titled “Restoring a quarantined DLL”Review its exact path, hash, size, and source before restoring it from the quarantine panel. The development Launcher uses an audit policy: it does not automatically quarantine new DLLs or require another approval after a rebuild.
Identity initialization failed
Section titled “Identity initialization failed”Corrupt JSON, DPAPI decrypt failure, mismatched identity_public, or invalid rotation lineage leaves user.json unchanged and blocks authentication and profile edits. Keep the original and its .bak file for private recovery assistance; never post either publicly.
No @anomaly ID appears in the Launcher
Section titled “No @anomaly ID appears in the Launcher”That is expected. The Launcher shows a non-secret identity_public fingerprint, not a server-local enrollment ID. Connect to the server and run anomaly.whoami in the client console.
Crash privacy
Section titled “Crash privacy”JSON crash reports are written locally and are never uploaded automatically. Retention is bounded to at most 20 artifact sets, 30 days, and 256 MiB total. Native minidumps are disabled by default; setting ANOMALY_ENABLE_MINIDUMPS=1 opts into local capture. A minidump can contain private process memory.
Filing a report
Section titled “Filing a report”Include the game version, core and Launcher versions, relevant log excerpt, enabled mod hashes/versions, and exact reproduction steps. Never include user.json, private signing material, or unreviewed minidumps.
Report issues at the Anomaly GitHub issue tracker.