What it does
Here the player swings and a program aims: AimAssist pulls the crosshair toward the nearest opponent while the player moves the mouse and clicks, and Aimbot simply locks on. Because a human is doing the hitting, it's easy to pass off as skill — “he just has good aim”.
It shines wherever the target moves a lot: strafing in duels, jump fights on anarchy, chasing someone around a bed in BedWars, bow shots. Keeping your crosshair on a jumping opponent is hard to do honestly; with aim assist it's free.
How to spot it
- The crosshair sticks to the hitbox and follows through sharp strafes and jumps
- Turns run at one speed and brake smoothly right on the target — no overshoot, no correction
- When switching targets, the view glides to the new opponent in an unnaturally clean arc
- The crosshair keeps tracking an opponent hidden behind blocks
How it gets caught
The mouse turns the camera in steps whose size is set by sensitivity, so an honest player's rotations sit on a fixed grid. A cheat computes its own angles, and its rotations often fall off that grid. There's handwriting too: a real hand overshoots and corrects back, while aim assist brakes perfectly, fight after fight.
False signals come from the cinematic camera and zoom mods, which change smoothing and sensitivity; in DGuard, allowed mods are written into the code and produce no evidence. DGuard's aim and TriggerBot rules run in its cloud check: the plugin sends only measurements — camera turns, clicks and hits — with no nicknames.