|
CardName: Iceheart Wretch Cost: {4}{U}{U} Type: Creature - Giant Wizard Pow/Tgh: 4/4 Rules Text: When Iceheart Wretch enters the battlefield, target creature you control gains "whenever this creature deals combat damage to an opponent, carve a blue rune." (Create a blue Rune enchantment token with "{U}, Sacrifice this enchantment: Tap or untap target creature.") Flavour Text: Set/Rarity: temporary storage Common |
History: [-] Add your comments: |
See Balten Herald.
Is this a common that permanently grants another creature a complicated (nonkeyworded) ability? Why? At common you go for the simple incarnation of the mechanic: "When ~ ETBs, carve a blue Rune."
Even at uncommon this would rather itself have the triggered ability than grant it indefinitely, maybe grant the ability "until ~ leaves the battlefield".
The creature was intended to give the a creature the ability to carve a blue rune on damage only UEOT. I forgot to include "UEOT" in the text. Admittedly, I just wanted to throw stuff on the card so it didn't just say "when ~ EBTs, carve a blue rune."
On a six mana 4/4 the additional hoops of playing this precombat, needing an additional creature, attacking with it and evading blockers in turn seven... is a lot to ask for if all you get in return is Twiddle.
That's another reason I suggest a simple ETB trigger. A 4/4 for
could have "When ~ ETBs, carve two blue Runes." considering Heavy Infantry.
I could see this being an uncommon, that grants all creatures the rune-carving saboteur ability.
As a rule of thumb: If you add complexity to a card just to not use the most simple incarnation of an ability, you might not be designing for common anymore.
I wholeheartedly agree with you vand see my error. My only goal however was to feature the blue rune.