Can you retreat a unit after damage has been assigned in a showdown?

Question

Accepted Answer

Yes — if you play Retreat after damage has been assigned but before that damage is actually dealt/resolved, you can return the unit to its owner's hand and prevent it from being dealt that damage. If the damage has already been dealt and resolved (the unit was killed or damage applied), it's too late to Retreat it.

You may play Retreat after damage is assigned but before the damage is dealt, returning the unit to its owner's hand and preventing it from taking that damage. If the damage step (the actual dealing/resolution of damage) has already finished and the unit has taken damage or been killed, playing Retreat afterward cannot undo that damage.

Damage is assigned (assignment step completes) but the damage-dealing instruction has not yet been resolved; players may respond with Reactions. You play Retreat as a Reaction (it may be played any time, even before spells and abilities resolve), returning your unit to your hand and channeling 1 rune exhausted. Because the unit moved to a non-board zone (hand), it is no longer the same game object and is no longer a legal target for any pending damage instruction that would hit it [359.3.e.4]. The pending damage instruction resolves and ignores targets that are no longer legal; the unit you returned is unaffected by that damage [359.3.e.5] [359.3.e.12].

If the damage has already been dealt/resolved (the damage step has finished) and the unit has taken damage or been killed, playing Retreat afterward cannot retroactively prevent that damage. If a spell or ability had already "chosen" the unit as a persistent target and the unit was only moved to a battlefield or base (a Board Zone), that targeting relationship may remain in some cases [FAQ:unleashed#22]; moving a unit to hand (a Non-Board Zone) severs that relationship outright [359.3.e.4]. If an effect attempts to reference the unit's Might or other properties after it has been moved to hand during resolution, those checks return null and calculations based on them are ignored [359.3.e.12]. If some other replacement or replacement-timing effect prevents you from playing Reactions at that exact moment, you may not be able to play Retreat despite the above assumptions.

The text of Retreat allows it to be played as a Reaction "any time, even before spells and abilities resolve," so you can use it in response to the assignment of damage before that damage is actually applied. When you return the unit to hand, it changes to a Non-Board Zone; per the rules, a game object that changes to or from a Non-Board Zone is no longer the same object and is no longer a legal target for effects that would hit the original object [359.3.e.4]. Therefore, when the pending damage instruction resolves, it will ignore that unit as a target and the unit will not be dealt the damage [359.3.e.5]. The game also treats checks on properties of that unit (like Might or location) as null once it is off the board, so any calculations based on the unit after it is returned are ignored [359.3.e.12]. The provided FAQs give analogous examples: moving units off the battlefield in response to multi-target damage prevents them from being affected as the ability resolves [FAQ:unleashed#20] and moving a unit to a non-board zone severs targeting relationships entirely [FAQ:unleashed#22]. Note the important timing caveat: if the damage step has already finished and the damage has been applied (or the unit has been killed and sent to trash), it is too late to use Retreat to avoid that damage.