Battle Destruction Is Determined at Damage Calculation but Performed at End of the Damage Step

A monster losing a battle is "determined to be destroyed by battle" during damage calculation,

but the destruction is not actually carried out until the End of the Damage Step. There is a

real sub-step gap between the two. A monster that **leaves the field before that performance

sub-step — banished, bounced, shuffled away by a card effect — is never destroyed by battle**,

and "destroyed by battle" triggers do not fire.

See the Damage Step structure in Battle and Damage Step. This is a

battle-specific timing rule, not the generic "leaves the field = new card" principle (that is

file 75 / file 16);

the doomed-by-battle status is Damage-Step bookkeeping checked only at the performance sub-step.

The sub-step sequence

1. Perform damage calculation — ATK/DEF compared, battle damage applied. At this instant the

game determines which monster(s) will be destroyed by battle. They are not sent to the

GY yet.

1. After damage calculation — a monster determined to be destroyed sits in a locked state:

it cannot be targeted, cannot change battle position or have its ATK/DEF changed, its Continuous

Effects stop applying, optional Quick Effects cannot be activated, and it cannot be returned to

the hand/Deck by effects.

1. End of the Damage Step — monsters still on the field and still flagged are now sent to

the GY (destroyed by battle); "when/if destroyed by battle" triggers become available here.

Removed before the performance sub-step → not destroyed

If a card effect removes the doomed monster from the field (banish, bounce, shuffle to Deck) in

the window before the End of the Damage Step performs the destruction, the monster is **not

destroyed by battle at all**. Because it was never destroyed by battle:

• "When this card is destroyed by battle" / "destroyed by battle and sent to the GY" triggers

cannot activate.

• If the same monster later returns to the field (e.g. a banish-then-return effect within the

same turn), it returns as an ordinary monster with no pending destruction — by the time the

performance check runs it is simply a monster on the field, not a flagged one.

Worked example. A monster loses the battle and is "determined to be destroyed by battle."

Before the End of the Damage Step, a card effect banishes it (and it returns to the Monster

Zone before the destruction step). — It is **no longer considered determined to be destroyed by

battle and stays on the field**. (Konami official Q&A, db.ygoresources.com qa/24347.)

This is method-agnostic: any removal (banish / bounce / shuffle) by any effect that can act in

that window prevents the battle destruction; whether the monster later returns is irrelevant to the

fact that it "was not destroyed by battle."

Judge calls to watch for

• "It lost the battle, so it's destroyed" — only at the End of the Damage Step. If it left the

field first, it was not destroyed by battle, and its battle-destruction triggers don't fire.

• Distinguish determined to be destroyed (at damage calculation) from performed destruction

(End of the Damage Step) — effects acting in between can change the outcome.

• Don't explain a returned monster's survival with "it's a new card" — the operative rule is the

destruction-performance timing, independent of card-identity doctrine.

Sources

• Konami official "Damage Step Rules" (yugioh-card.com) and Yu-Gi-Oh! Perfect Rulebook 2017

(pp. 188-193), via Yugipedia Damage Step — destruction determined at damage calculation,

performed at End of the Damage Step; monsters can be removed by effects before that.

• db.ygoresources.com Q&A 24347 (2026-06-11): a monster determined to be destroyed by battle that

is banished and returns before the destruction step is no longer destroyed and stays on the field.

https://db.ygoresources.com/data/qa/24347