How to Fix an All-Targets Spell Hitting Dead Enemies and Wasting Damage in Unity

A Fire-All spell should only hit enemies that are still alive. If it pelts corpses and overflows damage, the target list is stale. Here is how to rebuild it at cast time.

How to fix it

1. Query live targets at resolve

When the spell executes, gather targets by filtering the current enemy group for !IsDead, instead of reusing a list from selection time.

2. Re-evaluate per row

For row-targeting skills, recompute which units occupy the targeted row at resolve time, since deaths can empty or shift a row.

3. Skip cleanly if none remain

If no valid targets remain when the spell resolves, end the action without wasted hits and proceed to the next turn.

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.