Tick rate explained: what 64-tick, 128-tick and Counter-Strike 2's sub-tick actually mean

Tick rate is how often a game server updates the shared match. Riot built Valorant around 128-tick servers and spent years keeping them there; Valve's sub-tick system in Counter-Strike 2 tries to make the number matter less.

Finn Tamati

Two glowing paths meeting at a maze corner, marked by evenly spaced rings of light

Every competitive shooter has the same small tragedy in it. You're holding an angle, crosshair parked where the enemy has to appear, and somebody runs around the corner and drops you before you've seen them. Then the kill cam shows a version of events you don't recognise. Some of that is the network. Some of it is a number players argue about with unusual passion for something they can't see: the tick rate.

A tick is one update, or frame, of the shared game world on the server. Riot's engineers describe part of what happens in each one: the server checks the game's state against what each player's machine last knew and packages up the changes to send out. A 64-tick server runs 64 of those frames a second; a 128-tick server runs 128, so by Riot's arithmetic each frame has to be finished in about 7.8 milliseconds. More ticks means the server's picture of the match is refreshed more often, which matters most in exactly the moment above, when two players meet at a corner and fractions of a second decide it.

Two of the best-known tactical shooters have answered the tick question in different ways, and the differences say a lot about what each studio thinks the problem is.

Riot bought the bigger number, and paid for it

Riot's case for 128-tick servers in Valorant was set out in August 2020 by Brent Randall, an engineer on the game's Gameplay Integrity team, in a post on Riot Games' own news site. Valorant, he wrote, is about taking positions and holding them, and holding becomes impossible "if other players can run around a corner and kill the defender before the defender can react due to latency". That latency, he explained, is partly the network and partly the server tick rate. To give defenders time to react, Riot decided Valorant needed 128-tick servers.

The bill came in CPU time. Randall wrote that the team had to process an entire server frame within 7.8125ms, and that doing so naively meant a single game would occupy a whole CPU core. Riot wanted to offer 128-tick for free rather than as a premium service, so it set itself a target of better than three games per core, which on its usual 36-core hosts meant 108 games, or 1,080 players, per machine. Allowing for overhead, that left a budget of 2.34ms per frame. When the work started, a frame took 50ms.

Closing that gap was mostly patience: profiling, budgets for every subsystem, and some lovely small economies. The server, Randall explained, checks a shot by rewinding player positions and animations to the moment it was fired, and Riot found it only needed to compute those animations every fourth frame, cutting that cost by 75%.

Keeping the number honest has been its own job since. In a March 2023 developer post on the Valorant site, engineer Aaron Cheney described the worst slowdown since launch, in August 2022, hitting games with more than 10 players, such as custom and esports matches. The first sign came from a 22-player playtest, where players "noticed server tick fluctuations". The culprit was a single line of code from an Unreal Engine 4.26 upgrade. After the fix and further work, he wrote, "Since patch 5.07, 99.3+% of server frames have met our strict 128-tick requirements."

Valve tried to make the number matter less

Counter-Strike came at it from the other side. In CS:GO, as Valve's Counter-Strike 2 team told PC Gamer's Rich Stanton in an October 2023 interview, players were split between 64 and 128-tick servers, and tick rate affected the game itself, including how grenades were simulated and weapon spray patterns. Players found it hard to switch between the two.

Valve's response in Counter-Strike 2 was sub-tick. Rather than settle the old argument by picking a winner, the team said, its sub-tick servers "separate gameplay from tick boundaries", with the goal of "a consistent, tick-independent experience that's better than CS:GO's 64 or 128 tick experience". One visible side effect: rifle sprays in CS2 look slightly smaller than in 64-tick CS:GO, because Valve tried to match 128-tick behaviour where it could.

The launch didn't settle the matter. Players shared clips of hits that didn't register, and PC Gamer asked whether sub-tick was working as intended. Valve's answer was that those clips showed a different bug, an animation and hitbox mismatch when looking down, and that for the most part the system worked, while conceding that as more people played, some systems weren't reaching their goals.

What the number does and doesn't tell you

It's tempting to read tick rate as a score, where bigger wins. The two studios' own words suggest something more modest. Riot treats a high, steady tick rate as a fairness promise to the player holding an angle, and has spent years keeping it. Valve treats the tick as something gameplay shouldn't depend on at all.

Neither approach takes the network out of the equation. Riot's own explanation puts the latency behind a lost peek down to both the network and the tick rate, so a faster server only fixes part of it. And a fast server only helps if it hits its target every frame, which is the quiet point of Cheney's post: the number on the box is a promise, and keeping it is work that never really finishes.

So when the kill cam shows a corner you don't remember, tick rate is part of the answer, rarely all of it. The rest is distance, connection and the ordinary unfairness of being the one who was standing still.

Sources

More from Xarmo News