Main / Executor detections
Illegal native execution
exec.illegal_nativeclientDefault: logA dangerous game function was called from inside ByteAC's own environment.
How ByteAC finds it
ByteAC wraps AddOwnedExplosion, ShootSingleBulletBetweenCoords, SetPlayerWeaponDamageModifier, NetworkExplodeVehicle and SetEntityInvincible in its own environment. ByteAC never calls them, so any call there came from injected code.
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.
- native
- Which of these functions was called.
- 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.
What to do
Ban once you have seen it fire on a known cheater.
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.