The exact configuration file can change between releases. Always use the configuration supplied with your licensed version.
This page explains the main configuration categories without publishing protected thresholds or signatures.
Use during installation, integration work and controlled validation.
Typical purpose:
Recommended starting point for production servers.
Typical purpose:
Use only after the server has been tested thoroughly.
Typical purpose:
Strict mode is not automatically “better.” Poorly tested strict settings can create operational problems or false positives.
Controls access to the panel, staff commands and sensitive actions.
May include console logging, database evidence, Discord webhooks and staff audit records.
Protect webhook URLs and do not publish them.
Controls event firewall behaviour, validation rules and honeypot handling.
Do not share protected event names or detection logic publicly.
Controls monitoring of player-created objects, pedestrians, animals, wagons and other network entities.
Entity protection should distinguish abusive bursts from legitimate ambient or scripted world activity.
Controls observation of abnormal money, item and weapon changes.
These systems may require integration with the server’s framework and custom resources.
Controls detection and reporting of abnormal movement, teleporting or travel patterns.
Legitimate administrative, jail, ferry, housing and mission teleports should be reviewed.
Controls evidence collection and scoring around combat behaviour.
Aim-related evidence should normally be reviewed alongside context rather than treated as automatic proof.
Controls monitoring of expected resources and suspicious resource state changes.
Controls warnings, strikes, containment, kicks, bans or other actions.
Start conservatively and verify that staff understand the response workflow.
Before changing production settings: