CS2 sub-tick updates: what Valve changed and what the tick rate still controls

[ice]

CS2 sub-tick updates: what Valve changed and what the tick rate still controls

Tick rate was the number Counter-Strike players argued about for a decade. A 128 tick server was treated as a straight upgrade over 64, and matchmaking felt worse because it ran at the lower figure. Counter-Strike 2 answered that with sub-tick updates, and the argument came back in a different shape. What follows is what Valve documented, what third parties reported after launch, and what still runs on ticks.

What a tick was

The server used to evaluate the world in discrete intervals. In CS:GO matchmaking that happened 64 times a second, roughly every 15.6 milliseconds, and on 128 tick servers roughly every 7.8 milliseconds. Every tick, the clients and the server exchanged positions and actions and agreed on what the world looked like. A click that landed between two ticks waited for the next one, and in a game where a rifle round crosses a site in a few frames, that wait could decide a duel.

What sub-tick changes

Valve's description is short. Sub-tick updates are the heart of Counter-Strike 2, and instead of evaluating the world in intervals, the servers know the exact instant that motion starts, a shot is fired, or a grenade is thrown. The company's claim that follows is that tick rate no longer matters for moving, shooting or throwing, so your shots and grenades behave the same on any server.

The mechanism, as the community has described it, is a timestamp. Each input the client sends carries a timecode, so when the server builds the next game state it can collect inputs from every player, order them chronologically and simulate the actions in that order.

What still runs on ticks

This is where the argument lives. Valve's promise covers movement, shooting and grenade throwing. It does not say the server stopped updating the world on a tick.

Third party coverage reports that CS2's official servers still update at 64 ticks per second, that FACEIT ran 128 tick CS2 servers and Valve stopped it, and that players still complain about dying after they have taken cover. Dexerto's explainer attributes those deaths to several factors at once rather than one: ticks, ping, packet loss and interpolation. Sub-tick fixes the moment your input is registered. It does not fix how long the world takes to reach your screen.

Practical rules

1. Stop shopping for tick rate. Per Valve, your moving and shooting are equally responsive at any tick rate, and there is no client setting that changes the architecture.
2. Treat ping, packet loss and your interpolation settings as the things you control. They are on the list of factors behind deaths that feel unfair.
3. Do not read sub-tick as an anti-peek patch. The complaint about dying after turning a corner is a latency and update problem, and Valve never claimed sub-tick solved it.
4. Test any setting change on the same kind of server you normally play on. Server side behaviour is not something a config file reaches.

FAQ

Do I need to change any settings for sub-tick?
No. It is a server side architecture, not a client option, and Valve describes it as running regardless of tick rate.

Are CS2 servers 128 tick?
Third party reports say official servers run at 64 ticks and that a third party attempt to run 128 tick CS2 servers was shut down. Valve's own claim is narrower: tick rate no longer matters for movement, shooting and throwing.

Does sub-tick remove peeker's advantage?
Valve never said it would. The shot around the corner complaints are attributed to ticks, ping, packet loss and interpolation together.

Is tick rate completely irrelevant in CS2?
For the three actions Valve lists, yes. The server still updates the world on a tick, which is why complaints about animations and spray timing keep coming up.

Sources
[1] Counter-Strike 2 official page (Valve)
[2] Counter-Strike 2: Moving Beyond Tick Rate (Valve)
[3] Dexerto: What is sub-tick in Counter-Strike 2?
[4] cs.money: What is subtick in CS2 and how it works