Minecraft has no traditional anti-cheat — servers run plugins like Watchdog (Hypixel), NCP, or AAC. These detect statistical anomalies in movement and combat data, not memory injection. So you need a client that spoofs those statistics.
What a Good Hack Client Does
- Killaura: Hits players without looking at them. Good clients rotate the head server-side to avoid Watchdog flags.
- Speed: Ground speed increase. Set to 1.2–1.5x max to avoid NCP kicks.
- ESP/Tracers: See player positions through walls.
- Anti-KB: Reduce knockback from hits.
- Scaffold: Auto-places blocks while bridging.
Hypixel-Safe Config
Hypixel Watchdog bans in waves, not instantly. Moderate settings work for weeks. Keep killaura range under 3.2 blocks (vanilla reach is 3.0) and CPS under 12.
Get the full client at CosmoCheatz Minecraft page.
Version-Specific Bypass Behaviour
Minecraft 1.20.2 changed the movement packet ordering in a way that broke most speed modules written for 1.19.x. Clients now ship separate movement handlers for 1.20.1 and 1.20.4 because the server tick rate and anticheat buffer thresholds differ. On Hypixel, 1.20.4 clients must cap vertical velocity at 0.42 blocks per tick to avoid the new NCP vertical check; older clients use 0.6. Paper servers running 1.21.1 with Vulcan 2.9 will flag any speed above 1.3x within 12 blocks of a block update, so scaffold and speed cannot be used together. Verify a bypass by typing /ae or checking the server console for the anticheat's debug prefix — a clean run shows no 'failed movement' lines for 30 seconds of strafing. Common mistake: copying a 1.8.9 config onto a 1.21 client; the killaura range maths assumes 3.0 reach but 1.21 vanilla reach is 3.0 blocks for players and 4.5 for entities, so a 3.2 setting overreaches on entity hits.
Detecting Silent Flags Before Bans
Most servers do not ban on the first flag; they log it. Watchdog reports are visible to staff via /watchdogreport and accumulate in a database. A silent flag happens when your reach exceeds 3.3 blocks for more than two consecutive hits, or your rotation snaps more than 180 degrees in one tick. Test by enabling a client's debug HUD and watching the 'flags' counter during a 10-minute bedwars game — anything above zero means the config is too aggressive. On Grim 2.5, a single flag appears in the console as 'Grim:
Client-Side Performance and Module Conflicts
Running ESP and tracers together at render distance 16 adds roughly 12 ms per frame on a GTX 1660; the fix is to limit ESP to 48 blocks and disable tracers for entities outside 32 blocks. Fabric-based clients on 1.21.1 conflict with Sodium 0.5.8 because both hook the same chunk render event, causing a hard crash when entering the nether. Use Iris 1.7.3 instead of OptiFine — OptiFine's custom sky renderer breaks scaffold's block placement preview. Module conflicts are common: killaura and autoclicker both write to the attack packet, producing double hits that NCP flags as 'invalid attack frequency' within 20 seconds. Disable autoclicker when killaura is active. Verify stability by running a 5-minute loop of bridging with scaffold while killaura targets a armour stand; if the client drops below 60 fps or logs a 'packet desync', reduce the scaffold place delay from 0 to 2 ticks. People get wrong that higher CPS equals better killaura — above 14 CPS the hit registration on 1.20.4 servers drops packets and your effective DPS falls.