Skip to content
Anomaly

Troubleshooting and Logs

This chapter covers common Launcher and modded-game failures and the files maintainers need when you report a bug.

Where logs and crash reports live

Section titled “Where logs and crash reports live”
  • Game log: GameRoot/games/<version>/Latest.log.
  • Older MelonLoader logs: GameRoot/games/<version>/MelonLoader/Logs/.
  • Crash reports: %APPDATA%/Anomaly/CrashReports/crash-*.json.

On Linux, %APPDATA% is inside the Wine or Proton prefix used by the modded game. Native Linux loadouts use GameRoot/wineprefixes/<loadout>/.

Install and reinstall issues

Section titled “Install and reinstall issues”

The Launcher cannot download files

Section titled “The Launcher cannot download files”

Check your network connection, firewall, VPN, or proxy. The Launcher needs access to Steam for game builds, Anomaly services for install resources and repository mods, and MelonLoader release hosting.

Retry once. If the same file keeps failing, check Anomaly release notes or Discord for service issues.

Local directory is invalid

Section titled “Local directory is invalid”

If you choose Use local directory…, pick the folder that contains SCPSL.exe. Do not select SCPSL_Data/ or a parent Steam library folder.

A new SCP:SL update just shipped

Section titled “A new SCP:SL update just shipped”

Anomaly may need an update before it can support a new game build. Use Game Versions to install a supported build, or wait for a new Anomaly release.

Security software blocked install

Section titled “Security software blocked install”

Some antivirus tools lock newly written executable files while scanning. Close the game, wait for the scan to finish, and retry. If you add exclusions, limit them to your Anomaly GameRoot.

Section titled “Loadout links fail”

The Launcher links Mods/, UserLibs/, and UserData/ into the selected game version at launch time. Link failures usually mean the game is still running, security software is blocking junction creation, or a file is sitting where a folder link should go.

Close the game, retry once, and check the launch-failure details for the exact folder (Mods, UserLibs, or UserData) that failed.

Runtime issues

Section titled “Runtime issues”

The modded game launches then closes

Section titled “The modded game launches then closes”
  1. Open GameRoot/games/<version>/Latest.log.
  2. Check the last error for a mod name, missing dependency, or loader failure.
  3. Disable the most recent mod you installed and try again.
  4. If core Anomaly files are missing or damaged, use Reinstall from Game Versions.

The server disconnects you after joining

Section titled “The server disconnects you after joining”

Common causes:

  • Your Anomaly client and the server are incompatible versions.
  • Your local identity file is missing or invalid.
  • You are trying to join a vanilla server with the modded client.
  • The server rejected the connection before gameplay loaded.

Update the Launcher, launch the modded game once, and confirm the server is Anomaly-enabled.

No @anomaly ID in the Launcher

Section titled “No @anomaly ID in the Launcher”

Launch the modded game once and return to the Launcher. If the ID still does not appear, your user.json may be missing or invalid.

Do not share user.json while troubleshooting. Describe what the Launcher shows instead.

A mod shows missing dependencies

Section titled “A mod shows missing dependencies”

Install the dependencies listed by the mod author or use the repository version if available. See Installing and Managing Mods.

Filing a bug report

Section titled “Filing a bug report”

Good reports include:

  • What you expected and what happened.
  • SCP:SL version and Anomaly Launcher version.
  • Relevant Latest.log excerpt.
  • Crash report JSON if the game crashed.
  • Enabled mods and versions.
  • Reproduction steps.

Report issues at the Anomaly GitHub issue tracker.