Counter-Strike 2 Subtick Netcode: How It Changes Peeking and Spray Transfers

Counter-Strike 2 didn't just get a visual upgrade. Under the hood, Valve ripped out the old networking model and replaced it with something called subtick. The marketing line was "tick rate no longer matters," and that one sentence kicked off more arguments than almost anything else in the game. Some of those arguments are based on real changes to how the game feels. A lot of them are based on misunderstandings about what subtick actually does. The honest version is messier than either side claims. Subtick fixes some old problems, leaves others in place, and shifts the feel of peeking and spraying in ways you can adjust to once you know what's going on. What follows walks through what subtick does under the hood, how peeking changed, why sprays feel different, why the tick-rate debate won't die, and what to actually change in your duels.

What Subtick Networking Actually Does

Ticks, in plain terms

A server tick is just a heartbeat. On the old CS:GO matchmaking servers, the server woke up 64 times a second, looked at everything every player did, and resolved it in a batch. That's a 64-tick server. Do the math and each beat lands roughly every 15.6 milliseconds (1000 divided by 64). Anything you did between two beats had to wait for the next one.

Here's the catch. If you clicked to fire 1 millisecond before a beat, the server couldn't see that. It only saw the click at the next beat, 14.6 milliseconds later. Multiply that across thousands of clicks and shots per match, and you get a small but real timing error baked into the whole game. Competitive services like FACEIT ran 128-tick servers for exactly this reason. Twice as many beats meant each one covered about 7.8 milliseconds, so the worst-case snap error got cut roughly in half. Tick rate mattered a lot, because that snap-to-the-beat error was the ceiling on how precise any single shot could be.

The timestamp trick

Subtick changes the rule. Instead of snapping your action to the next beat, the client stamps the exact moment you did it. Pull the trigger, tap a movement key, release a grenade. Each input ships to the server with a precise timestamp attached. The server still runs its 64 beats per second, but now it can line up events in the order they actually happened, even when several land inside the same beat.

So the precision of your shot no longer depends on how close to a beat you happened to click. Two players clicking inside the same 15.6-millisecond window can still be told apart. In theory, the old tick-rate ceiling goes away for shooting, moving, and throwing. That's the whole pitch behind the "moving beyond tick rate" line, and on the narrow question of input timing, it holds up.

What stays the same

A few limits did not move. Subtick does not speed up the physical round trip between your PC and the server, which still sits somewhere around 15 milliseconds on a decent connection and a lot more on a bad one. Light and packets only travel so fast. It also does not change the rate at which the server sends you updates about everyone else. You still see the world update at the server's tick cadence. What changed is how your inputs get resolved, not how fast information travels back and forth. Anyone who tells you subtick "removed lag" is selling something.

That distinction matters for the rest of this. Subtick made input timing sharper. It did not flatten the network, and it did not make peeker's advantage disappear. Two of the loudest complaints about CS2 actually trace back to that gap.

Peeker's Advantage in CS2 vs Source

Where the edge comes from

Peeker's advantage is a latency fact of life in any online shooter, and it has always existed in Counter-Strike. When you swing around a corner, you see the angle holder before they see you, because the packet saying "you moved" has to reach the server and then reach the holder on a delay. For a sliver of time, you have a head start on reacting. The holder is still staring at empty wall on their screen.

That window is tiny, but it stacks with reaction time. A skilled peeker can pre-aim the spot, swing, and fire before the holder's brain even registers that a model appeared. The same thing happened in CS:GO. The famous "Ferrari peek" was born in the old game, not this one. Subtick did not invent peeker's advantage. What it did was change the shape of it.

The old reference point

In CS:GO on a 128-tick LAN setup, engineers and serious players generally put the peeker's advantage window somewhere around 60 milliseconds once you added the server and client sides together. The exact figure varied by who was measuring and what the connection looked like, so treat that as a ballpark, not a spec sheet. The point is the number existed, people knew roughly where it lived, and on LAN with good settings it could be managed.

The wider community feeling about CS2 is that the window got worse and harder to manage, even in clean conditions. Faster player models, smoother animations, and the way Source 2 handles acceleration all nudge the aggressor's favor upward. Several analysts have argued peeker's advantage in CS2 is as strong as it has ever been in the series. That's a big claim, and reasonable people argue about the exact size of the effect, but the direction is pretty consistent across what players actually report feeling.

