| Namekkos: Cardlist | Visual spoiler | Export | Booster | Comments | Search | Recent activity |
| Mechanics | Political Groups | Locations | Naming Convention | Limited archetypes | Skeleton |
|
CardName: Gift of Anima Cost: 1u Type: Enchantment - Aura Pow/Tgh: / Rules Text: Enchant artifact As Gift of Anima enters, put five +1/+1 counters on enchanted artifact. Enchanted artifact is a creature with base power and toughness 0/0 in addition to its other types. If it doesn’t have clockwork, it has clockwork. (Whenever it becomes tapped, remove a +1/+1 counter from it at end of turn.) Flavour Text: Set/Rarity: Namekkos Uncommon
Gift of Anima
  Enchant artifact
As Gift of Anima enters, put five +1/+1 counters on enchanted artifact. Enchanted artifact is a creature with base power and toughness 0/0 in addition to its other types. If it doesn’t have clockwork, it has clockwork. (Whenever it becomes tapped, remove a +1/+1 counter from it at end of turn.) |
Code: CU03 History: [-] Add your comments: |
Putting this on an artifact creature (with base p/t and no clockwork) seems a bit beyond blue's capabilities.
If the artifact creature has no counters on it, it becomes a 5/5. That's totally in blue. Ensoul Artifact
How do the multiple clockwork abilities interact if this e. g. animates a Spring-Loaded Key? Does it lose two charge counters and two +1/+1 counters for each tap?
(Checks mechanics page)
Oh, so only two +1/+1 counters.
(Reads further.)
You really shouldn't need to create an exception to rule 113.2c. If you don't want separate instances to trigger separately, don't make it a triggered ability. It's a keyword, hard code it into the turn structure.
Triggered abilities work a certain way and create expectations that this keyword ability breaks, so it shouldn't be a triggered ability.
Theoretically it could be a turn-based action where you remove a counter from each tapped permanent with clockwork during your cleanup step, but I wasn't sure if I liked how that worked with untap effects. I really didn't want the downside part to stack, but I thought using a delayed trigger would still be the most intuitive way to do that
I'm removing the exception and just accepting that this and Itezoe, Clockwork Kirin will lose counters extra fast. This rattling around in my brain did remind me that it needs to trigger during the cleanup step rather than the end step, at least
For this card at least you could try the Delay-trick: "If it doesn't have clockwork, it has clockwork." Certainly reads funny. This was meant for spell effects, not static abilities. I really have to think about how that would work.
You could still have the turn-based effect "remove a counter for each time it has tapped this turn". Technically you don't even need to remove the delayed trigger, just the first trigger:
That way the creation of the delayed trigger is part of a static ability (as such redundant). There is still the creature/noncreature thing, but I already forgot how that supposedly works since yesterday. ^^
I considered the templating from Delay, but I really didn't like how it sounds. "If it doesn't have X, it gains X" is pretty reasonable, but it gets weird as a static effect on an aura