Let’s stop pretending this is just “netcode issues.”

Let’s be more specific, because this clearly isn’t just a “feels bad” issue — it points to a deeper problem in how server reconciliation is currently handled.

What we’re experiencing strongly suggests that the lag compensation window is too forgiving, to the point where higher latency clients are being over-prioritized.

From a low latency perspective (20–30ms), the gameplay symptoms are consistent:

- Taking damage after reaching cover (server rewinding too far back in time)

- Inconsistent hit registration despite confirmed shots on target

- “Super bullets” effect where damage is applied in a single frame

- Losing trades even when shooting first with clear visual confirmation

This indicates that the server is resolving engagements based on delayed client states that no longer match the current reality of the low ping player.

In other words, the reconciliation model appears to favor historical client input over present server state.

If that’s the case, then the system isn’t just compensating for latency — it’s overcorrecting.

At a technical level, this raises a few critical questions:

- What is the current lag compensation window (in ms), and is it dynamically scaled?

- How is server authority balanced against client-side hit validation?

- Is there any cap to prevent excessive backward reconciliation for high latency players?

- What is the effective server tick rate under load, and does it degrade in real matches?

Because right now, the outcome of gunfights feels decoupled from real-time player input.

This isn’t just a balance issue — it’s a synchronization issue between client perception and server resolution.

If left unaddressed, this will continue to erode player trust, especially among players with stable low latency connections — the very group that should be experiencing the most consistent gameplay.

To put it simply:

Right now, it feels like the game rewards delayed information over accurate information.

And that is fundamentally the opposite of what a competitive FPS should do.