Injected thread / environment

Three checks report under this key: the Lua environment of the ByteAC client is missing basic parts (Citizen or debug), ByteAC's own functions were replaced after loading, or the server received a report code that does not exist in ByteAC.

Reported by the ByteAC script in the player's game. A strong signal, but a modified client could hide it.

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

env

"citizen" = the Citizen table or the debug library is missing or replaced in ByteAC's environment.

fn

"byteac core hook" = ByteAC's own report or check functions were swapped for something else.

reason

"unknown report code" = the player's game sent a report that no real ByteAC client can send (forged event).

code

The fake report code that was sent.

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.

None known. These states do not happen in a normal game.

Ban.

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.