Welcome to the Official Redemption® Message Board!
Yep, because those card affect u, not him so the Protect doesn't stop that, the battle just ends in a stalemate.
Not really, because they still have to push their numbers over your's to win regardless.
Pretty sure you can't ignore Gideon because you cannot target him. Just gotta find the ignore ruling somewhere around here.
No, that's just it.You don't target AUTO/Gideon. You can't; it can't be negated. But with that up, your opponent can't ignore/be immune to him.
Ok I have been gone for a while but when did the search function die?
Admittedly, but what the heck has ignore or immunity that's CBN?
No, the ignore/immunity DOES have to be CBN to get past Iron Pan... right?
Why is it that you do not interrupt the CBP abilities and then prevent it when you negate? Isn't it an interrupt first and a prevent second?
From the 10th Anniversary Rulebook:In the definition of Negate:"Negate is the same as 'interrupt and prevent' combined. A negate ability interrupts a special ability, and then prevents that special ability for the rest of the battle."
And when did this happen? Because doing that just makes everything that much more complicated.
Interrupt for a moment undoes what is done, prevent undoes what is not yet done, and negate permanently undoes what is done or yet to be done (depending on the card).
Wait a minute.Minister Polarius, are you saying that you CAN negate CBP before it is played?
so you interrupt the inability to be prevented, prevent it, and then if/when it reactivates the negate happened prior to the CBP effect.
Negate functions exactly like interrupt+prevent
Remember, CBP isn't affected by cards played BEFORE it. A negate after the fact can stop it.
Quote from: Redoubter on May 16, 2012, 05:56:51 PMRemember, CBP isn't affected by cards played BEFORE it. A negate after the fact can stop it.Which includes a continues negate, like Iron Pan, correct?
The reason you can negate a CBP is because CBP is not inherently CBN, so you interrupt the inability to be prevented, prevent it, and then if/when it reactivates the negate happened prior to the CBP effect.
Right, that's what I thought. It's just the way that Minister Polarius put it...Quote from: Minister Polarius on May 16, 2012, 03:36:32 PMThe reason you can negate a CBP is because CBP is not inherently CBN, so you interrupt the inability to be prevented, prevent it, and then if/when it reactivates the negate happened prior to the CBP effect....sounds like you CAN interrupt the CBP, then prevent it.Which is what I thought we determined to NOT be the case.
...sounds like you CAN interrupt the CBP, then prevent it.
Actually, I am exactly correct. Negate functions exactly like interrupt+prevent, but is not defined that way.
Quote from: Minister Polarius on May 18, 2012, 01:47:14 PMActually, I am exactly correct. Negate functions exactly like interrupt+prevent, but is not defined that way.If it's not defined that way, then don't say that it is that. This leads to the type of confusion we get in this thread.Negate is defined all by its lonesome as a completely different ability, and that makes it simpler to explain as well. If you try to mix them together, you get two pages of confusion.
The biggest problem with saying "negate" is "undo" is that it leaves out the prevent aspect.