Pyromancer Ascension and Copy spells

Asked by kevint1999 8 years ago

Lets say I have an active Pyromancer Ascension out. I play a regular old cantrip, such as Serum Visions, then I play Twincast to copy Serum Visions. Do I end up with 4 copies of Serum Visions? One being the original casted, another from pyromancer ascension, one being the Twincasted and the final one being the copy of Twincast?

Also, do these apply to all other copy spells such as Reverberate and Increasing Vengeance?

erabel says... Accepted answer #1

Short answer: Yes.

Long answer: ...also pretty much yes. The Ascension is active. You cast Serum Visions, Ascension triggers, you maintain priority, you cast Twincast, Ascension triggers. Assuming no one else does anything, what will happen is:

  1. The Ascension trigger to copy Twincast resolves. Assumably you target Serum Visions with the copy.
  2. Twincast copy resolves. You get a copy of Visions.
  3. Copy of Visions number 1 resolves.
  4. Original Twincast resolves. You get a copy of Visions.
  5. Copy of Visions number 2 resolves.
  6. Ascension trigger to copy Serum Visions resolves. You get a copy of Visions.
  7. Copy of Visions number 3 resolves.
  8. Serum Visions resolves.
August 5, 2015 3:31 a.m.

kevint1999 says... #2

Thanks! I thought so, but as you've shown, the steps are complicated. I'm trying to assemble a storm-esq deck using this kind of interaction :P

August 5, 2015 3:34 a.m.

Devonin says... #3

Note however, that the end result of all this in terms of storm is a storm count of -2- for the original Serum Visions and Twincast.

Storm counts how many spells have been cast this turn, and you're only casting one copy of serum visions and one copy of twincast. All the rest are creating copies of spells directly on the stack, which aren't cast.

August 6, 2015 11:38 a.m.

kevint1999 says... #4

Yeah, I got that. It's Manamorphose I'm actually copying, to create a sustainable mana generation while drawing cards to eventually allow me to repeat and storm

August 6, 2015 12:56 p.m.

This discussion has been closed