What is a triggerbot?

A triggerbot fires for you when your crosshair lands on an enemy. It does not move your aim - that's an aimbot. A triggerbot is strictly an automated mouse click that happens when the conditions you configured are met.

How a triggerbot works

Reads where your crosshair is pointed in-game.
Checks whether something the player would shoot at sits under that point.
If yes, issues a left-click (sometimes after a small delay).
If no, does nothing.

That's the whole loop. The interesting decisions are which checks happen first, how confident the bot has to be before clicking, and how the click is timed.

What separates a careless triggerbot from a careful one

Hitbox vs colour. The least-careful triggerbots fire when a pixel in the crosshair matches an enemy outline colour. They click at smokes, decals, the wrong team. Careful ones check actual entity hitboxes.
Friendly check. Whether the bot refuses to fire at teammates. Sounds obvious. Plenty of cheap triggerbots skip it.
Visibility check. Whether the bot confirms the bullet would actually reach the target through world geometry. Without this, triggerbots fire into walls and give the player away.
Reaction delay. The time between "conditions met" and "click sent". Zero delay means every shot fires at the exact same millisecond offset from the trigger - a fingerprint. Humanized delays vary the timing.
Activation gate. A hotkey that has to be held, or a state condition like "only while a specific weapon is equipped".

Triggerbot vs aimbot vs ESP

These three categories are often bundled but they do different things:

ESP / radar - shows you information. No input. See what is ESP?
Aimbot - moves the mouse. Input. See what is an aimbot?
Triggerbot - clicks the mouse. Input, but only the click.

You can run a triggerbot without an aimbot (you aim, it fires) and an aimbot without a triggerbot (the bot aims, you fire). Bundling both is common; they're not the same feature.

How Favade's triggerbot works

Favade's triggerbot only fires when all of the following are true: crosshair on a real enemy hitbox, target visible through world geometry, local player alive, and safe-mode on. After the conditions flip true, the click is issued with a humanized delay that varies each activation, so the timing pattern doesn't look like a fixed-interval script.

With safe-mode off, the triggerbot stays disabled regardless of the per-feature toggle. The two-step gating is deliberate.

Risk

Triggerbot is an input-side feature and carries higher anti-cheat exposure than read-only overlays like ESP or radar. Favade's conservative defaults (visibility check + humanized delay + safe-mode gate) reduce the fingerprint - they aren't a safety guarantee. See anti-cheat and platform support before running it on a main account.