what-bethmo-said, mid-June'99 (part A) Date: Wed, 16 Jun 1999 15:11:52 +0100 From: Paul Barclay What Bethmo's Said, mid-April '99 through mid-June '99 [By Dave DeLaney, the rec.games.traging-cards.magic.rules NetRep] [As usual, this is NOT a Rulings post - it's merely a compilation of official answers bethmo has given to various questions over the last month or two, which didn't make it into a Rulings post (yet).] GENERAL 1) 6E does not, says bethmo, have "targetted permanents" in general. Consequences of this include: Local enchantments don't "target what they sit on" under 6E - they are simply 'attached to' them. Thus, the protection-from- wording has to note that the creature "cannot be the target of spells or abilities and cannot be enchanted by enchantments", instead of "cannot be the target of spells, abilities, or enchantments". Black Vise, Lifetap, and other spells that used to be "targetted spells which made a permanent" are now going to either not choose a player/opponent at _all_, and affect -every- applicable player/opponent [Bill Rose tells us that this will not unduly impact the multiplayer game environment...] - or will get rewording to "As ~ comes into play, choose a player/opponent. / ...". A couple of the copy cards [Clone, Doppelganger, Copy Artifact] will still be "targetted creature spells"; that's about it, though. Copy cards are expected to be Weird anyways... 2a) If a "damage shield" is set up that says "Damage that would be dealt -here- is dealt to this creature instead" ... and later, when it gets used, "this creature" is either not in play any more, or isn't a creature ... the shield fails to move the damage to the missing creature, but -does- get used up in the attempt. 2b) "Redirection" damage shields of this sort do _not_ remove 'combat damage' status from damage; combat damage that's edited by an en-Kor ability, for instance, to go to some other creature is combat damage when it's dealt to the other creature. 2c) "Redirection" shields of this sort, once the effect that creates them has resolved and made the shield, are no longer "targetted" in any way; gaining protection from the appropriate color _after_ the shield is in place won't stop the damage being moved onto "that creature" in any way. 3) Attackers or blockers that had combat damage -assigned to- them when combat damage went onto the stack ... and which are still in play, but no longer in _combat_, when combat damage resolves ... are still dealt their assigned damage normally. They don't "get it prevented because they're no longer in combat" or anything. [Attackers or blockers which are no longer _creatures_, or not in play, can't get damage dealt to them, of course.] 4) Rule 402.3 is _only_ talking about text stating the permanent it's written on "is" or "counts as" a specific -type- of card [permanent type, land type, creature type, etc.] or color; "This creature is unblockable" is an ability, and can be removed by Humility, since "unblockable" isn't a color or type, for instance. "Counts as a Dragon" would not be an ability, as would "is a red card" or "is an enchant creature". 5) If a creature type has multiple words, the creature counts as each of those words as a creature type: a Cleric Legend is type Cleric and type Legend, for instance, while a People of the Woods, if that type stayed the same, would now be type "People", type "of", type "the", and type "Woods" - four creature types. Most of the multiword-type creatures are getting updated to be single- word types; some are not. See Oracle 6E for details. 6) Abilities worded like "Whenever ~ blocks or becomes blocked by a creature, destroy that creature at time T" will destroy that permanent even if it's no longer a creature when the time comes. The ability triggers off blocking/being blocked by the creature, and never again checks whether it still -is- a creature, after that. 7a) Triggered abilities are never activated [and vice versa]. Triggered abilities worded like "When/ever /At