External memory write

Every 1 to 2 minutes ByteAC sets a harmless marker (one damage-proof flag) on the player's own character 6 times and checks that it is still there half a second later. A normal game keeps it. A tool that writes to the character's memory from outside wipes it. The server only reports a player whose marker vanished in at least 3 checks in a row while at least 80% of the other players kept theirs, and at most once per 10 minutes.

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.

probes

How many times the marker was set in the last check (4 to 6).

lost

How many of those times it was gone again. 6/6 = every time.

checks

How many checks in a row came back wiped. Each check is 1 to 2 minutes apart.

seconds

Seconds from the first wiped check to this report.

cleanPlayers

Other players checked in the last 5 minutes who kept their marker.

comparedWith

Other players checked in the last 5 minutes. cleanPlayers = comparedWith means everyone else was fine.

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.

Trainers, overlays or other external tools that write game memory are caught too (not allowed either, but not always an aimbot). If a script on your server resets damage proofs for everyone, the check turns itself off and the server console says so.

Log. Strong lead when checks keeps growing over many reports. Watch the player live before banning.

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.