Client marks action timestamp locally before UDP datagram transit.
Late hit visibility depends on movement vectors, interp & tick cadence.
Symptom
What happens during a "shot behind cover" exchange?
Consider a simple duel around a corner between Player A (peeking out) and Player B (holding an angle and stepping back into cover). Three independent clocks sit between them: Player A's round-trip delay to the server, the server's simulation tick cadence, and Player B's round-trip delay plus client interpolation buffer. When Player A swings out and shoots on their own screen, their shot packet takes half their round-trip time to reach the match host.
Meanwhile, Player B may already have begun strafing back behind the wall locally. Because modern shooters implement lag compensation (rewinding enemy hitboxes on the server back to where Player A saw them when pulling the trigger), the server validates Player A's hit against Player B's earlier position and sends a damage/kill confirmation to Player B. By the time that confirmation reaches Player B's client, Player B has already walked another step behind cover on their monitor—making the kill look impossible in a 15-second clip.
Notice what was absent in that entire sequence: packet loss on Player B's line. Even if Player B has a spotless 18 ms fiber line, the combined travel time of Player A's outbound shot, server tick quantization, and Player B's inbound snapshot creates a visible rewind gap whenever two players fight across unequal paths.
How tick interval, interpolation, and lag compensation stack
Tick rate vs sub-tick vs interpolation buffer (IND)
Players often treat "128 tick," "64 tick," "20 Hz," and "sub-tick" as magic bullets that solve every delay symptom. Each term actually addresses a different slice of the timeline:
- Server tick rate (Hz): How many times per second the server steps world physics and emits world snapshots. At 20 Hz (used by some battle-royale lobbies), one tick takes 50 ms; at 64 Hz (CS2), one tick takes 15.625 ms; at 128 Hz (Valorant), one tick takes 7.8125 ms.
- Sub-tick timestamping: Instead of snapping a mouse click to the next tick boundary, sub-tick packets record the exact fraction of the tick when you clicked or released a movement key. That improves shot-timing fairness for the shooter, yet it still cannot outrun the speed of light or eliminate peeker's advantage while waiting for packets to cross the internet.
- Interpolation buffer (IND): Because real networks never deliver UDP frames with mathematically identical spacing, your own game client intentionally delays rendering remote players by roughly 1–2 ticks (often shown as IND around 15–22 ms in games like Overwatch 2) so characters glide smoothly instead of teleporting when a packet arrives 4 ms late.
The diagnostic takeaway is simple: when your own IND or jitter buffer sits calmly at its baseline and no packet loss appears, dying right as you step behind a corner is an inherent byproduct of multiplayer reconciliation. Conversely, when your IND climbs sharply or movement snaps unpredictably outside gunfights, your local path or home uplink is struggling to feed smooth frames to the client.
Reconciliation timing vs real network faults
Use this matrix to verify whether your clip shows normal lag-compensation asymmetry or an actionable connection problem on your side.
| What your clip shows | HUD graphs at that second | Likely explanation | Should you change home gear? |
|---|---|---|---|
| Hit behind wall right after peeking back | Flat ping, calm IND, zero loss | Server lag compensation resolving opponent's earlier view | No. Router, DNS, or cables will not change opponent ping. |
| Your own shots register 200+ ms late on every duel | Ping flat at 120+ ms on distant hub | Server/region selection or cross-continent party queue | Check selected region/Data Center before touching local gear. |
| Enemies freeze mid-air then teleport across rooms | IND climbs sharply, jitter spikes, or loss % rises | Unstable packet arrival on your link, Wi-Fi, or ISP path | Yes—pause home uploads and compare wired Ethernet first. |
| Screen stalls during abilities; gunshots feel unresponsive | Frame time / SIM spikes; network graphs stay calm | Client CPU/GPU frame pacing or shader compilation | No—address thermals, FPS cap, and background apps. |
When to switch measurement method
When should you stop blaming tick rate and run a network check?
Switch to a controlled wired check whenever your own HUD shows rising interpolation delay, jitter bars, or packet loss—especially if movement snaps occur while nobody else is peeking you. Those symptoms mean packets arriving at or leaving your machine are delayed or dropped before server reconciliation even starts.
For game-specific overlays, inspect the CS2 telemetry guide (ping/misdelivery vs frame time), the Overwatch 2 NetGraph guide (IND vs SIM), or the Apex Legends guide (20 Hz simulation and HUD icons). If wired Ethernet still shows recurring packet drops or ping spikes, use the packet-loss note and our local ping log reader to log your gateway alongside a public resolver.
Common questions about tick rate and peeker's advantage
Can my router fix dying slightly behind cover when my own ping is flat?
No. Lag compensation rewinds the world to match the shooter's view at the moment they fired. Even if your wired connection is completely spotless, an opponent playing from a higher latency or swinging a corner first can register a valid hit before your screen receives their position update.
Why does sub-tick not eliminate peeker's advantage?
Sub-tick timing records exact input timing within a tick interval so firing feels responsive to the shooter, but packets still travel across the physical network. The defender still sees the peeker only after the peeker's packet reaches the server and the server snapshot travels to the defender.
When does interpolation delay (IND) point to my own connection instead of lag compensation?
When your own client raises its interpolation buffer above baseline during normal movement—accompanied by jitter spikes, rubberbanding, or loss bars on your screen—incoming snapshots are arriving unevenly on your end of the path.
Has Fix My Ping published an in-game tick-rate lab trace for this note?
No. This field note explains published multiplayer netcode mechanics and gives you a blank diagnostic comparison table. No synthetic or in-game packet capture is published on this page.
Editorial log
November 17, 2026. First publication by Jay Fan to stop players with flat, zero-loss connections from blaming their router or ISP for multiplayer lag compensation and corner-peeking timing. Corrections: redmedia24@yeah.net.