The key difference from kill aura is the absence of auto-aim. Kill aura finds the nearest target in radius on its own, snaps the camera, and attacks by itself. On any decent server with NoCheatPlus, Matrix, Vulcan, or Grim these actions get flagged: attack angles that are too clean, hits without line of sight, hitbox connections the player physically should not see. TriggerBot is free of these issues by definition: if you did not aim, there is no hit. That is why on servers where kill aura lives a minute before the ban, the trigger calmly runs for hours.
The core setting is the delay between target detection and the click. In Winlend it is set in milliseconds, usually in the 50–200 ms range. 50 ms is near-instant reaction, faster than a live player, and you should not push that on servers with behavioral anti-cheat. 100–150 ms is a realistic human reflex — that is exactly what a trained PvP player needs for a conscious click. 180–200 ms is maximum safety, looks like a slightly lazy reaction, indistinguishable from regular play. On top of that there is randomization: the delay floats inside a defined window so the timings never line up. This is the bypass for behavioral anti-cheat — the server has nothing to grab onto because there is no pattern.
The second important parameter is the activation mode. Hold-mode requires you to hold a chosen key (usually right mouse button or a separate bind). Release it, clicks stop. This is the controlled option for duels: you decide when the trigger is active, the rest of the game goes without it. Auto-mode keeps the module running constantly while it is toggled on in the menu — handy for long farm sessions or mass fights. In Winlend both modes switch in one window, plus there is a separate hotkey for fast on/off.
The friend/foe filter is the thing without which a trigger on a server with friends turns into a disaster. The module can tell who to hit and who to skip. Winlend keeps a local friends list by nickname, and TriggerBot ignores them even if your crosshair accidentally drifts over. Same for mobs: you can enable attacks only on players or add specific entity types for grind setups. A separate item is the reaction to invis players: if you want, the module ignores invisible enemies so you do not get flagged for clicking empty space.
Now about versions. Winlend supports 1.16.5, 1.21.4, and 1.21.11 — the three working branches the Russian-speaking PvP community sits on right now. 1.16.5 is the classic for duel and anarchy servers, the old combat with 1.9 timing, so the trigger gets tuned a bit longer there. 1.21.4 is the main current version for most new pack servers and mid-tier projects. 1.21.11 is the freshest worlds, where all the new updates land and where anti-cheats are already tightened for the latest patches. The module works identically across all three branches, the only difference is which client build you download. You can download the triggerbot together with Winlend on the product page: https://cheatgarden.com/product/winlend — separate builds for each version are right there.
Legit use is the main scenario this module exists for. On honest PvP servers, where admins actually monitor logs and run fresh anti-cheat, kill aura is a one-way ticket to a ban inside a couple of rounds. TriggerBot gives a real edge without exposure: you get perfect click timing, you do not lose milliseconds on reaction, you hit exactly on the frame where the hitbox sits under your crosshair. In duels this boosts effective CPS and removes finger fatigue on long sets. On mixes and bedwars the trigger helps finish off opponents when they slip across your crosshair in close range. On anarchy servers and during raids the module covers the routine: automatic clicks on the right target while you handle movement, building, or a stealth approach.
A few words on tuning so the trigger does not get flagged. Do not drop the delay below 80 ms — that is already past human reaction, and servers with timing analysis catch that. Always turn on randomization, at least plus-minus 30 ms around the base delay. If you play duels, use hold-mode on right click or a separate bind — that gives you control and does not raise suspicion when you visibly whiff into empty space. Do not run it together with aimbot modules: if you are using the trigger for stealth, do not break that disguise with another obvious cheat.
About the standalone triggerbot mod outside of a client, a separate note. Around the web you can find standalone mod files for forge or fabric that drop into a regular launcher. The problem is, most such builds are either outdated versions without updates for fresh anti-cheats, or outright stealers that grab account tokens. In the Winlend client the module ships as part of a whole build, updates together with game and anti-cheat patches, and does not need you to install mods separately on top. This is a working legit triggerbot for the version you need, no dancing around mod conflicts or dependency matching.
Frequently asked questions
How is triggerbot different from kill aura?
Kill aura does everything on its own: finds a target in radius, snaps the camera, attacks. Because of this almost every modern anti-cheat catches it — angles too clean, hits without direct line of sight, inhuman turns. TriggerBot only fires when you yourself aim the crosshair at the enemy. No auto-aim, no suspicious camera movement, no hits through walls. From the outside it looks like normal PvP with very stable click timing. That is why on servers where kill aura lives minutes, the trigger calmly works for hours. This is the main pick for honest arenas and duel grounds with serious moderation.
Which Minecraft versions does TriggerBot in Winlend support?
The module is present in all three working client branches: 1.16.5, 1.21.4, and 1.21.11. 1.16.5 is old combat with 1.9 timing, relevant for classic duel and anarchy servers. 1.21.4 is the main fresh version most new pack servers and mid-tier projects sit on. 1.21.11 is the latest branch with anti-cheats updated for current patches. You download the build for your game version, install it, hop on the server. TriggerBot logic is identical across all three branches, the difference is purely technical compatibility with Minecraft itself. You can download the triggerbot together with the client on the Winlend product page.
What delay should I set to not get flagged?
The optimal range is 100–180 ms with randomization plus-minus 30 ms enabled. That lands inside the typical human reaction of a trained PvP player. Setting under 80 ms is a bad idea: that speed is already past biological reaction, and servers with behavioral analysis on hit timing pick it up. 200 ms is the maximum-safety option, looks like slightly lazy but absolutely alive gameplay. The main thing is not to forget randomization: a fixed 100 ms delay on every click gets flagged by interval statistics even by simple anti-cheats. A floating spread breaks the pattern and makes the module indistinguishable from a regular player.
What is hold-mode and what is it for?
Hold-mode is a mode where TriggerBot only works while you hold a chosen key. Release it, clicks stop. Usually bound to right mouse button or a separate hotkey. Why you want this: in duels you decide when the module is active, and the rest of the game runs completely normally. If you accidentally aim at a teammate or a peaceful player — the click does not go through, because you simply did not press the key. It is also useful for stealth: if someone is watching your gameplay or you suspect screen-sharing by an admin, the trigger is off by default and only activates at the right moment. Auto-mode keeps the module always on — handier for long farm and raids.
Does triggerbot get caught by anti-cheats on modern servers?
Properly tuned — no. Modern anti-cheats like Grim, Matrix, or Vulcan are aimed primarily at catching auto-aim, hits through walls, inhuman camera turn angles, and impossible hitbox connections. TriggerBot does none of that — it just presses left click when your own crosshair is already on target. It only gets flagged in two cases: if the delay is too short (under 80 ms) or if it is fixed without randomization, giving perfectly even intervals between hits. In Winlend both of these are covered by settings: delay randomization and a flexible range let you make the behavior indistinguishable from a live player. That is exactly the legit triggerbot.
Can I use TriggerBot with friends on the same server?
Yes, that is what the friend/foe filter is for. The client keeps a local friends list by nickname — you add your teammates there, and TriggerBot ignores them even if you accidentally swing the crosshair over during a mass fight. This matters especially on bedwars, in team mixes, and on anarchy servers with alliances, where an accidental hit on your own can cost a round or a kick from the team. You can also tune the reaction to different mobs: for example, hit only players or enable attacks on specific entities for farming. The friends list is stored locally and does not need confirmation from the other side — it is just the module's internal filter.
Why is a standalone triggerbot mod worse than the client-integrated one?
Standalone mods for forge or fabric floating around the web usually suffer from three issues. First — outdated versions: the author dropped a build for 1.20 and quit, and you are trying to stretch it onto 1.21.11 and get a crash or incompatibility with the current anti-cheat. Second — no updates: servers patch their defenses every couple of weeks, and a one-off mod stays stuck with old logic. Third and most dangerous — stealers: a significant share of free mods with a trigger inside grabs Microsoft account tokens and Minecraft sessions. In Winlend the module is part of the client, updated centrally with game patches, and does not require fiddling with separate mod installs on top of the launcher.