Main / Client detections
Anti spectate
client.spectateclientDefault: logThe player watches another player through spectator mode.
How ByteAC finds it
The client checks every second whether the game is in spectator mode without permission.
Reported by the ByteAC script in the player's game. A strong signal, but a modified client could hide it.
What the numbers mean
These are the values shown under the detection in the Threat feed and on the player page.
- 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.
Can also be caused by
Admin menus that spectate. txAdmin is handled.
What to do
Log, or Kick on servers without admin spectate.
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.
Related settings
- Max on-foot speeddefault 25 m/s
- -
- Teleport distancedefault 120 m
- -
- Super jump heightdefault 8 m
- Height gained on foot within 1.5 s before anti super jump flags. Raise it if scripts lift or launch players.
- No-ragdoll gracedefault 1 s
- Ragdoll must stay disabled this long in a row before anti no-ragdoll flags. Raise it if your scripts disable ragdoll for a while (spawn protection, safe zones).
- Allowed ped modelsdefault 2 entries
- Used by anti model change. Leave empty to allow all.