Why holding still got riskier

Put it together and the job of an angle holder changed. In CS:GO you could plant your crosshair on a common spot and trust that a clean headshot would settle the duel more often than not. In CS2, holding a perfectly static angle against a good swing is closer to a coin flip, because the peeker gets the first real look and your shot has to land inside a shrinking window. The model you see is also slightly behind where the server thinks the peeker is, which is the root of all those "shot first, died anyway" clips.

None of this is cheating or a bug. It's the netcode resolving two near-simultaneous events, and on a swing the resolution tends to favor whoever committed to the peek. So the smart play drifted away from camping one pixel.

Spray Transfer Timing Differences

The compressed-spray feeling

Sprays in CS2 use the same recoil patterns as CS:GO, at least on paper. The AK and the M4 still climb the same way, and the muscle memory from the old game still applies. What changed is how the game hands you that pattern. Because subtick resolves your shots more precisely, the spray can land tighter to where the pattern says it should. That sounds good, and mostly it is. The side effect is that the window you have to correct each pull feels smaller.

In CS:GO, a chunk of the old tick error gave you a little slack, an accidental forgiveness on timing. Pull the mouse a beat late and the noise sometimes covered it. CS2 takes that slack away because the shots land closer to their true timestamps. Plenty of players describe the result as the spray feeling "compressed," like the same number of bullets happen in slightly less playable time. Your hands have less margin to get the pull right before the pattern runs away from you.

Transfers feel tighter

Spray transfers, flicking from one dead enemy to a second target mid-spray, feel the effect even more. A clean transfer in CS:GO relied on a feel for the rhythm of the pattern and where the recoil was sitting when you snapped across. The new timing tightens that whole process. Miss the snap by a small amount and the first bullet on the second target lands higher than you expect, because the pattern kept climbing while your crosshair caught up.

The fix is mostly tempo. Slow the transfer a hair and let the crosshair settle before you commit the next pull, instead of trying to drag a live spray across two bodies at full speed. Players who treat the second target like a fresh micro-reset tend to connect more than those who try to chain it as one long motion. It's a small habit change, but it lines up with how the more precise timing punishes rushed transfers.

Shooting consistency updates

Valve has shipped several updates aimed squarely at how subtick handles shooting. The patches targeted consistency in how shots resolve between ticks, alongside the usual tweaks to grenade animations and sounds. The takeaway is that the spray and tap feel has been a moving target since launch, and Valve has been actively tuning it rather than leaving it set. If your muscle memory felt off in one patch and better in the next, that was probably real, not in your head. Check the patch notes when something suddenly feels different, because the resolution logic has changed more than once.

How Tick Rate Myths Persist Despite Subtick

"Just give us 128 tick"

This is the loudest myth and it refuses to die. The argument goes that CS2 matchmaking feels worse than old FACEIT 128-tick servers, so Valve should flip a switch, run 128-tick servers, and fix everything. The engineering reality is more annoying than that. Since subtick already stamps the precise time of each input, doubling the tick rate would only help at the margins. The big input-timing error that 128 tick used to fix is already handled by the timestamp.

That doesn't mean 128 tick would change nothing. It would smooth out how often you receive updates about other players, which affects how chunky fast movement looks on your screen. But it would not fix peeker's advantage, because that comes from network round-trip and reaction time, not from input snap error. So the demand for 128 tick is mostly aimed at a problem subtick already solved, while the problems people actually feel need different fixes entirely.

The pro-feel gap

Pros have a legitimate gripe that sits next to the myth. Even ropz, one of the most mechanically gifted players in the world, said the subjective feel of CS2 does not fully match 128-tick CS:GO. That's a real statement from a real player who would know. The interesting part is why. Subtick is more precise on paper. The timestamps are tighter. But the game still sends you the world at 64-tick cadence, and the way movement and animation interpolate can feel less crisp than the old 128-tick feed even when the math says it should be fine.

Two things are true at once here. The system can be technically correct and still feel worse to a top player whose hands are calibrated to the old game. "More precise" and "feels better" are not the same thing, and the gap between them is where most of the frustration lives.

