What causes a puzzle timer continuing to run during pause?

The countdown accumulates real elapsed wall-clock time (unscaled) regardless of the pause state, so pausing the game does not stop the clock.

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 a Puzzle Timer Continuing to Run During Pause

Quick answer: Drive the timer from scaled game time and set the time scale to zero on pause, or explicitly gate the timer update behind a paused flag so it stops accumulating.

A timed puzzle must freeze its clock when the player pauses. If the countdown keeps dropping during the pause menu, your timer reads unscaled real time. Use scaled time or guard the update with the pause state.

How to fix it

1. Drive the timer from scaled time

Accumulate the countdown using Time.deltaTime (scaled), and set Time.timeScale = 0 on pause so the timer naturally stops with the rest of gameplay.

2. Or gate the update on pause

If you intentionally use unscaled time elsewhere, wrap the timer's decrement in an if (!isPaused) check so it never advances while paused.

3. Resume cleanly

On unpause, restore the time scale (or clear the flag) without applying the elapsed pause duration, so the player loses no time for pausing.

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

The errors you never hear about are the ones quietly costing you players. Visibility turns them into a worklist.