Install the Modded Client

The Anomaly Launcher manages install, reinstall, and launch. You choose a GameRoot, install a compatible game build, and create a loadout. Launcher-owned GameRoot, active-loadout state, and the highest accepted signed official-core version are stored in launcher.json under the Launcher’s OS application-data directory, not in the protected client identity profile. That is %APPDATA%/Anomaly/ on Windows and native application data for a native Linux Launcher.

Quickstart

1. Download the Launcher from the Anomaly Launcher releases page. Use the x64 archive for Windows or Linux.

2. Extract it outside your vanilla SCP:SL directory.

3. Choose a GameRoot. The Launcher stores games/, mods-cache/, loadouts/, and native-Linux wineprefixes/ beneath it.

4. Install a supported game build. The v1 core accepts 14.2.7 and later releases in the 14.2 patch line, but rejects versions earlier than 14.2.7 and versions 14.3.0 or newer.

5. Create or select a loadout. Official Anomaly core tracking is enabled by default.

6. Launch. The Launcher verifies and materializes the signed official core, applies the loadout, then starts the selected game build. For source builds, use the local development workflow.

Official runtime layout

The signed client runtime contains:

Plugins/Anomaly.Bootstrap.dll
Mods/Anomaly.Client.dll
UserLibs/Anomaly.Client.Api.dll
UserLibs/Anomaly.Shared.dll
UserLibs/<verified runtime dependencies>
LICENSE
NOTICE
THIRD_PARTY_DEPENDENCIES.md

The Launcher verifies the signed dependency closure again after extraction. It does not silently continue without Anomaly when an official-core check fails.

GameRoot layout

GameRoot/
+-- games/<gameVersion>/
+-- mods-cache/
+-- loadouts/<name>/
|   +-- loadout.json
|   +-- local/
|   +-- runtime/
+-- wineprefixes/<loadout>/     native Linux launcher

Third-party catalog is not a v1 install source

The public repository tab and anomaly-launcher:// deep links are planned and disabled. Use the signed official core plus trusted manual files in the selected loadout.

Client profile, cache, trust, and crash data are under the selected game’s MelonLoader UserData/Anomaly directory. Existing roaming AppData client data is not imported or used as a fallback. See Runtime Paths and User Data.

Continue to First Launch, Profile, and @anomaly Identity.