← Duel Masters English

Reference · 31 Aug 2026

Rulings that catch people out

Duel Masters has no stack. It resolves simultaneous effects by a fixed priority order instead, and that difference produces a set of interactions that look wrong if you are reasoning from Magic. Here are the ones worth knowing before they cost you a game.

Rule numbers refer to the official Comprehensive Rules, version 1.50, 10 April 2026.

There is no stack

When several effects trigger at once, they do not go on a stack and resolve in reverse order. They resolve in a fixed sequence:

1Shield Triggers, turn player first 2Shield Triggers, non-turn player 3Everything else the turn player controls, in whatever order they choose 4Everything else the non-turn player controls

One effect resolves completely before the next begins — but the turn player keeps priority throughout. If a turn-player effect triggers while the non-turn player is working through their queue, the current effect finishes, then the turn player's new trigger is handled next, ahead of anything the non-turn player still has waiting. Only after that does the non-turn player resume.

What this means in practice You cannot respond to a spell. There is no window between announcement and resolution. Every "instant-speed" interaction in this game comes from the shield zone, because that is the only place a card can act on your opponent's turn.

Rules 101.4, 101.5, 506.3e

Multiple Shield Triggers at once

Three shields break together and two of them have Shield Trigger. What order? Your choice. Since a 2020 rule change, shields entering hand from a single break-event arrive simultaneously, so you declare which Triggers you are using and resolve them in any order you like. Official rules revision notice
Can I use a Trigger creature's "when it enters" ability before resolving the other Trigger? No. For a spell, the Shield Trigger ability covers casting it. For a creature, it covers summoning it — and nothing further. If another declared Trigger is still pending, the creature's enter-the-battlefield ability waits. Official rules revision notice

"When it is entering" versus "when it entered"

This is the distinction that produces the most confusing board states, and Japanese card text marks it with two characters that are easy to skim past.

JapaneseTimingType
Before the creature arrivesReplacement effect
After the creature arrivesTriggered ability
I control two different cards that punish cheating creatures into play. Which one applies? The one that reads — "as it is entering." That is a replacement effect: it applies before the event happens, and once replaced, the event never occurred at all. The card that reads never gets to trigger, because nothing ever entered. Consequence of the replacement-effect rules

A Magic player will recognise replacement effects. The trap is that the two wordings look nearly identical in Japanese and are frequently both present on the board at once, since cheat-punishing cards are a staple of the format.

Blockers redirect, they do not stop

The reminder text is precise about this and it matters:

What does Blocker actually do? Tap this creature and change the attack's target to it. It is a redirect, not an interception — and it costs you a tap. Official reminder text
Can a creature that "cannot be attacked" block? Yes. "Cannot be attacked" means it cannot be declared as a target when the attack is announced. Redirecting an attack onto it afterwards is a different operation, and it is legal. Community ruling, consistent with the redirect wording
Can a creature that "cannot be chosen" be attacked or blocked? Yes. Being unselectable applies to abilities and effects that choose targets. Attacking and blocking are not that. Official PLAY'S rules FAQ

Three separate protections that a Magic player would file under "hexproof" and expect to behave the same way. They do not.

Summoning sickness has an exception you will meet immediately

A Shield Trigger creature arrives during my opponent's attack. Can it block that attack? Yes. Blocker beats summoning sickness — the rules state this explicitly. A Trigger creature with Blocker can block the very attack that put it into play. Comprehensive Rules, summoning sickness section

This is a large part of why attacking is risky. A shield you break can produce a blocker that stops the same attack.

Where PLAY'S differs from paper

The digital game is a re-implementation, not a port, and a handful of interactions resolve differently. These are documented by players rather than by Takara Tomy, and are worth treating as observations rather than rules.

Two identical creatures with a "when it would be destroyed" effect battle each other. What happens? In PLAY'S, the turn player's survives and the non-turn player's is destroyed. In the paper game, the correct resolution is reportedly that both are destroyed. Whether the digital behaviour is deliberate or a bug has never been stated. Mikegamo, "Fine rules and behaviour in PLAY'S"
The general warning If you learn a ruling from a video, a wiki or a blog, check when it was written. Duel Masters rulings change — one well-known 2020 revision altered how a whole class of interaction resolves, and older explanations of it are still online and still confidently wrong. Japanese guides say this to their own readers; it applies double in translation.

Where to check

The other half of this Everything above is about what happens once the game is running. The rules that govern what you are allowed to build in the first place — deck size, the copy limit and the cards that override it, the three zones outside your forty, and the caps on hand and board — are on their own page.

Sources

Rule numbers and official wording are translated from the Japanese and can be checked against the PDF. Community rulings are marked as such. Terms are defined in the glossary.

Corrected 31 August Two errors. The article cited version 1.49 when 1.50 has been out since April, and it invented a rule number — 101.4a — that does not appear to exist; the relevant clauses are 101.4, 101.5 and 506.3e. More seriously, the description of mid-resolution triggers was backwards. It said a newly triggered effect waits its turn. Rule 506.3e says the opposite for turn-player effects: they are handled immediately after the current effect finishes, ahead of anything the non-turn player still has queued. That is a difference that changes outcomes, and it is now stated correctly.

Corrections and questions

If something here is wrong, please say so — that is the most useful thing you can do with this page. Comments use GitHub, so you will need an account, and everything posted lives in this site's own repository rather than on a third-party service. No tracking, no ads.