Safe-mode and VAC posture
What safe-mode is in Favade, why aim assist and the triggerbot self-gate on it, and what we mean when we describe a feature as VAC-conservative.
Last updated: 2026-06-02
Safe-mode is the global toggle that gates Favade's more invasive features behind a single conservative posture. Aim assist and the triggerbot self-gate on it; if it's off, those features stay off. The point is that the most aggressive behavior in the product is never one click away by accident.
What safe-mode does
When safe-mode is on, the gated features only act when conditions are clean:
- Visible target. The runtime world-physics parser confirms the entity is actually reachable through world geometry.
- Real hitbox. The crosshair has to sit on a real enemy hitbox, not a teammate, not a dropped weapon, not a smoke.
- Humanized timing. Aim motion and triggerbot fires get humanized delays so the input pattern looks like a person playing.
- Alive in-game. Gated features disable on death and during freeze.
What "VAC-conservative" means
A feature that we call VAC-conservative is one that defers, delays, or refuses to act rather than reaching for the most aggressive behavior. The triggerbot waits for the cleanest conditions and adds a humanized delay; aim assist moves the mouse through a motion model rather than writing view angles directly. These are deliberate choices, not bugs.
Conservative is not the same as undetected. No third-party CS2 tool is risk-free. Safe-mode is about reducing fingerprint and avoiding the most obvious patterns. It does not make Favade invisible to anti-cheat or to spectators. See wallhack vs radar for the broader risk discussion.
What happens when safe-mode is off
The aim assist and triggerbot tabs in the menu carry inline notices that explain exactly what's gated. With safe-mode off, several of those features simply won't run, regardless of whether the per-feature toggle is on. The notice tells you which checks are disabled and why.
We make this a deliberate two-step rather than a single global toggle so that you cannot enable the more invasive behavior by accident.
Surfaces that are not gated
The browser radar and the in-game ESP do not gate on safe-mode. The radar runs entirely outside the game process; the ESP is read-only against game memory and does not produce input. The triggerbot and aim assist are the surfaces that produce in-game input - those are the ones safe-mode protects.