You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a card with an ETB such at Cloudblazer or Wall of Omens is enchanted with an ability suppression effect from Lignify, Frogify, or Darksteel Mutation, blinking/flickering the creatures causes the enchantment to correctly drop off, but the ETB does not trigger.
Rule 400.7 should mean the creature reenters as a new instance with no connection to it's previously enchanted state.
The text was updated successfully, but these errors were encountered:
{1}{U}
Enchantment — Aura
Enchant creature
Enchanted creature loses all abilities and is a blue Frog creature with base power and toughness 1/1. (It loses all other card types and creature types.)
{1}{W}
Enchantment — Aura
Enchant creature
Enchanted creature is an Insect artifact creature with base power and toughness 0/1 and has indestructible, and it loses all other abilities, card types, and creature types.
Yeah, this fails for ExileThenReturnTargetEffect (e.g. Cloudshift) although it does pass for ExileReturnBattlefieldNextEndStepTargetEffect (e.g. Turn to Mist).
The effects from BecomesCreatureAttachedEffect that remove abilities and change subtypes don't appear to get cleaned up in time.
I thought game.getState.processAction(game) would account for that. Needs more research.
When a card with an ETB such at Cloudblazer or Wall of Omens is enchanted with an ability suppression effect from Lignify, Frogify, or Darksteel Mutation, blinking/flickering the creatures causes the enchantment to correctly drop off, but the ETB does not trigger.
Rule 400.7 should mean the creature reenters as a new instance with no connection to it's previously enchanted state.
The text was updated successfully, but these errors were encountered: