Mashup: the Gathering Workbench: Recent Activity
| Mashup: the Gathering Workbench: Cardlist | Visual spoiler | Export | Booster | Comments | Search | Recent activity |
Recent updates to Mashup: the Gathering Workbench: (Generated at 2025-07-03 12:51:17)
I'm simplifying the battlestones by doing something that should have been done a while ago... combining the two abilities together into one large ability when you sacrifice the stone. This buster is the only card that doesn't make much sense with that thought process, though, so I'm shipping it back and making a new battlestone. Maybe it can appear as a weird one-of in a Mashup: Revised. I still do like that first ability. I should use it someday.
UG06
You know, I didn't really think about paying the casting cost, which you figure would be an important consideration. Truth is, I expect some people will expect that you must target a land, and some people will expect the cost of the spell will be free. It's probably best if I work with player expectations, instead of fight them. Changed over to both of them.
It doesn't let you skip out on mana costs, so having it work the first turn would add a significant, hidden cost to that attempt. I'm imagining a popular use case for this card would be to fetch Boom // Bust the next turn (you're already paying 6), which makes the ability rather irrelevant for a while unless you want to rub it in by including several copies of Raze.
I kept the "actualy does so" part out since that required too much stinginess and probably more words than wanted... though I admit the disconnect is jarring. I suppose I could just write out "cast it, targeting a land". It's not that big an overstep.
There seems to be some really interesting design space here, but it's a bit muddy. I could see some sort of cycle of cards. Perhaps an enter the battlefield effect. In reality, the "do it every turn" may be fair, but would be odd for the first time it appeared...
I'd be more worried that this lets you cast, oh, Desert Twister or Boomerang or... I think "That targets" is a valid filter; but I don't think it's implicitly enforcing "And when you cast it actually does so"
Random generator gave me Stone Rain and Ratcatcher. I don't really know if this works the way it reads. Do Magic cards understand basic logic? Can they tell that Stone Thrower can't, for example, search through your library for another Stone Thrower and cast it, just because the text includes the words 'target land' (Well... okay... Stone Thrower's not a sorcery. But you get the idea)? Hmm.
UR03