Logs and Crash Reports

Anomaly writes logs in the same places players and server operators already expect: the active game-version folder, MelonLoader logs, the server log, and the shared Anomaly crash-report folder.

Log streams

Modded-game log

Path: GameRoot/games/<version>/Latest.log

This is the main client log. It includes MelonLoader output, Anomaly output, and mod output. The Launcher tails this file in its log view.

Older session logs are kept under GameRoot/games/<version>/MelonLoader/Logs/.

Launcher output

The Launcher writes its own diagnostic output to its attached console when one is available. User-facing failures are also shown in the Launcher UI.

Server log

Anomaly server messages appear in the normal LabAPI server log.

Useful prefixes:

[Anomaly] for lifecycle, networking, and asset messages.
[Diag] for detailed auth and role diagnostics.

Crash reports

Path: %APPDATA%/Anomaly/CrashReports/crash-*.json

On Linux, use the Wine or Proton prefix’s mapped %APPDATA% path.

Crash reports are JSON summaries produced by the modded client. They can include:

Report ID and timestamp.
Exception type, message, and stack trace.
Recent game-log entries.
System and graphics information.
Current scene and connection state.
Loaded mods.
Native dump path, if one was produced.

The Launcher shows the most important fields in a crash dialog, but the JSON file remains available on disk.

Filing a bug report

Useful reports include:

What you expected and what happened.
SCP:SL version and Anomaly version.
Relevant Latest.log excerpt, usually 50 to 200 lines around the failure.
Crash report JSON if the game crashed.
Enabled mods and versions.
Reproduction steps.

Do not include:

Contents of user.json.
Native dump files in public channels.
Entire unrelated logs by default.

Open issues at the Anomaly GitHub tracker.

Networking Compatibility.