How to Fix a Quest Tracker That Updates Only on Reopen

Killing enemies advances a quest, but the HUD counter stays at the old value until you open and close the quest log. The tracker only refreshes on open. Here is how to fix it.

How to fix it

1. Emit a progress signal

Have the quest manager emit a quest_progress_changed signal whenever an objective count updates, carrying the quest id and new values.

2. Subscribe the HUD tracker

Connect the HUD tracker to that signal and update only the affected line, so progress shows live without reopening any menu.

3. Refresh on quest swap too

Also update when the tracked quest changes or completes, so switching the active quest immediately reflects the new objective text.

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.