Logs and Crash Reports

Log streams

Client and MelonLoader: GameRoot/games/<version>/Latest.log and MelonLoader/Logs/.
Launcher installer: the Launcher’s OS application-data Anomaly/installer_logs/.
Patch history: the Launcher’s OS application-data Anomaly/patch_audit.json.
Server: the normal LabAPI server log.

Anomaly uses contextual lifecycle, authentication, networking, and content messages in those logs. Run anomaly.status for a concise summary of versions, connection/readiness, feature states, and relative diagnostic locations, or anomaly.status --copy to copy it. The summary excludes identities, server endpoints, and arbitrary module health details; raw logs still require review before sharing.

Crash artifacts

The client writes crash-*.json under <MelonLoader UserData>/Anomaly/CrashReports/ for the selected game instance. Reports contain a report ID, timestamp, exception and stack information, bounded recent logs, system/runtime details, loaded-mod information, and a redacted connection-state snapshot.

Server endpoints and the local nickname are redacted on a best-effort basis. No diagnostic artifact is uploaded automatically.

Retention

Cleanup keeps an artifact set only while all limits are satisfied:

At most 20 artifact sets.
At most 30 days old.
At most 256 MiB total.

JSON and its matching dump are treated as one set. Cleanup is best effort during failure handling.

Minidumps

Native minidumps are disabled by default. Set ANOMALY_ENABLE_MINIDUMPS=1 before launch only when you intentionally want a local capture. Dumps can contain credentials, chat, server data, private keys, and other process memory even when the JSON report is redacted.

Useful release evidence

For a release defect, preserve source commits, dependency/package hashes, game and loader versions, platform, exact command, and relevant logs. Label build/test evidence separately from fresh Windows, Proton, client, and server runtime evidence.

Continue to Networking Compatibility.