How to Fix Battle-Pass Tier Progress Resetting on Reconnect

If a brief disconnect makes a player's battle-pass level snap backward, your reconnect logic is overwriting good local progress with an old server value. Reconciling to the higher total fixes it. Here is how.

How to fix it

1. Model progress as monotonic

Store season progress as a total XP that only ever increases, so reconciliation is a simple max rather than a fragile merge.

2. Reconcile to the maximum

On reconnect, compare local and server totals and adopt the larger, then push it to the authoritative side so both converge upward.

3. Queue unsynced gains

Buffer XP earned while offline and replay it to the server on reconnect with idempotent ids, so nothing earned during the gap is lost or double-counted.

4. Grant tier rewards by total

Derive unlocked tiers from the reconciled total and grant any tier whose reward is unclaimed, so a temporary rollback never strands a reward.

Catching the ones you can't reproduce

The hardest version of this to fix is the one you can't reproduce — it only happens on a player's hardware, OS, driver, or save state, under conditions that simply aren't present on your machine. A report that says “it crashed” or “it froze” gives you nothing to act on, so the bug survives release after release while quietly costing you players.

Automatic error capture closes that gap. Each failure arrives with its full stack trace, the device and OS, the build number, and a breadcrumb trail of what the player did right before it broke, so even a failure you have never seen becomes a specific, reproducible issue. Fold identical failures into one signature ranked by how many players each hits, and your worklist sorts itself worst-first instead of arriving as a stream of vague complaints.

This is where a tool like Bugnet earns its place. Its SDK captures every error automatically with the full stack trace plus device, OS, memory, build, and game-state context, folds duplicates into one grouped issue with an occurrence count, and ties each to the build it first appeared on — so you fix the problem that hurts the most players first and confirm it is gone when its signature disappears from the next release.