Multiverse Design Challenge: Recent Activity
| Multiverse Design Challenge: Cardlist | Visual spoiler | Export | Booster | Comments | Search | Recent activity |
| All challenges | Upcoming Challenges | Make a new design challenge! | All challenges (text) |
Recent updates to Multiverse Design Challenge: (Generated at 2025-05-13 19:12:49)
Soul sisters are too easy, I guess.
Added Yazt, Phantom General. Decided to make a creature that could easily take out half of your opponent's life. The leader of an Illusion "Army" that would act only as a decoy for Yazt himself. His power is on the low side, but I mean, with giving him at least five turns of Unblockable, I figured that two power was a safe place to start.
Added Keeyaw, Aven Singlicator.
For Challenge # 111, and yet another creature that become Legendary by default. I'm not really sure if this guy is printable, considering his two abilities won't interact in a way most players think they will (I guess, he mostly flickers your stuff. That being the case, the activation might be too high? He does protect himself...)
Alex got it. Hurting fetchlands and land-based LD was the goal.
Mmm. I guess that is a strong interaction.
This isn't that much of a hoser, really. It makes Creeping Tar Pit and Kessig Wolf Run a little more expensive to use, but those were only activated when the controller had plenty of mana. What this is most effective against is Terramorphic Expanse, Flooded Strand and friends.
I added Isamiashi, Devoted Clerk to the lineup, because it occurred to me that there are other reasons why Legendary is necessary, besides stacking, confusion or flavor. Jack saved me from having to create a card to express the idea of 'because you want to abuse the Legendary rule intentionally.' Isamiashi adds 'it was going to happen anyway' to the list of reasons.
It's a good stab at the idea of 'Fine once. Egregious in multiples'. But I suppose it does hose a small selection of cards, which is normally fine. I don't think Tsabo's Web would usually be reprintable, but if Wizards felt it was necessary, I could see them reprinting it.
It's true, maybe once a turn is plenty, but what drew me to the design was the idea that if you had one out, you could cast your second one, killing the first and bouncing it from your graveyard to your hand, and then recast it, getting one attack and two burns. Which is just possible at 8 mana, but implausible if you had to pay 3RR twice, or 2RR twice plus a mana cost for returning it to hand. But maybe that doesn't matter, maybe I should focus on making the card interesting in more straightforward ways.
Why do you need to cast two in one turn? Casting one on t4 and another on t5 seems to work just fine.
And FWIW, this doesn't abuse the legend rule any more than Kokusho, the Evening Star did... though I guess that's not actually a very strong statement :P
Scalding Phoenix, a phoenix lord where two copies can use the legend rule to loop themselves.
For Challenge # 111.
I tried to make a phoenix lord that also worked with the new legend rule to allow you to keep looping two of them.
However, it ends up a bit caught between those two aims, and there are flavour problems too:
Damage on death doesn't feel quite right flavour-wise or mechanic-wise, though phoenixes have done something similar before.
This has to be very aggressively costed to give you the dream of casting two in one turn.
It needs some way of returning itself, preferably immediately so you can loop them, but that's usually left off because it's sometimes abusable. And that doesn't fit on the card easily, so it's also applied to any other phoenix, but it's a strange bonus to give when most phoenixes return anyway. One the one hand, it's a bit of a superfluous bonus, on the other hand, it's just a cost reduction, it's not as broken as infinitely recurring any other creature type might be.
The whole concept of a phoenix lord is suspect, since there's only supposed to be one phoenix in most mythologies.
I think the new legend rule makes sense, but I'm not sure if cards should encourage players to deliberately make use of it: does it break the flavour if you deliberately want to cast multiple copies of your unique creature?
I tried Shield, Semblence Bear, not a particularly strong hit.
I was so sad Krark's Thumb was legendary, it was obvious to me what to do, and I always have a ready supply of d8 :)
I'm not 100% sure, but I don think we ever did "Design a Legendary permanent" before. Seems kind of obvious in retrospect.
Just in case we have, though, I added a little twist. The card designed should make more sense as a Legendary card than as a non-Legendary one. Flavor and story make sense, of course. But bonus points are rewarded to cards that become very dangerous when stacked on top of each other (like, perhaps, Grand Arbiter Augustin IV), or tend to break the game down when two are allowed on the board (like Krark's Thumb (Three Krark's Thumbs on the board would require a flip to be repeated 8 times.))