Configuration

Anomaly.Server’s configuration is intentionally small. Most compatibility behavior is managed by Anomaly and must match the client release.

Config fields

AssetDirectory (string, default "")

Folder on the server that contains files Anomaly can offer to clients.

• Leave it empty to disable asset distribution.
• Use an absolute path for clarity.
• Keep production payloads small enough that first-time joins are still reasonable.
• Restart the server after changing the configured path.

When set, Anomaly scans the folder at startup and sends missing files to clients as they join. Clients cache downloads locally, so returning players usually transfer less.

RequirePassword (boolean, default false)

Requires Anomaly clients to enter the server password before the server accepts the connection.

• Leave it false for open Anomaly servers.
• Set the password with the password <value> server console command instead of editing password files by hand.
• If this is true but no password has been configured, clients are rejected until an operator sets one.

Setting a password with the command enables RequirePassword for new connections immediately and persists the setting when LabAPI can save the config.

PasswordKdfIterations (integer, default 120000)

Advanced setting for the cost used when saving a new password.

• Keep the default unless you have a specific operational reason to change it.
• Existing saved passwords keep the cost they were saved with.
• To apply a new value, change the setting and set the password again with password <value>.

PasswordMaxFailuresPerIp (integer, default 5)

Number of bad password attempts allowed from one IP before Anomaly temporarily blocks more password attempts from that IP.

• Set it to 0 to disable password failure blocking.
• This only applies to password failures, not normal moderation bans.

PasswordBlockSeconds (integer, default 300)

How long the temporary password failure block lasts, in seconds.

• The default is five minutes.
• Set it to 0 to disable password failure blocking.

Transfer and auth internals are managed by Anomaly

Chunk sizes, internal channels, protocol compatibility, and authentication details are not server settings. They are part of the Anomaly release and must match between client and server.

Password command

Use the server console command to manage the Anomaly password:

password <value>
password status
password clear

Command behavior:

• password <value> saves the password and enables RequirePassword for new connections immediately.
• password status reports whether password auth is required and whether a password is configured.
• password clear clears the saved password and disables RequirePassword.
• Empty passwords are rejected.

When password auth is enabled, clients see a password prompt during pre-join authentication. Pressing Esc cancels the join attempt.

Reloading behavior

Anomaly reads most config when the plugin starts. Changing AssetDirectory itself requires a server restart.

File changes inside the already-configured asset folder may be detected while the server is running, but large content changes are still best scheduled for restarts so clients are not forced into heavy mid-round downloads.

Password changes made through the password command apply to new connection attempts immediately. Existing connected players are not kicked when you set or clear the password.

Next

Auth Model and @anomaly IDs.