Updating and Reinstalling

SCP:SL updates can require a new Anomaly-compatible build. The Launcher keeps game builds under GameRoot/games/<version>/ and lets each loadout choose the build it should run.

How the Launcher tracks installs

The Launcher tracks two different things:

• Installed game builds under GameRoot/games/<version>/.
• Named loadouts under GameRoot/loadouts/<name>/, each pointing at one game version plus a pinned mod set.

This means you can keep an older SCP:SL build for one server while testing a newer build in a separate loadout.

Changing game versions

Open Game Versions, select a build, and click Install. The Launcher downloads or uses the selected source and applies Anomaly again.

Use this when:

• A server requires a specific SCP:SL build.
• The latest game update is not Anomaly-compatible yet.
• You want to keep a test build beside your normal build.

After installing the build, set your loadout’s game version to the new install. See Loadouts and Game Versions.

Reinstall / Sync

Use Reinstall / Sync when an installed game version is missing files, has damaged patch bytes, or needs to be regenerated.

During repatch, the installer restores GameAssembly.dll, global-metadata.dat, and globalgamemanagers from their existing .bak sidecars before applying patches again. Those .bak files are treated as the vanilla patch source so patch precondition checks run against original bytes, not already-patched bytes.

First-run stays isolated

The installer-only first-run pass loads only Anomaly.FirstRun.dll. It temporarily isolates Mods/, generates Il2Cpp assemblies, and restores your original Mods/ afterward so a reinstall does not accidentally load your active loadout or local dev mods.

Uninstall

Use Uninstall from Game Versions to remove an installed build from GameRoot/games/<version>/. Loadout definitions, cached mod packages, shared identity, and launcher data are separate from that game-version folder.

If you manually delete the whole GameRoot, back up loadouts/ and any local files first.

When install or reinstall fails

Common causes include:

• Network failure while downloading game or install resources.
• A newly released SCP:SL build that Anomaly does not support yet.
• Missing or invalid local SCP:SL source folder.
• Security software locking files in the game-version folder.
• A real file or folder blocking Mods/, UserLibs/, or UserData loadout linking.

Retry once after checking network access and closing the game. If a new SCP:SL update just shipped, wait for an Anomaly release that supports it.

Your identity survives

Your @anomaly identity lives in %APPDATA%/Anomaly/user.json, outside the GameRoot. Normal reinstall flows do not remove it.

Next

Installing and Managing Mods.