What causes a tutorial soft-locking when the player pauses mid-step?

Pausing the game also halts the tutorial controller, but the resume path does not re-arm the step's listeners or timers, so after unpausing the step sits frozen and never completes.

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 Tutorial Soft-Locking When the Player Pauses Mid-Step

Quick answer: Exempt the tutorial controller from the pause, or on resume re-arm the current step's listeners and timers so it continues exactly where it stopped.

If pausing during a tutorial step leaves it permanently stuck, the pause froze the tutorial logic and resuming did not bring it back. Either keep the tutorial running through pause or explicitly restore the step's state on resume.

How to fix it

1. Exempt the tutorial from pause if needed

If the step relies on timers, consider keeping the tutorial controller processing during pause. In Godot, set the controller's process mode so it survives the paused tree.

2. Re-arm on resume

If the tutorial does pause, on unpause re-attach the current step's listeners and restart any per-step timers, so it picks up rather than sitting dead.

3. Test pause at every step

Pause and resume in the middle of each step during QA. Steps that depend on a one-shot timer started before the pause are the usual soft-lock culprits.

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.