Detection flags

What each flag means

Flags are safety checks that run after the model scores a player. When one applies, the detection keeps the model's verdict but never counts toward a ban.

How flags work

The plugin records each fight a player takes part in as a sequence: combat with one weapon that ends after three seconds without shooting or when the player switches weapons. Sequences only count if they had a kill or enough shots, hits and damage. Every five sequences are scored together by the model.

When the model's verdict is Cheating, ChrononLabs runs a few checks on the same batch of sequences. Each check that matches adds a flag. A flagged detection:

keeps the Cheating label and its confidence, marked Not counted toward bans;
never triggers a ban, a violation or a notification;
still goes into the review queue, so you can look at it and ban by hand if the replay shows cheating;
lists every flag on its detection page with the values that were measured.

Legitimate detections never get flags. More than one flag can apply at once: low damage and zero accuracy often appear together.

Flags not recorded

Detections created before flags were stored show “Flags not recorded”. That does not mean a check failed, only that the result was not saved at the time.

Auto-legitimate list

Flag codeauto_legitimate
When it appliesThe verdict is Cheating and the player's SteamID is on this server's auto-legitimate list.
Values shown on the detectionNo extra values.

What it means

The player was deliberately exempted on this server. The model still scored them, and the result is kept so you can see it, but nothing is enforced against them.

Common causes

Staff, testers or content creators whose play style is unusual on purpose, such as admins testing weapons.
A player who was cleared after an appeal or a confirmed false positive.
A player added while investigating a problem and never removed.

What to do

Nothing, if the player belongs on the list. The list holds up to 128 players per server and is managed by ChrononLabs staff: contact us to add or remove someone. If a listed player keeps getting high-confidence Cheating verdicts, open the replay and check that the exemption is still deserved.

Low damage per second

Flag codelow_damage_per_second
When it appliesThe verdict is Cheating and the player's average damage per second across the scored sequences is 5 or lower.
Values shown on the detectionAverage damage per second, and the threshold of 5.

What it means

Damage per second is the damage a player dealt in a sequence divided by how long it lasted. Aim assistance almost always shows up as damage, so a Cheating verdict with almost none is far more likely a false positive than a cheater.

Common causes

Low-damage weapons or non-lethal tools such as stun guns, tasers or paintball guns.
Gamemode rules that reduce or block damage: damage multipliers, armor, god mode, safe zones or disabled friendly fire.
Long fights with few hits, such as spraying at long range or suppressive fire.
A custom weapon base or addon that deals damage outside the normal damage event, so the plugin sees less damage than was actually done.

What to do

Usually nothing. If many detections on your server carry this flag, check whether your weapon base or gamemode changes how damage is applied, and run the self-diagnostics to confirm the damage event reaches the anti-cheat.

Zero accuracy

Flag codezero_accuracy
When it appliesThe verdict is Cheating and the player's average accuracy across the scored sequences is exactly 0.
Values shown on the detectionAverage accuracy.

What it means

Accuracy is hits divided by shots fired. Zero means no recorded shot hit anything. A cheat exists to hit, so a Cheating verdict with no hits points to missing or unusual data rather than a cheater.

Common causes

Weapons that do not fire bullets: melee, projectiles such as crossbows, rockets and grenades, thrown props or vehicles.
A custom weapon base that does not report its shots through the standard bullet event, so hits are never registered.
A player firing at nothing in particular, such as testing a weapon or shooting at walls.

What to do

Usually nothing. If it shows up often, a weapon pack on your server is probably not reporting shots. Run the self-diagnostics and check that shots fired are seen.

Insufficient sequences

Flag codeinsufficient_sequences
When it appliesThe verdict is Cheating and fewer than 3 sequences were scored.
Values shown on the detectionNumber of sequences, and the minimum of 3.

What it means

Sequences are normally scored five at a time. When a player leaves before reaching five, the ones collected so far are still sent. With fewer than three fights there is too little evidence to trust the verdict.

Common causes

The player disconnected, crashed, was kicked or timed out shortly after a fight.
A map change or server restart ended the session early.
A short session with only one or two qualifying fights.

What to do

Nothing. The player's next session will produce full batches of five. If a player keeps leaving after a fight or two with high confidence each time, check their other detections and replays.