Install Anomaly.Server

Use the server archive from one Anomaly release. Do not mix Server and Shared DLLs from different builds.

Archive layout

plugins/global/Anomaly.Server.dll
dependencies/global/Anomaly.Shared.dll
dependencies/global/<required runtime dependencies>
LICENSE
NOTICE
THIRD_PARTY_DEPENDENCIES.md

Paths are relative to the LabAPI root. Anomaly.Shared.dll is a dependency, not a LabAPI plugin, and must not be copied beside Anomaly.Server.dll in plugins/global.

Installation

1. Stop the server. Do not replace framework assemblies in a running process.

2. Verify the release archive. Use the published signed manifest, package hash, and dependency inventory.

3. Extract with paths preserved into the LabAPI root so the plugin and dependency land in the directories shown above.

4. Start the server and require the Anomaly.Server enabled; authenticated admission is operational. log entry before accepting players. Treat any initialization, rollback, retained-patch, or admission-closed error as a failed start.

5. Exercise controlled round and process restarts on staging. Anomaly must initialize before facility generation; loading or replacing the core after a map exists is refused. Stop the process before changing core assemblies, then start it again. When testing disable cleanup, confirm unrelated Harmony patches remain present and the captured server runtime state is restored.

Fail closed is expected

If a mandatory Anomaly hook or service fails, modded admission remains blocked. Do not interpret a running LabAPI process as proof that Anomaly is operational.

The optional AssetDirectory is configured separately. Continue to Configuration.