Wallhack vs radar

"Wallhack" and "radar" are sometimes used interchangeably, but they're different mechanisms with different trade-offs. Knowing the distinction matters if you're deciding between them.

What a wallhack does

A wallhack is rendered inside the game process. It hooks into the game's draw loop and adds extra visual elements - boxes, skeletons, name plates - directly on your main viewport, layered on top of the normal scene. Players are visible through walls because the wallhack is drawing them on top of the world geometry.

Implementation-wise this means injecting code into the running game, intercepting graphics API calls (DirectX, Vulkan), and pushing additional draw calls into the same rendering pipeline.

What a web radar does

A web radar like Favade renders outside the game. The game state is read by a small companion process and forwarded to a browser-rendered top-down view. Nothing is drawn on top of CS2's main viewport; the radar surface lives on a different screen entirely.

Trade-offs

Field of vision

A wallhack shows players in the same perspective you're playing - first-person, through walls. A radar gives you a top-down map view: better for awareness across the whole map, weaker for pinpoint aim through a wall.

Distraction

A wallhack adds visual elements to your main HUD. A radar lives on a second screen, so your primary view stays clean.

Sharing

A wallhack is inherently single-player - what you see is rendered on your machine. A radar can be stream-shared so a teammate or coach watches the same surface without their own license.

Detection posture

The two mechanisms have very different exposure surfaces. We make no absolute safety claims - every kind of third-party tooling carries risk - but the surfaces differ technically. Each user accepts the risk of running tooling alongside their game.

What Favade is

Favade is both: a web radar on a second screen and an in-game ESP overlay drawn directly on your main CS2 viewport. The two surfaces ship with the same license - you don't pick one or the other.

The web radar is a browser view on a second screen showing the top-down map with players, utility, bomb state, and stream-share for anyone you authorise.
The in-game ESP draws boxes, skeletons, health, names, weapons, and distance labels on top of CS2's normal scene - enemies visible through walls in your main view.

Risk-wise the two surfaces are not equivalent. The radar lives outside the game; the in-game ESP runs inside the game process. We make no absolute safety claims for either - every kind of third-party tooling alongside CS2 carries risk, and each user accepts that risk. The benefit of having both is that you can choose which surface to use in a given session: radar-only for minimum exposure, in-game ESP when you want it.