Triggerbot in Favade
How Favade's VAC-conservative triggerbot works - what it gates on, when it fires, the humanized reaction delay, and how to set it up.
Last updated: 2026-06-02
Favade's triggerbot is built to be conservative. It only fires when the conditions look clean: a real, visible enemy hitbox sitting under your crosshair, with a humanized delay between the moment the conditions go true and the moment the click goes out.
What it actually checks
The triggerbot evaluates several conditions every frame and only fires when all of them are true:
- Crosshair on a hitbox. A real entity hitbox - not a friendly, not a dropped weapon, not a smoke.
- Visible target. The world-physics parser confirms the bullet would actually reach the entity, taking world geometry into account.
- Local pawn alive. The triggerbot self-disables on death and during freeze periods.
- Safe-mode on. The global VAC-conservative gate; see safe-mode and VAC posture.
If any condition fails, no input is generated.
Humanized reaction delay
Once the conditions all become true, the triggerbot waits a randomized humanized delay before issuing the click. The delay is not constant - it varies on each activation - so the timing pattern does not look like a fixed-interval script.
A small delay still feels close to instant in practice; the point is to avoid a fingerprint where every shot fires at exactly the same millisecond offset.
Inline safe-mode notice
The triggerbot tab in the menu carries an inline notice describing what's gated and why. If you flip safe-mode off, the notice updates to tell you which checks are now disabled and which features will stop running. You should always be able to see, in the menu, what state the triggerbot is in.
Recommended setup
- Safe-mode on.
- Triggerbot enabled in its own tab.
- Activation hotkey bound to a key you don't press by accident (a mouse side-button works well).
- Leave the humanized delay at its default unless you have a reason to change it.
When it will not fire
Common reasons the triggerbot will not fire even though it is enabled in the menu:
- Safe-mode is off.
- You are dead, in a freeze period, or in warmup.
- The crosshair is on a teammate or non-player entity.
- The world-physics check thinks the target is occluded.
- The activation hotkey is bound to a key you are not pressing.