How to Fix a Cure-All Item Clearing Only One Status in Godot

A full-cure item should wipe poison, blind, and silence all at once. If it only clears one, you mutated the list while looping it. Here is how to clear them all.

How to fix it

1. Iterate a copy

Loop over statuses.duplicate() (or a snapshot) while removing from the original, so removals do not shift indices under the iterator.

2. Or rebuild the list

Alternatively build a new list of statuses to keep — those not covered by the cure — and assign it back, avoiding in-place removal entirely.

3. Refresh derived state

After clearing ailments, recompute any stat penalties and update status icons so the unit reflects its now-clean condition.

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.