All posts

How CSJS stopped wallhacks

Why hidden enemies used to show up in game updates, and how CSJS fixed it.

CSJS

When player occlusion is enabled, the CSJS server checks whether solid cover hides an opponent from you. If they're fully hidden, the server leaves their location out of the updates it sends to your browser. The feature is off by default.

Where wallhacks get their data

Before this change, your browser could receive an opponent's position even when a wall hid them on screen. A wallhack could read those coordinates and draw a marker that followed the opponent as they moved behind cover.

How server-side occlusion works

The map gives the server a rough idea of which areas you could see. For opponents in those areas, the server traces lines from your eyes to several points on their body. A clear line lets the server include their position in your update. A teammate holding a different angle gets a separate result.

Diagram showing a wall blocking the sightline between a player and an opponent.
A wall blocks one of the server's sightline checks.

What happens when you peek

At a tight corner, the edge of an opponent's collision bounds can come into view before the first few points the server checks. That made opponents appear late on some peeks. If those first lines are blocked, the server now checks the corners of the bounds too, so a narrow opening can count sooner.

A wallhack can remember where it last saw an opponent. It has no new location to draw while that opponent moves behind solid cover.