Sub-tick concepts in CS2
| Term | Meaning in this article | What it does not mean |
|---|---|---|
| Tick | A scheduled update step in the server simulation | Not the same as the player’s rendered frame |
| Sub-tick event time | Timing information associated with an input between regular updates | Not an infinite update rate or a guarantee of zero delay |
| Client feedback | Local visual or audio response shown while actions are processed | Not always identical to the final server-confirmed state |
| Network latency | Time for information to travel between client and server | Not removed by recording a more precise input time |
| Dated revisions | Valve has adjusted movement feedback and shooting consistency after launch | A patch note applies to its stated behavior and date, not every aspect of netcode |
Ticks and when an input occurs
A networked CS2 match maintains a shared game state through regular server updates, commonly described as ticks. A player’s input does not necessarily arrive at the server exactly on one of those boundaries. Sub-tick records timing information for an action within the interval, so the server can account for when movement starts, a shot is fired or a grenade is thrown rather than treating every action as if it occurred only at the next whole update.
Valve introduced sub-tick as a central CS2 architecture feature in March 2023. Its description framed the goal as more accurate action timing for moving, shooting and throwing. This is a description of how the game processes event time; it is not a promise that every real-world connection has equal latency or that all actions are simulated continuously. The normal server simulation and the information sent across a network still have finite update and delivery processes.
Input, prediction and server state
A player first provides an input through the local game client. The client can show immediate feedback while the action is sent to and evaluated by the server. The server maintains the authoritative match state and communicates updates back to players. Sub-tick timing is relevant to the timestamp associated with the action, while client prediction and visible feedback are separate parts of the overall experience.
This distinction helps explain why “I saw it happen” and “the server confirmed that exact result” can feel different in a networked match. A more precise event timestamp does not guarantee that every visual effect, animation, hit result and remote-player position will appear identically on every machine at every moment. Latency, packet delivery, prediction, rendering and later server updates remain part of the path. A player should not use sub-tick as a universal explanation for every missed shot or apparent movement discrepancy.
Connections to movement, shooting and throws
For Movement, input timing describes when movement begins or changes, while movement rules determine acceleration, speed and accuracy. Sub-tick does not itself explain how quickly a player stops, jumps or changes direction; those behaviors belong to the movement system. Counter-Strafing and Movement Inaccuracy cover the player-facing decisions that follow.
For weapon fire, sub-tick relates to the recorded timing of a shot, but weapon accuracy, Recoil, Spread and damage determine other parts of the result. For a grenade, throw timing is only one part of the trajectory; the grenade type, release input, physics and map surfaces still matter. See Grenade Throws and Smoke Interactions. These systems meet in one round but should not be collapsed into a claim that the timing architecture controls every combat outcome.
Feedback and responsiveness
The visible and audible feedback shown immediately after an input is not itself the whole server result. Early CS2 updates adjusted when feedback from sub-tick inputs, including movement acceleration and muzzle flashes, was rendered, and synchronized random shooting spread between clients and servers by default. Those changes illustrate that presentation and consistency can be tuned alongside event timing. They do not mean that the original system stored no action time or that the later change removed all delays.
Valve’s public explanation says tick rate no longer matters for moving, shooting or throwing in the intended sub-tick model. Read that as the design goal for event timing, not as a guarantee that server load, latency, packet loss, frame rate or every community server configuration is irrelevant. A player may still experience delay or inconsistent feedback because the full client-server path includes more than a single timestamp.
Dated CS2 changes
Sub-tick is an evolving CS2 system rather than a launch setting that never changes. On November 8, 2023, Valve updated how visual and audio feedback from sub-tick input was rendered and synchronized random shooting-spread values between clients and servers by default. This addressed feedback timing and consistency around the system’s operation.
A June 2023 update also described sub-tick movement as more precise and less “floaty” in response to player feedback, and tuned the camera view-punch effect during shooting to align with other sub-tick shooting effects. Later CS2 release notes continue to describe specific movement, prediction and shooting consistency adjustments. Record each change against its patch date rather than rewriting it as a universal definition of sub-tick. Patch Archive tracks those dated changes.
What sub-tick does not guarantee
Sub-tick does not make the server update infinitely often, eliminate ping, guarantee that a shot hits because the crosshair briefly crossed a target, or ensure that two clients render the same frame at the same instant. It does not make movement accuracy, recoil or grenade behavior identical across every weapon and surface. It records event timing as part of CS2’s architecture; the rules and state changes associated with each action still matter.
When reviewing a disputed moment, separate the player’s input, local feedback, server-confirmed event, weapon accuracy and network conditions. A single clip may show a timing disagreement without identifying its cause. Use a dated CS2 update when describing a specific fix, and avoid importing tick-rate claims or implementation details from older games or unofficial experiments as if they were current Valve guarantees.
Counter-Strike 2 scope
This entry describes sub-tick only as used in Counter-Strike 2. It focuses on Valve’s public explanation and dated CS2 updates, while avoiding undocumented implementation claims and assertions about unrelated Counter-Strike versions. Technical behavior can be revised by patches; current dated notes take precedence for a specific change.
Asynchronous game-delta transmission (June 29, 2023)
The June 29, 2023 Limited Test update made the sending of game-delta frames asynchronous. The stated purpose was to reduce CPU use on the dedicated server’s main thread and thereby reduce the probability of dropped ticks. This was a server-networking implementation change, not a promise that dropped ticks could never occur or a replacement of Sub-Tick input timing. The note does not quantify performance gains or describe client-side behavior.
Network optimization and shot-random-seed separation (March 30, 2023)
The March 30, 2023 Limited Test update listed multiple network-traffic optimizations and corrected shooting random-seed separation between server and client code. This records a synchronization/implementation fix in the CS2 test build; the patch does not state what the optimizations were, quantify latency or server load, or claim that all later networking behavior was unchanged.
Lag-compensation adjustments (September 13, 2023)
The update made various lag-compensation adjustments but gives no parameter, threshold, example or measurement. It establishes system iteration during the Limited Test, not a quantified latency improvement or a changed hit-registration rule. See Sub-tick for timing context.
Lag compensation favors lower-latency players (September 14, 2023)
The update rebalanced lag compensation to favor players with lower latency. That wording identifies the direction of the adjustment, but provides no formula, threshold, sample scenario or exact effect on a shot. The previous day’s Limited Test notes had described general lag-compensation adjustments; this September 14 entry is a separately dated rebalance with an explicitly stated preference. It should not be translated into a guarantee that lower-ping players always win a disputed interaction or a specific numerical advantage. The patch also fixed two dropped-item presentation problems: dropped grenades could be invisible, while dropped bombs and weapons could appear in the wrong location. The notes do not describe causes or pickup-rule changes.
Interpolation parameter adjustment (September 5, 2023)
The September 5 update adjusted interpolation parameters but provides no exact values, affected setting, or scenario. The note is distinct from hit-registration rules and from the next day’s separate buy-menu and grenade fixes. Do not infer a particular latency benefit from this line alone.