Community

Invoke Prejudice

Nether Void

Invoke Prejudice

counter that spell unless that player pays {oX}, where X is its converted mana cost.

Jul 3, 2012 -- 11:29PM, DEATHKILLER2001 wrote:

What about the (now missing) interaction between Tallowisp and Threads of disloyalty ? The printed version of each cards makes it look like Tallowisp can be used to search for the Threads, but the oracle text on Threads makes that interaction impossible.

Shouldn't Threads instead be worded 

Enchant creature

You control enchanted creature.

Threads of Disloyalty may only enchant creatures with converted mana cost 2 or less

to avoid confusion?

I know it's more wordy, but it really bugs me that I can't use these cards together. It's a cool interaction and there's no good reason to kill it.

It's true that Tallowisp no longer interacts with all the same things it did before, but I think the cleaner wording of Auras is still worth it (by a significant margin).  The entire point of the enchant ability is to specify what the Aura can enchant (and what it can target while it's a spell).  So having an enchant ability that says one thing but a further ability that says it can really only enchant a subset of that would be redundant.

And Threads of Disloyalty isn't the only card that would be affected.  There are over a dozen other card that also had "enchant creature" in the type line and an ability that imposed a further restriction but which now have that restriction as part of their enchant ability.  I strongly oppose giving these cards ugly errata, just for the sake of restoring their interaction with Tallowisp (and Rootwater Shaman ).

Jul 4, 2012 -- 5:54AM, Soular wrote:

615.11

This rule covers damage that can't be prevented and how damage prevention shields still are applied to such damage, even though those shields won't actually prevent damage. Now, rule 615.7 makes it clear that a damage prevention shield is reduced by actually preventing damage, not just by the act of applying that shield. So, I'm adding a clarification to rule 615.11 that says your existing damage prevention shields will be intact even after you're dealt damage byMalignus, for example.

I'm a bit confused as to what is the purpose of the original rule 615.11 :

615.11. Some effects state that damage "can't be prevented." If unpreventable damage would be dealt, any applicable prevention effects are still applied to it. Those effects won't prevent any damage, but any additional effects they have will take place.

 
Is it for cards like Inquisitor's Snare  to do the rest of their effect (destroying the creature)? Any other examples?

 It allows cards like Inquisitor's Snare to use any additional effects that the card has even though the damage isn't prevented.  Now, effects that would prevent damage dealt to a source stay on when a creature whose damage can't be prevented damages it.