Launching the Modded Client

Launch vanilla SCP:SL through Steam when you want vanilla servers. Launch an Anomaly loadout through the Anomaly Launcher when you want an Anomaly-enabled server.

Launch flow

Before creating the game process, the Launcher:

1. Resolves the loadout’s selected game version.
2. Uses local/Mods/Anomaly.Client.dll and its companion files when a local development core is present; otherwise resolves a compatible signed official package.
3. Verifies the signature, dependency inventory, and file integrity of an official package before and after extraction.
4. Builds the loadout runtime from its package and local files.
5. Applies the development audit policy, links the runtime into the selected game build, and starts SCPSL.exe.

A missing or invalid official package blocks an official-core launch. A local development core takes precedence over official resolution; see Local and Dev Mods for its required layout.

Mods execute with full process trust

The development audit policy does not require individual hash approvals or automatically quarantine new or rebuilt DLLs. Install only code you trust with the game’s access to files, memory, and the network.

Windows and Linux

Windows uses directory junctions for loadout activation. Native Linux uses the selected loadout’s Wine prefix under GameRoot/wineprefixes/<loadout>/ and launches through the configured Wine/Proton path. A Windows Launcher run under Proton uses that Steam shortcut’s prefix.

The Launcher records active links so a later run can clean up links left by a crash. Do not manually move runtime links while the game is open.

Optional launch arguments

Launch arguments are passed to the selected game process and saved as launcher-owned state. Normal Anomaly use does not require custom arguments.

Continue to Updating and Reinstalling.