Perception is not measured latency

The clean way to frame the whole debate is that how a game feels is not the same as what a network test measures. A player can have great ping, a perfect timestamp system, and a correct resolution of their shots, and still swear the game feels off. Feel is built from animation, sound, input cadence, and a dozen small cues that a single latency number does not capture. That's not the player being wrong. It's the limit of describing a human experience with a millisecond figure.

So when someone says "subtick is just an excuse to run cheap servers," they're mashing together a few separate complaints. Some are about cost and infrastructure, which is a fair thing to push Valve on. Some are about feel, which subtick genuinely changed. Some are about peeker's advantage, which is a network reality. Untangling them is a lot more useful than the shouting match, because each one has a different answer.

Practical Adjustments for Duels and Trades

Stop holding pure static angles

This is the single biggest adjustment for most players. Lining up a crosshair on a head-height pixel and waiting is now the weakest it has been in the series, because peeker's advantage rewards the mover. You don't have to abandon holding angles entirely. You do have to stop being the easy target who sits on one spot for ten seconds. Hold a slightly off-angle, one step away from where a peeker pre-aims. Reposition between duels so the same attacker can't pre-fire the spot you were just on. Or skip holding altogether and peek into the enemy on your terms, turning their edge back on them by becoming the mover.

Jiggle peeking is your friend here. Quick out-and-back movements bait the first shot from an overeager holder, and once they've fired and missed, the angle is yours. The key is not to fire on the first jiggle. Let them commit to the trigger pull, then swing wide and take the duel while their weapon is resetting. Against a team that swings hard, the players who win are usually the ones who refused to let the enemy dictate the peek in the first place.

Trade fast, trade together

Since peeker's advantage favors whoever moves, the answer to losing a teammate is almost always to trade immediately. Your teammate dies on a swing, and for a brief moment the enemy is committed, exposed, and looking the wrong way. That's your window to peek the same angle and even the numbers before the enemy can reset. The longer you wait, the more the advantage swings back to them.

Trading is a habit more than a skill. You need to be close enough to your teammate that you can peek within a beat or two of their death, not stacked so far back that the enemy has time to reposition. Play in pairs around choke points, agree on who peeks first, and treat the follow-up peek as part of the same play, not a reaction you think about after the fact. Done well, trading turns peeker's advantage into a wash, because even if the first peeker wins their duel, the trade peeker walks in with the same edge against a target who just stopped moving.

Counter-strafe and wide swings

Clean counter-strafing matters more under the new netcode, because the precision of your first shot is tied to stopping correctly. Tap the opposite movement key to kill your momentum so the server sees you as still when you fire, instead of sliding. Sloppy counter-strafes that worked on the old tick slack will now leave you moving when the shot resolves, and a moving shot is a missed shot at range. Spend five minutes in an aim map to make the stop clean. It pays for itself fast.

On the attacking side, lean into the wide swing. A controlled wide peek catches holders who set up on the common angle and forces them to track you across more screen space. Pair it with a pre-aim on where you expect the head, and the holder has to react to a model that's already partly past their crosshair. The risk is over-swinging into a second defender, so wide swings work best when you have info on how many are there, or when a teammate is trading right behind you.

Utility and repositioning

When raw duels feel coin-flippy, shift the load onto utility. A flashbang erases peeker's advantage for the half-second the holder is blind, because they can't react to a model they can't see. Smokes cut the sightline so the peeker has to swing blind into your space, which flips the edge back to whoever holds the gap. Molotovs deny the swing angle entirely and force the peeker to wait or reroute. Not a bad toolbox to lean on when the rifle duels stop going your way.

Repositioning does similar work. After you take or contest a duel, move. Even a small shift to a new angle resets the pre-aim the enemy had on you and makes them re-earn the peek. Against players who pre-fire common spots, the simplest counter is to not be on the common spot anymore. The netcode punishes the stationary and rewards whoever keeps moving, so build repositioning into your rhythm the way you'd build reloads. Peek, fight, shift a step, repeat. That loop, more than any single setting or config tweak, is what actually adapts your play to how CS2 resolves a duel.