What causes fleeing a battle still applying enemy damage?

Your escape succeeds but the current turn keeps resolving, so enemy actions already queued this round still execute and damage the fleeing party.

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 Fleeing a Fight Still Letting Enemies Counterattack in Unity

Quick answer: On a successful escape, immediately halt the turn loop, cancel all remaining queued actions, and transition straight to the field without resolving pending enemy turns.

Pressing Run and succeeding should get the party out clean, not eat a free round of enemy hits. If it does not, the battle loop keeps running. Here is how to bail out.

How to fix it

1. Short-circuit the turn loop

When escape succeeds, set a fleeing flag and break out of the action-resolution loop before any further queued actions run.

2. Clear the action queue

Discard all pending enemy and ally actions for the round so nothing resolves after the player has left the fight.

3. Transition immediately

Play the escape jingle and load the field scene right away; do not wait for the round to end or the victory/defeat check to run.

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.

Ship the fix, watch the signature disappear from the next build. That's how you know it's really gone.