How to Fix the Run Timer Continuing During the Pause Menu

If pausing to grab coffee ruins your daily-run time, the timer is using real time, not game time. Accumulating only while unpaused keeps the recorded time fair.

How to fix it

1. Accumulate only while running

Add to the run timer using the scaled delta that goes to zero when paused, or skip the accumulation entirely while the pause flag is set.

2. Avoid wall-clock differencing

Do not compute elapsed time by subtracting timestamps captured at start and end, since that includes paused time; sum per-frame game deltas instead.

3. Verify against the leaderboard rules

If the timer feeds a daily leaderboard, confirm the definition of run time (with or without pauses) is consistent so scores are comparable.

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.