How far back can the server rewind? Can it go back 500ms or 1 second?
Most servers cap rewind history to 1000ms (1 second) as a fixed ring buffer. This is an anti-cheat and abuse boundary: rewinding further would let exploits artificially extend effective latency, and servers must balance shooter fairness against preventing attacks. The buffer size is chosen to cover typical internet latencies; anything beyond that is treated as a missed shot.
Answered in
Time-Travel Fairness: How Servers Rewind for Lag CompensationWhy lag compensation rewinds the game world to when a shot was fired, and why victims experience the cost.
Read the full analysisOther questions this article answers
- Why does lag compensation exist at all? Can't players just aim for where the enemy is now?
- How does the server know what time the client fired the shot at?
- What happens to the player who gets shot from behind cover? Is that not unfair to them?
- What happens if the ring buffer doesn't have a snapshot for the timestamp on the packet?
More system design questions
- Why doesn't Google just run Dijkstra faster?
- What is a shortcut edge and when is it precomputed?
- How much space do shortcut edges take compared to the original graph?
- Can Contraction Hierarchies handle dynamic graphs like traffic or road closure?
- Why contract low-degree nodes first instead of high-degree ones?
- What is a CRDT and why does it matter for real-time collaboration?
- How do CRDTs handle concurrent edits without a central server referee?
- Why did Figma move from operational transforms to CRDTs?
Every answer on Crashtech is written by the editor of the article it comes from — never auto-summarised. Browse all answers or the System Design beat.