Anti resource stop

The ByteAC client sends a heartbeat every 20 s. The server also counts what it sees the player do (walking on foot, damage events). Silence while the player keeps playing means ByteAC was stopped while the game runs: that gets the action set here. Silence without movement (frozen game, loading, AFK) is logged once and never punished. If more than 10% of players go silent at once, nobody is reported and the server console warns, because the problem is on your side. A stop message from the client on its own is only logged.

Checked in the player's game and on the server.

These are the values shown under the detection in the Threat feed and on the player page.

silentFor

Seconds since the last heartbeat (or since joining when never is true).

never

true = this player never sent a single heartbeat since joining.

active

true = the server saw the player keep playing during the silence (this is the case that gets punished). false = no movement or shots.

walkedM

Metres the player walked on foot during the silence, measured by the server.

shots

Damage events the player caused during the silence.

widespread

Number of players silent at the same time. Present = not counted against the player.

resource

Only on the stop message: name of the resource that was stopped in the player's game.

source

Where the check ran: "client" = the ByteAC script inside the player's game reported it, "server" = the server measured it itself. Server measurements cannot be faked by the player.

active:false is normal (alt-tab, crash dialog, loading). active:true without cheating is rare: a client crash of ByteAC alone.

Ban is fine because only active:true is punished.

The action (Off, Log, Kick, Ban) is set per detection on the Protection page. It only applies when Enforcement is on Custom. See Actions, modes & numbers.

Heartbeat timeoutdefault 75 s

Silence before a player who is still playing is reported. Plain silence waits at least 120 s.