Nothing recorded yet.
Active entries and manual offline bans. The rules behind them live under Config → Ban rules.
What happens on which code. Everything here is proven server-side, except THREAD_STALL which is reported by the client.
Which checks run, and how tolerant they are. What happens on a hit is set under Actions.
Compares the position the client reports with the one the server reads from the entity. Catches a cheat feeding the anticheat fake coordinates.
Below 20 m normal sync lag alone would ban people, so that is the hard floor. A cheat that manipulates its whole network sync moves the server value along with it and stays invisible to this check.
Reads player positions server-side for the map view. The client is never asked, so the data cannot be faked. Needs OneSync.
Timing of the handshake and the rotating channel. Raise the grace values before you tighten anything — slow clients must not be dropped here.
A ban covers every trait the player had. Missing traits stay empty and are never checked.
Switched off, a ban runs straight through with no capture and no waiting for one. Screenshots need screenshot-basic running — it is detected at runtime and a ban never fails because it is missing. The banned player is moved to routing bucket base + server id, so nobody else is in there.
Staff the anticheat never enforces against. Detections are still recorded and still show up in the log and the webhook — they are just downgraded to log instead of kicking or banning.
A Discord ID works from the moment the player connects, so it also lets a staff member through an existing ban.
Where detections are mirrored to. Leave the URL empty to switch it off.