How Lag Compensation Works in Online Shooters

Lag compensation is the technique that makes shooting feel fair in online shooters, ensuring that when you aim at a target and fire, you hit it—even though your latency means the server sees a slightly different moment. Understanding how the server rewinds time to check hits is key to fair networked shooting.

The problem: you shoot at what you saw, but the server sees later

In an online shooter, by the time your shot reaches the server, the target has moved—because of your latency, the server's current state is ahead of what you saw when you fired. Without compensation, you'd have to lead targets by your latency, aiming where they'll be rather than where they are, which feels broken. Lag compensation solves this by rewinding: the server keeps a history of recent world states, and when your shot arrives, it rewinds the world to the moment you actually fired (based on your latency), checks whether your shot hit the target as it was positioned then, and registers the hit accordingly. This means you hit what you aimed at—the target as you saw it—because the server checks the hit against the rewound state matching your view, compensating for your latency. Rewinding the server's world to when you fired, and checking the hit against that state, is how lag compensation makes shooting fair despite latency.

The tradeoff: lag compensation can create 'shot around a corner' moments. Lag compensation makes shooting fair for the shooter, but it has a tradeoff that affects the target: because the server rewinds to when the shooter fired, a target who has already moved to safety (in their own view) can still be hit, because in the rewound state they were exposed. This produces the 'I got shot around a corner' or 'shot after I was already behind cover' experience, where the target was hit based on a past state even though they'd moved. This is the inherent tradeoff of lag compensation: it makes shooting fair for the shooter (you hit what you saw) at the cost of occasionally unfair-feeling deaths for the target (hit based on a past position). Tuning lag compensation involves balancing this—how far back the server will rewind, how to handle the edge cases—to make shooting feel fair without making the around-the-corner deaths too egregious. This is a fundamental tension in networked shooters with no perfect solution, but lag compensation, despite its tradeoff, is what makes online shooting feel responsive and fair for the shooter, which is why it's standard in online shooters. Understanding both how it works (rewinding to the shooter's moment) and its tradeoff (target hit based on past state) is essential to building and tuning fair networked shooting.

Plan for the parts you can't see

Once a game leaves your machine, a lot of what happens to it becomes invisible by default. Players run it on hardware you don't own, hit problems you never reproduced, and most of them never tell you — they simply move on. The gap between 'it works for me' and 'it works for everyone' is where a surprising amount of churn quietly lives.

So plan to see what you otherwise couldn't. Watching real players, capturing the bugs and crashes they hit with the context to fix them, and paying attention to where they drop off all turn invisible problems into ones you can actually act on — which protects the reviews and retention everything else depends on.

Consistency beats intensity

Indie development is a long game, and it rewards steady, sustainable effort more than heroic bursts. A little progress made consistently — on the game, on the marketing, on the community — compounds in a way that last-minute sprints never do. The developers who finish and find an audience are usually the ones who kept showing up, not the ones who worked themselves into the ground for a week and then burned out.

Build a pace you can sustain, and protect it. Momentum is fragile and expensive to rebuild, so steady forward motion is worth more than any single intense push.

Let real players be the judge

It's remarkable how differently real players behave from how you imagine they will. The tutorial you think is obvious confuses them; the feature you agonised over goes unnoticed; the thing you almost cut becomes their favourite. None of that is visible from inside your own head, which is why watching real people play is the single highest-leverage thing most developers under-do.

Watch without intervening, resist the urge to explain, and pay attention to what players do as much as what they say. Their confusion and their choices are data, and acting on that data is what turns a game that works for you into one that works for everyone.

Polish where players actually look

Polish is not evenly valuable. Players form an impression in the first minutes and spend most of their time in the core loop, so effort spent there returns far more than effort spread thin across content few people reach. The opening, the moment-to-moment feel, and the things every player touches are where polish converts directly into how good the game feels.

Be deliberate about it. Make the first impression strong and the core interactions satisfying before widening out, because a great core with less content almost always beats a sprawling game that never feels good to play.

Scope is a decision, not an accident

Almost every overscoped game got that way one reasonable addition at a time, with no single decision ever feeling like the mistake. The finish line recedes a little with each new feature, and because the project always feels nearly done, the developer rarely notices how far the goal has drifted until they're exhausted and the game still isn't out.

Treat scope as something you actively decide rather than something that happens to you. Write down what the finished game contains, make every addition a conscious trade against that, and keep most new ideas in a backlog where they belong — because a small game you finish beats a large one you abandon.

Lag compensation rewinds the server's world to when the shooting player fired, checking the hit against what they saw—so you hit what you aimed at despite latency. The tradeoff is the occasional 'shot around a corner' death for the target.