Part 6: Peeker's advantage, sub-tick, and the ghost in your kill cam

Part 6 of 8 in The Field Manual, Stazione's guide to how Counter-Strike actually plays, from defined mechanics to high-level theory and the detours in between. Full list at the bottom.

You were holding the angle. You had your crosshair right there. The enemy stepped out and you were dead before he fully appeared. Cheater? Usually not. Usually it's physics, or rather the physics of sending information across the internet. This is the most misunderstood mechanic in Counter-Strike, and once you understand it, you'll play angles differently.

Peeker's advantage, in one paragraph

When you peek, your own computer shows you the enemy the moment you start moving, because it's your movement. The player holding the angle only sees you after your movement travels to the server, gets processed, and travels back out to them, and then their game adds a small buffer to keep motion smooth. For a sliver of time, you can see them and they can't yet see you. That sliver is peeker's advantage. It isn't a bug or a cheat. Every online shooter has it. The size depends on everyone's connection.

What that means for how people play

• Wide swings: fast, committed peeks that take full advantage of the head start instead of inching out.
• Jiggle peeks: stepping out and straight back to bait a shot or grab information, without really committing to a fight.
• Holding off-angles: standing somewhere the peeker doesn't expect, so their head start is spent looking at the wrong spot.
• Crossfires: two defenders watching one doorway from different places. A peeker can win the race against one of them, but not both at once.

This is also part of why defenders play in pairs, and why "just hold the angle" is worse advice than it sounds.

Ticks and sub-tick

A server doesn't update continuously. It simulates the game in steps called ticks. Valve's official CS2 servers run 64 of them per second. In CS:GO, where many third-party services ran 128, "64 vs 128 tick" was one of the community's longest arguments.

CS2's answer was sub-tick: your client timestamps exactly when you clicked, moved or threw, instead of rounding every action to the nearest tick. So the server knows precisely when you fired, even if it happened between ticks. What sub-tick doesn't change is that the server still simulates and sends updates 64 times a second, and latency is still latency. Peeker's advantage sits on top of all of it, just as it did before.

"I died behind the wall"

The other famous complaint is dying after you've already reached cover. To make hitting moving targets fair, the server rewinds time to check what the shooter actually saw when they fired (lag compensation). If they hit you on their screen, the hit counts, even if on your screen you'd already made it around the corner. CS2 had a rough stretch of this feeling worse than it should after launch in September 2023, and Valve has worked on it since. The underlying tradeoff will never fully go away: someone's screen has to be the one that counts.

Worth arguing about: is peeker's advantage a skill to exploit, or a flaw CS should keep trying to fix?

Argue it out in the discussion thread. That's where this actually gets resolved.

Where these numbers come from: Dexerto on sub-tick · CSDB.gg: what is CS2's tick rate. Game values are current as of September 2026; Valve changes them, and we'll update when it does.