Anti silent aim

Two checks, both only for hits the server saw itself from this shooter on this victim. Crosshair: the shooter's game measures how far the crosshair pointed from the victim at the moment of the hit; 25 degrees or more counts. Body: for hits more than 15 m away, the server checks whether the victim stood behind the shooter's body. Shotguns, fists and shots from vehicles are skipped. The first two counted hits within a minute are only logged; the third gets the action set here.

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.

crosshairOff

Crosshair check: degrees between where the crosshair pointed and the closest body part of the victim. 0 = dead on. A normal hit is under 5.

aiming

Crosshair check: true = the shooter was aiming down sights at that moment.

dot

Direction check from -1 to 1: 1 = target straight in front of the shooter's body, 0 = exactly to the side, -1 = straight behind. Below -0.2 means behind the body.

distance

Metres to the target.

hits

Counted off-aim hits within the last minute (1, 2, 3...). The action only applies from 3.

weapon

GTA weapon hash of the weapon used, as a number. 2725352035 = WEAPON_UNARMED (fists). Use the Hash lookup page for others; custom (add-on) weapons will not be in the list.

damage

Damage the game reported for this hit (GTA health points; a player has 100 usable HP above the 100 of a downed ped, plus up to 100 armor).

held

Only on records from older ByteAC versions: the weapon in the shooter's hand.

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.

One or two hits: lag between the players, or the body turning while the crosshair stays. That is why only three within a minute count.

Ban is reasonable once you have seen it on Log for a few days. Records with crosshairOff are much stronger than records with only dot.

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.

Memory aimbot framesdefault 22

Frames the camera must follow a player without matching mouse input before a lock counts. Locks where the mouse was moving need 1.5x as many.

Min hits for headshot checkdefault 30

-

Headshot % above server normaldefault 80 %

How many % higher than this server's normal player median before flagging (e.g. normal 33% + 80% above = flags at ~60% HS).

Max hit distancedefault 450 m

-

Max hits per seconddefault 18

-

Inventory check exemptionsdefault 0 entries

Jobs whose weapons come from scripts instead of the inventory.