Install Anomaly.Server
Anomaly.Server is a LabAPI plugin. Install the server and shared DLLs together, restart the server, and confirm Anomaly appears in the logs.
Prerequisites
Section titled “Prerequisites”- A working LabAPI server. Follow the LabAPI docs if you do not have one yet.
- Write access to the server’s plugin directory.
- Matching Anomaly server files from the same release.
Files you need
Section titled “Files you need”Anomaly.Server ships as two DLLs that must stay together:
Anomaly.Server.dll.Anomaly.Shared.dll.
Grab both from the Anomaly releases page.
Installation
Section titled “Installation”-
Stop the server. Do not hot-swap Anomaly while the server is running.
-
Copy both DLLs into the LabAPI plugins directory. On a stock LabAPI install this is usually
<server>/LabAPI/plugins/. -
Start the server. LabAPI loads Anomaly during startup.
-
Verify the plugin loaded. Look for
[Anomaly]startup lines, including authentication, networking, and asset setup messages.
If startup fails, LabAPI logs the exception and continues without Anomaly support. If vanilla clients can still join, Anomaly did not finish loading.
Asset folder setup
Section titled “Asset folder setup”Asset distribution is optional. To use it, configure AssetDirectory after the first generated config file appears, then restart the server.
See Configuration for the available settings.
EXILED compatibility
Section titled “EXILED compatibility”Anomaly.Server targets LabAPI directly. EXILED plugins can coexist with Anomaly.Server, but test each plugin because wrapper timing and identity access vary by plugin.
If an EXILED plugin needs an Anomaly player ID, use that framework’s documented way to access the underlying user ID.