What causes skipping level-up rewards when several levels are gained at once?

The level-up handler runs once per XP grant and recomputes the new level, but it only applies the reward for the final level instead of every level crossed.

How do I catch this when it only happens for some players?

Capture it automatically from the player's device with the full stack trace, the device and OS, the build, and a breadcrumb trail of what they did. That turns a vague complaint into a specific, reproducible issue you can fix without owning the hardware it happens on.

How to Fix Gaining Several Levels at Once but Only Getting One Level-Up Reward

Quick answer: Loop the level-up routine while remaining XP exceeds the next threshold, granting each level's rewards individually before moving to the next.

A big XP reward that jumps the player two levels should give two sets of rewards, not one. Process level-ups one at a time in a loop. Here is the fix.

How to fix it

1. Loop per level

After adding XP, while the total meets the next level's threshold, increment the level by one, subtract that threshold, grant that level's rewards, then check again.

2. Grant rewards inside the loop

Award stat points, abilities, or unlocks for each level individually within the loop, so no intermediate level is skipped on a multi-level gain.

3. Recompute thresholds each iteration

Look up the next threshold fresh on every loop iteration, since the requirement usually grows per level and a cached value would mis-count the jumps.

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 Godot 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.

Most of the time the fix is small. Seeing the failure clearly is the part that actually costs you.