Strikes

A strike is a recorded warning: behaviour suspicious enough to log, but not conclusive enough to ban on its own. Enough strikes in one session bans the player automatically — see Strikes for how that works.

This page covers reading the strike list, resolving strikes, and what to do about false positives.

The table

Filter by severity to narrow the list. Search matches names, reasons and Strike IDs.

Reading a strike

Opening a strike shows the detail the detection recorded, such as the speed measured, the distance covered or the model spawned. Use it to judge whether the strike was genuine.

A “Vehicle Boost” strike citing 400 km/h in a hatchback is cheating. One citing a speed slightly above the limit for a supercar usually means the setting is too tight — adjust it on Configuration.

Resolving

Marking a strike resolved records that you have reviewed it and decided no action is needed. It stays on the player’s record and drops out of your unresolved count.

Resolving does not undo anything: it does not lower the risk score or reverse a ban. It only keeps your queue accurate.

Admins can resolve strikes in-game with the resolveStrikes permission.

Patterns to look for

One player, many strikes across sessions. The session counter resets on disconnect, so a player can collect strikes indefinitely without being banned. Sort by player and check the totals — this is what the risk score on Players is for.

Many players, one detection. That is a mis-tuned detection rather than an outbreak of cheating. Loosen the setting.

A burst of high-severity strikes. Usually a cheat menu that detections catch but do not ban outright. Worth reporting on Discord.

False positives

If a detection repeatedly strikes a player it should not, whitelist that player against that detection rather than disabling it for everyone. See Whitelisting.