Weapons / Weapon cheats
Anti external memory aimbot
weapons.memory_aimbothDefault: logThe camera follows a moving player by itself: an external aimbot writes camera angles into game memory.
How ByteAC finds it
While aiming or firing, the client compares how much the camera turns with how much the mouse moved. A lock is counted when the camera follows a player's head or chest for many frames more than the mouse explains (mouse still, moving only up/down, or moving the other way). The server needs 2 locks within 2 minutes (or 1 very strong one) before it reports.
Checked in the player's game and on the server.
What the numbers mean
These are the values shown under the detection in the Threat feed and on the player page.
- confidence
- ByteAC's estimate from 50% to 99%, higher with more locks, larger turns, locks through walls and a high headshot rate.
- locks
- Locks within 2 minutes.
- yawDeg
- Degrees the camera turned that the mouse does not explain.
- coneDeg
- Closest the crosshair got to the target bone, in degrees (under 1 = dead on).
- frames
- Frames the lock lasted.
- idleFrames
- Frames with the mouse completely still.
- steerFrames
- Frames with the mouse moving, but not enough or the wrong way.
- wallFrames
- Frames without line of sight to the target (locked through a wall).
- distM
- Distance to the target in metres.
- mouse
- "idle" = mouse still during the lock (strongest), "moving" = mouse moved.
- headshotPct / aboveNormal / hits / headshots
- The player's headshot rate this session compared with your server's normal player.
- 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
Controllers with aim assist, vehicle cameras, scripted cameras. Keyboard and mouse only; vehicles are skipped.
What to do
Log. Several reports with mouse idle and high confidence are very strong.
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
- 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.