>-2 should read "put a 1/1 black skeleton creature token onto the battlefield". "Create" is us being forward-minded with our templating. Pic related is the October FNM promo, so rumor is that Wizards is updating their token making wording to be more concise.
Probably have to do some weird Chain Veil-esque shenanigans to be 100% rules tight. >You may activate ~'s loyalty abilities a second time each turn, as though loyalty abilities have been activated this turn.
There might even be a better template for it than just using the standard Magic template. Dig around on the MSE forums. I remember a few years back, "Power Cards" were a big deal for 4e D&D, so maybe find a template for that?
Christian Roberts
I was wondering whether or not to change the effect to hatching maggots whenever it takes damage or whenever a creature goes to the graveyard.
Additional question: Does color have to be capitalized? i.e. "target Black creature" versus "target black creature".
Thomas King
Super types are always capitalized while colors or only capped if first word. So Creature not creature. See for reference on making tokens.
John Perry
Supertypes are not always capitalized. Subtypes are.
Aaron Howard
Color words aren't capitalized (unless they start a sentence, obviously). Subtypes, like Goblin, Equipment, Aura or Forest, are capitalized, but card types (creature, enchantment) and supertypes (legendary, snow, basic) aren't. Counters aren't capitalized either.
As an odd note, if you have to invert the condition, you hyphenate capitalized (types) only. So it's non-Goblin, non-Aura, nonbasic, nonartifact, and nonwhite.
So it's a "black Maggot that makes -1/-1 counters", or more completely >Whenever ~ is dealt damage, create a 0/1 black Maggot creature with "When this creature is dealt damage by another creature, put a -1/-1 counter on that creature."
Adrian Davis
Draft 02
Second version incoming.
Xavier Martinez
Draft 03
I now realize that "takes damage" might be better changed to "is dealt damage" if the source of damage is not meant to be specified any further.
Jaxon Lewis
Closer, but you're missing finer details. For example Not: >Whenever Maggot-Mother takes damage But: >Whenever Maggot-Mother is dealt damage Why? Because that's how Wizards writes it.
Not: >create a 0/1 black Maggot creature with the ability: But: >create a 0/1 black Maggot creature with Note the lack of the colon. Magic has a very defined meaning for colons in text, and they never show up outside of that meaning.
Also, you have a period outside the quotation marks at the end of the rules text. It goes inside, because its both ending the quote (defining the token's ability) and ending the rules text (defining the card's ability).
It's not that its about defining the source, its that objects/players never take damage, objects/players are always dealt damage.
