Expedition of the Guild resurrection priority is a fixed order the game applies when heroes fall: Revive first, then Heal, then Damage. A healer is brought back only after everyone who can re-enter the fight has done so, and damage dealers come back last — which is why a fight that has already lost its Tank gets worse in a specific, predictable order.
Expedition of the Guild resurrection priority: Revive, Heal, Damage
The August 2026 update set the order explicitly with improved battle resurrection logic, and it works like this:
- Revive first. The heroes who can get back up and re-enter the fight are the first ones brought back.
- Heal second. Once the fight-capable members are up, the healer is restored.
- Damage last. Damage dealers are the last to come back.
That ranking is not arbitrary. It follows what a party needs most in the middle of a fight: someone who can take hits again, then the person who keeps everyone alive, then the people who end the fight. Restoring the healer before the Tank would give you a party that heals a front line that is not there.
What each step of the order means
Read the order as a diagnosis tool. If the fight is going wrong, the order tells you what has already gone wrong:
- Damage dealers still down. They are last in the queue, so a fight that reaches this state has been losing for a while. You are in a losing position, not a recoverable one.
- Healer down but damage dealers up. The revive step has already run, so the healer is next. This is the moment where the party is still recoverable.
- Tank down. The boss has moved on to its next target in the priority list, and the front line has to be restored before anything else. The aggro and targeting guide covers what a dead Tank does to the rest of the party.
The practical consequence is that keeping the Tank alive is worth more than keeping a damage dealer alive, because the Tank is first in the enemy's targeting order and the party is weakest without a front line.
Why the order was changed
The order exists in its current form because the earlier behaviour was replaced. The change made revival follow the order above instead of running on its own schedule, which is what makes the state of the party readable at a glance: you can tell how bad a fight is by looking at who is still on the floor.
There was also a build bug around a hero waiting to revive at a dungeon portal stage: the hero could disappear and be removed from the character list. That was a defect in that build rather than a change to the priority order, but it is worth knowing about if a hero ever goes missing from your roster.
The revive and death counters
The achievement list tracks both sides of this, which makes them a rough measure of how your fights are going:
| Counter | Achievement |
|---|---|
| 100 revives | Arise, My Warrior! |
| 500 revives | I Fight for You, My Lady! |
| 100 deaths | Corpse-Run Rookie |
| 500 deaths | Corpse-Run Master |
Revive counts are a normal sign of a long campaign rather than a mistake — heroes go down, and the order brings them back. Death counts are the number to watch, because a rising death count alongside a flat revive count means the party is losing members it cannot replace, and the fix is on the setup side rather than the revival side.
Which heroes you put in each role determines how often you get to use that order at all, and the classes and roles guide covers how the roster splits across Tank, DPS and Healer.