Deploy the Gatewatch and Mirrorpool interaction

Maveric78f

When I play Deploy the Gatewatch while Mirrorpool is in play, Mirrorpool triggers on the first creature instead of triggering on the spell Deploy the Gatewatch.

pacha

Mirrorpool has always worked like that when you use it with a spell that casts a creature (or take control of if, or call it from the graveyard, or summon tokens).

James13

Normal resolution of the stack.

Spell "Call the Gatewatch" is cast and goes on the stack:
Creature summoned -> resolves (mirrorpool triggers here as this is the first actually finished card)
Creature summoned -> resolves
Creature summoned -> resolves
"Call the Gatewatch" resolves

Similarly we can use a creature with additional on cast effects like "Birthing Hulk" as an example. If Mirrorpool was in play here:

Creature card "Birthing Hulk" goes on the stack triggering on summon eldrazi tokens. Before birthing hulk resolves:
Eldrazi token summoned/resolves (mirrorpool triggers here as it's the first finished summon)
Edlrazi token summoned/resolves
Then finally Birthing Hulk finishes resolving and is complete.

Basically, you need to keep in mind that additional effects will always finish triggering first before the card that triggered them. Any further nested triggers then also gain priority in turn. This can in fact lead to some quite useful things if you are aware of that concept.

Maveric78f

Once again, inconsistent with paper MtG... And it's pretty annoying, when you can't use Not forgotten, Devil's Playground, nor deliriumed Descend upon the Sinful to trigger Mirrorpool into Deploy the Gatewatch.

moogus

James13 wrote:

Normal resolution of the stack.

Spell "Call the Gatewatch" is cast and goes on the stack:
Creature summoned -> resolves (mirrorpool triggers here as this is the first actually finished card)
Creature summoned -> resolves
Creature summoned -> resolves
"Call the Gatewatch" resolves

Similarly we can use a creature with additional on cast effects like "Birthing Hulk" as an example. If Mirrorpool was in play here:

Creature card "Birthing Hulk" goes on the stack triggering on summon eldrazi tokens. Before birthing hulk resolves:
Eldrazi token summoned/resolves (mirrorpool triggers here as it's the first finished summon)
Edlrazi token summoned/resolves
Then finally Birthing Hulk finishes resolving and is complete.

Basically, you need to keep in mind that additional effects will always finish triggering first before the card that triggered them. Any further nested triggers then also gain priority in turn. This can in fact lead to some quite useful things if you are aware of that concept.

This isn't accurate and not how the stack works. Mirrorpool says: "When you cast a spell, ..." NOT when a spell resolves.

The stack resolution is:
Cast Call the Gatewatch -> effect goes on stack
Mirrorpool triggers from casting a spell -> effect goes on stack
Nothing left to go on stack
Mirrorpool resolves
Call of the Gatewatch resolves

Your description is also misleading because the creatures entering the battlefield are part of the resolution of Call the Gatewatch. If a card had a triggered ability for when a creature enters the battlefield (including that creature), that would go on the stack.

tldr; previous poster's description of stack resolution is incorrect, and 2) how MtG:PQ handles the stack is definitely inconsistent with the paper version.

Plastic

moogus wrote:

... MtG:PQ ....is definitely inconsistent ....

Just keep this in mind at all times while playing and you'll save yourself a lot of headache trying to sort things out. That's what I've learned from playing this past year at least.

blacklotus

It doesn't matter MtgPQ descend doesn't work like in paper mtg. Almost all the mtgPQ cards don't follow paper mtg stats exactly.

if I want to complain, the current creature battlefield setup makes all the weeny creature buff spells like "Might of the Masses" quite useless. But I am not. Just play game with the new mtgPQ rules.

Remember this: mtgPQ is a mobile match3 game with mtg flavour, not mobile paper mtg.

gulgoth

Also if you summon a creature that spawns a token creature when it comes into play, you get a copy of the token rather than the main creature, which seems to not follow the same logic.

Ohboy

moogus wrote:

James13 wrote:

Normal resolution of the stack.

Spell "Call the Gatewatch" is cast and goes on the stack:
Creature summoned -> resolves (mirrorpool triggers here as this is the first actually finished card)
Creature summoned -> resolves
Creature summoned -> resolves
"Call the Gatewatch" resolves

Similarly we can use a creature with additional on cast effects like "Birthing Hulk" as an example. If Mirrorpool was in play here:

Creature card "Birthing Hulk" goes on the stack triggering on summon eldrazi tokens. Before birthing hulk resolves:
Eldrazi token summoned/resolves (mirrorpool triggers here as it's the first finished summon)
Edlrazi token summoned/resolves
Then finally Birthing Hulk finishes resolving and is complete.

Basically, you need to keep in mind that additional effects will always finish triggering first before the card that triggered them. Any further nested triggers then also gain priority in turn. This can in fact lead to some quite useful things if you are aware of that concept.

This isn't accurate and not how the stack works. Mirrorpool says: "When you cast a spell, ..." NOT when a spell resolves.

The stack resolution is:
Cast Call the Gatewatch -> effect goes on stack
Mirrorpool triggers from casting a spell -> effect goes on stack
Nothing left to go on stack
Mirrorpool resolves
Call of the Gatewatch resolves

Your description is also misleading because the creatures entering the battlefield are part of the resolution of Call the Gatewatch. If a card had a triggered ability for when a creature enters the battlefield (including that creature), that would go on the stack.

tldr; previous poster's description of stack resolution is incorrect, and 2) how MtG:PQ handles the stack is definitely inconsistent with the paper version.

I think you'll find the game more predictable if you stop thinking of it as an mtg game and more of it as a puzzle quest game with mtg flavour.