If I {reverberate} say an {incinerate} and my opponent {cancel} the incinerate what then happens to the reverberate. Cast in order incinerate reverberate then cancel.
The original incinerate is canceled and the copy still goes through. If the cancel was cast before the reverberate, then the incinerate is cancled and reverberate fizzles.
Quote from: JaCe BeLeReN on May 20, 2012, 06:38:07 PM
The original incinerate is canceled and the copy still goes through. If the cancel was cast before the reverberate, then the incinerate is cancled and reverberate fizzles.
With my limited understanding of the stack, you would still get one of the spells, no matter when the cancel was played.
If it was played
Incinerate > reverberate > cancel
Then the first and second spell are on the stack, the cancel has to choose which one to remove when it resolves first and then the one left resolves.
If it was played
Incinerate > cancel > reverberate
A. The reverberate resolves first as a copy of the first spell incinerating something. The cancel then resolves removing the first.
B. the reverberate resolves canceling the cancel and then the original incinerate resolves.
Quote from: Wally on May 20, 2012, 07:01:44 PM
Quote from: JaCe BeLeReN on May 20, 2012, 06:38:07 PM
The original incinerate is canceled and the copy still goes through. If the cancel was cast before the reverberate, then the incinerate is cancled and reverberate fizzles.
With my limited understanding of the stack, you would still get one of the spells, no matter when the cancel was played.
If it was played
Incinerate > reverberate > cancel
Then the first and second spell are on the stack, the cancel has to choose which one to remove when it resolves first and then the one left resolves.
If it was played
Incinerate > cancel > reverberate
A. The reverberate resolves first as a copy of the first spell incinerating something. The cancel then resolves removing the first.
B. the reverberate resolves canceling the cancel and then the original incinerate resolves.
Oops... Yes, your right
But if you cancelled the {Incinerate} then {reverberate} wouldn't have a target to copy. How would you still get either the original or copied {Incinerate}?
Quote from: BoyMac on May 20, 2012, 08:10:46 PM
But if you cancelled the {Incinerate} then {reverberate} wouldn't have a target to copy. How would you still get either the original or copied {Incinerate}?
Because the if you cast reverberate in response to the cancel, then it copies incinerate, but the original dies, but if they cast cancel in response to reverberate, then the incinerate dies, the the reverberate has no target and also dies.
Quote from: JaCe BeLeReN on May 20, 2012, 08:15:15 PM
Because the if you cast reverberate in response to the cancel, then it copies incinerate, but the original dies, but if they cast cancel in response to reverberate, then the incinerate dies, the the reverberate has no target and also dies.
Please refer to the sticky on how the stack works. Also once the spell is paid for, it's target is chosen and it is put on the stack, it will resolve if the original is there or not. If it is a copy it is on the stack as an {incinerate}.
You still get one version of it, the original or the copy. The cancel removes the other one.
None of the spells happen until both players pass without casting anything else. Everything just keeps stacking up on the stack until you let them resolve and then u can cast stuff again between each spell resolving if u want
If the original spell that {Reverberate} targeted is countered before {Reverberate} resolves, then it will not resolve for lack of a target.
As the original poster was asking, the {Cancel} will counter the {Incinerate} and the {Reverberate} will have nothing to copy.
Quote from: TJKoer on May 20, 2012, 06:33:10 PM
. Cast in order incinerate reverberate then cancel.
But Jester doesn't the reverb go on the stack before the cancel, forcing the cancel to target the reverb?
Quote from: Imdowd80 on May 20, 2012, 11:01:49 PM
Quote from: TJKoer on May 20, 2012, 06:33:10 PM
. Cast in order incinerate reverberate then cancel.
But Jester doesn't the reverb go on the stack before the cancel, forcing the cancel to target the reverb?
The {cancel} can target any spell on the stack that the player wants it to.
I forgot reverberate doesn't create a copy until it resolves so while it's on the stack it's waiting to make a copy of the targeted spell. Once reverberate resolves then it creates that copy and puts it on the stack waiting for it to resolve as well.
Quote from: BlackJester on May 20, 2012, 11:04:57 PM
Quote from: Imdowd80 on May 20, 2012, 11:01:49 PM
Quote from: TJKoer on May 20, 2012, 06:33:10 PM
. Cast in order incinerate reverberate then cancel.
But Jester doesn't the reverb go on the stack before the cancel, forcing the cancel to target the reverb?
The {cancel} can target any spell on the stack that the player wants it to.
Well that makes a world of difference. My home games just got a little more interesting.