Misc
Anti Bot
Filters bots out of the modules that target or draw players.
Some servers fill an arena with bots, and anything that looks for players finds them first. Anti Bot decides which players are bots, and the modules that target or draw players skip the ones it flags.
It does not do anything on its own. It is a filter the other modules read.
What it affects
Combat: Aim Assist, Back Track, Hitbox and Pearl Aimbot will not pick a flagged player as a target.
Visual: Player ESP, Name Tags and Tracers will not draw one.
Nothing else reads it. Reach, Velocity and the clicker modules are unaffected, because none of them choose a player to act on.
How it spots a bot
A player with no gamertag is treated as a bot. Real accounts always have one, and server-spawned bots usually do not, so the test is cheap and does not produce false positives on players.
Tip
Anti Bot starts switched on, so the filter is already working the first time you open the menu.
Note
Turning Anti Bot off does not flag anything — it stops filtering, and every module goes back to treating bots as ordinary players.
Settings
What Anti Bot does. Every value below is where the module starts before you change anything.
No name
On
Treat a player with no gamertag as a bot. This is the only rule Anti Bot applies, so turning it off leaves the module with nothing to match and no effect.
Conditions
When Anti Bot is allowed to act. Keybind and Enabled are on every module in the Client.
Keybind
None
A key that toggles this module while playing. Shortcuts are suppressed while the external editor has focus or another screen captures input. Click GUI defaults to Right Shift; other modules start unbound (None).
Enabled
On
Whether the module is running. Anti Bot and Anti Reach Display start on; other modules start off. Click GUI's open state is not saved, so the editor starts closed each launch.