CardName: Blessed Beast Cost: 3GG Type: Creature - Beast Pow/Tgh: 5/5 Rules Text: _Blessed_ - Blessed Beast enters the battlefield with an Aura token attached to it. It has enchant creature and "When enchanted creature becomes the target of a spell or ability an opponent controls, counter it. If you do, sacrifice this Aura." Flavour Text: Set/Rarity: [Assorted] Card Repository Uncommon |
Code: History: [-] |
See Blessed Soldier.
Iterating.
I really think you need the reminder text for blessing to be about 1/5th the current length.
This is an annoyingly solid creature, seems perfectly legit.
There is no reminder text. And there is no "blessing".
Fun (loosely related) Fact: 1/5th for e. g. the seconf ability would be about this long: "When enchanted creature is" and that's contentless drivel and doesn' account for the other half of the text not being shortened at all.
If I replaced the ability word with a keyword following the (rejected by others) simplified wording, I'd use:
> Grace (this enters the battlefield with an Aura. When a spell targets enchanted creature, sacrifice the Aura to counter the spell.)
which is still more than half the length (and sacrifices some functionality that is not strictly necessary). Can you imagine going even shorter?
Blessing (Counter the first spell that targets ~)
The whole 'having an aura token' thinkg is the complexity.
Or you can do as another set tried, and put all the complex wording on the token; but that has other nastiness which I dislike.
> Vitenka: "Blessing (Counter the first spell that targets ~)"
The proposed wording masks funtionally relevant information: The ability must remain recognizable as triggered ability.
The proposed wording also does not provide a marker and hence has memory issues over multiple turns.
The proposed wording further comes with a nonobvious drawback and can be a hindrance. In a hexproof world, would I want the shroud variant of the ability?
.
I'm trying to find an actual wording not a line to scribble on a playtest card to remember the idea.
Mm, sure. This is a good argument for just using hexproof instead.
The full horrendous thing can live in the comprules (e.g. "Use a token to represent this") but the long rules are currently more than a card full. Which kinda makes this not a mechanic you can splash onto too many cards; which suggests it doesn't really need to be a full mechanic.
Oh, blessed would just mean "enters with an Aura token" if I use it as an ability word - the individual token would be dependent on the card e. g. the totem armor token is an alternative Aura.
I wonder whether the ability that I've written out (or a shorter variant) would be worth a keyword similar to totem armor.
The idea is to weaken hexproof to address problems. Obviously this mechanical space is not evergreen worth.
Once again: using tokens and counters cannot be hidden in the rules for something like this since tokens and counters can be manipulated and the interaction needs to be apparent. Hence morph and embalm using overlays and such rather than counters.
Variant: Graceful Gargantuan