Two players in a shooter can both believe they fired first. Tick rate, the pace at which the server updates the authoritative world, decides which account the game accepts.
The server thinks in discrete steps
A game server does not process events continuously. It gathers inputs, advances the simulation and sends out a snapshot, repeating that cycle at a fixed rate.
Anything happening between two ticks is resolved at the next one, so the server's picture of the world is a series of frames rather than a smooth record.
A higher tick rate shortens the gap between those steps, meaning less action is compressed into a single update and positions are more current when they are sent.
Client frame rate and tick rate are unrelated
A player rendering at a high frame rate still receives world updates at the server's pace, and the client fills the gaps by interpolating between known states.
That interpolation is why smooth motion on screen does not guarantee accuracy. What is drawn between snapshots is an estimate, not information the server sent.
Players sometimes chase frame rate expecting a hit registration improvement it cannot deliver, because the limiting factor sits on the server side.
Lag compensation trades one unfairness for another
Servers rewind the world to reconstruct what a shooter saw when they fired, so that shots aimed at a visible target register despite network delay.
The consequence is that a player who has already moved behind cover on their own screen can still be hit, because the server judged the shot against an earlier state.
That is a deliberate choice. The alternative would require players to lead their shots by their own latency, which is far worse for most of the audience.
Tick rate is expensive at scale
Doubling the update rate roughly doubles simulation work and outbound bandwidth per match, multiplied across every server running concurrently.
Operators therefore balance responsiveness against hosting cost, and the same title often runs at different rates for casual queues and for competitive or event play.
Bandwidth constraints on the player side matter too, since higher rates increase the packet volume a household connection must handle without loss.
Consistency matters more than the number
A stable moderate tick rate produces better outcomes than a high rate that drops under load, because irregular updates make prediction less accurate.
Server population, region distribution and match density all affect that stability, which is why the same title feels different at different hours.
Reading tick rate as a single quality figure therefore misses the point. What players experience is the combination of rate, stability and the compensation model built on top of it.