Compatibility

Supported runtime set

Use Client, Client.Api, Server, Shared, Bootstrap, and SDK XML documentation from one matching Anomaly release. Client mods reference Anomaly.Client.Api.dll and Anomaly.Shared.dll. Server companions reference Anomaly.Server.dll and Anomaly.Shared.dll and use the Anomaly.Server.Api namespaces with native LabAPI lifecycle, events, and wrappers.

The managed Anomaly version is 1.0.0. Client and server both require application protocol v5; a different protocol version is rejected during authentication.

Component	Contract
Anomaly core	1.0.0
SCP:SL	14.2.7^
MelonLoader	0.7.2
Architecture	x64
Platforms	Windows and Proton/Wine
Application protocol	v5

Caret semantics

14.2.7^ means greater than or equal to 14.2.7 and lower than 14.3.0. It accepts later releases in the selected 14.2 patch line but not an earlier patch or a new minor line.

Peer Melon mods declare assembly-level Anomaly SupportedGameVersion metadata for Launcher compatibility status. The signed official core is rejected before materialization unless its metadata is present, valid, and compatible. Managed modules declare SupportedGameVersions in their sidecar and are rejected before assembly loading when that declaration is missing, invalid, or incompatible.

Anomaly does not use MelonLoader’s required-game-version attribute for this contract.

Runtime compatibility

Client, Server, Shared, API, Bootstrap, SDK XML, and package inventory must come from one tested release set.
Protocol v5 requires a matching client and server.
A local/Mods/Anomaly.Client.dll selects the local development core before official package resolution. Stage its matching API, Shared, Bootstrap, and dependencies together.
Official-package launches verify the trusted signing key, version, dependency inventory, and file integrity. An unknown signing key, downgrade, missing dependency, or modified artifact blocks that launch.
The development Launcher audits local DLLs without automatic quarantine or individual hash approvals. Managed-module metadata and official-package verification still apply.
Client profiles live in the selected game’s MelonLoader UserData/Anomaly directory. Their protected identity remains bound to the Windows user or Wine prefix used by that game.
Public remote password mode is unavailable.
Facility generation uses one immutable authenticated snapshot. Use FacilityLayout during LabAPI MapGenerating or edit selected rooms during Anomaly MapEvents.LayoutFinalizing. The authenticated final snapshot governs initial and late-joining clients; failed generation closes admission until the next successful generation or restart.

Testing your mod

Test your mod with the matching client and server on each platform you support. Check startup and shutdown, disconnect and reconnect, round restart, and the features your mod uses. For custom content, include acceptance, decline, late join, rendering, and item use.

Return to API and Namespace Index.