| Pyrulea: Cardlist | Visual spoiler | Export | Booster | Comments | Search | Recent activity |
| Mechanics | More Detail on The Set | Skeleton | Color Archetypes | Creative/World Building | Cycles |
|
CardName: Forge Golem Cost: 3 Type: Artifact Creature - Golem Pow/Tgh: 3/4 Rules Text: Forge Golem doesn't untap during untap steps. When a creature you control untaps, you may untap Forge Golem. Flavour Text: The discipline and cooperation is evident not only in Yaados military, but also in the workforce that supplies it. Set/Rarity: Pyrulea Common |
Code: CA01 Active?: true History: [-] Add your comments: |
Common artifact which works with unbound.
I like the unbound interaction on this idea.
Changed spot on skeleton
cardname: unnecessary ' ' removed
So the first restriction is just "Unless you control another creature"? (Actually, isn't that going to cause fights? Untap phase, I untap everything, not just the tapped things.)
I guess this is a combo piece; since it's pretty underwhelming untapping a creature with no abilities. Which makes it seem odd at common. But I guess that it fills a need for a middling creature that cares not about colour so anyone can snag it.
The current wording of this card would cause an infinite damage combo with Power of Fire. That's because Forge Golem will get a trigger to untap whenever the card itself untaps. Just activate the Power of Fire ability in response to the trigger.
You could write "Whenever another creature you control untaps." But that just means that two Forge Golems and a Power of Fire and any other tap outlet creates an infinite damage combo. Besides, even without the second Forge Golem, this would still untap 4 times if 4 other creatures untapped in the same untap step, since it would set up four separate triggers. And while that might be fair with Power of Fire, it has a nasty side effect of rewarding rules lawyering.
I'm not sure what the correct wording would be. But I think you want something closer to:
"During your untap step, if at least one other creature untaps, untap Forge Golem."
That locks the ability inside the untap step, one of the few places in the game where players can't respond to anything. And it removes the 'when' trigger, which puts an event on the stack that carries over to the next step. I'm not sure if 'if' or 'as' is more appropriate, though. Something, I'm sure, would get the job done.
Maybe...
> ~ doesn't untap during your untap step unless you control another tapped creature (not named ~).
... would suffice here? It obviously isn't exactly the same.
Another, harsher drawback that comes to mind could be:
> ~ doesn't untap during your untap step.
> If a creature you control would untap (and ~ is tapped), you may untap ~ instead.
Tons of annoying triggers though.
Depends quite what is intended; I guess. Letting a pair of them go whirr could be funny.
"Whenever one or more other creatures you control untap, untap ~." at least will prevent things from exploding during your untap step
subtype: added; ft: added