Andrew

  • Admin @ mtgzone.com, a Magic: the Gathering community
  • More at andrewgioia.com
  • Playing and collecting MTG since Mirage!
  • I ♥️ Legacy Lands, Premodern Parfait Oath, Modern Amulet Titan, and elf tribal

  • 226 Posts
  • 383 Comments
Joined 1 year ago
cake
Cake day: June 9th, 2023

help-circle



  • AndrewMAtoSpoilers[DSK] Withering Torment
    link
    fedilink
    English
    arrow-up
    7
    ·
    26 days ago

    Wow this feels like a pretty significant color pie break. I realize they’ve printed black enchantment removal a few times before (Feed the Swarm) but this is an instant and seems like they’re just shifting to giving this to black now. Seems like kind of a shame to me.





  • AndrewMAtoMTGThe Nadu Situation – Mark Rosewater on Tumblr
    link
    fedilink
    English
    arrow-up
    6
    ·
    1 month ago

    You’re absolutely right and Mark’s straw man arguments like that are pretty frustrating. I have the same meaning as you when I say stop designing for Commander as I’m sure the vast majority of others do. I don’t know if he’s being intentionally dishonest or if he just doesn’t get it still but it is 100% stop printing overstatted Commander cards that warp eternal formats and these ability soup engines-and-payoffs.

    Re: playtesting I wish they would come out and say what their playtesting process is. How many people are in each group, how long do cards get active testing, etc. Barring those details I kind of disagree that they can’t do more and while they definitely cannot catch everything, their process should be sufficient to not let a Nadu get by.





  • AndrewMAtoMTGOn Banning Nadu, Winged Wisdom in Modern
    link
    fedilink
    English
    arrow-up
    9
    ·
    1 month ago

    I appreciate them writing this and taking it on the chin here but honestly there is so much in here that’s pretty damning about their design process. Nadu was a massive mistake but one that seems negligibly correctable.

    Mistake 1: not enough playtesting!

    Majors describes the testing they did. He cites no actual numbers or anything but I think that makes it pretty clear how deficient it is/was:

    For both Modern Horizons 2 and Modern Horizons 3, we brought in a small group of contractors and worked on the set in a dedicated sprint as a collaboration between that group and a small number of play designers. The playtesting time is more dense, as the group is singularly focused on the set without other responsibilities, but shorter in terms of weeks.

    Emphasis mine. I would wager that this is probably 2-3 contractors who played for probably a few weeks with the people who designed the set, a group who is obviously stuck in groupthink and can’t see differently. There’s no wonder they miss issues like this.

    Mistake 2: changing cards again without testing

    Again we have a card that was changed at the last minute and shipped as-is.

    I missed the interaction with zero-mana abilities that are so problematic. The last round of folks who were shown the card in the building missed it too. We didn’t playtest with Nadu’s final iteration, as we were too far along in the process, and it shipped as-is.

    How many times does this need to bite them before they just actually playtest every single text change? It’s crazy to me.

    Mistake 3: no automatic flags for certain high-risk abilities

    They all missed the interaction with 0-mana abilities, OK fine. But why is there no automatic flag for high risk abilities? Off the top of my head:

    • unbounded triggers
    • triggers that draw you cards
    • triggers that put cards directly into play
    • triggers that occur whenever the permanent is targeted
    • triggers that give things to all of your creatures

    Original Nadu had every one of these, and there are no doubt many many more things that should automatically create a higher scrutiny/testing regimen. They added the 2-times-per-turn cap at the last minute but removed the by-an-opponent limiter!

    Software can easily flag cards that should be tested more fully, or recommend problematic interactions. They don’t seem to be doing this at all, instead just accepting a certain % of failure/risk. This is so preventable.

    Mistake 4: putting Commander cards in Modern sets

    This one is a personal pet peeve of mine and really irritates me more than everything else. This card was designed specifically for Commander yet it went into a set ostensibly for Modern/Legacy.

    In one of these meetings, there was a great deal of concern raised by Nadu’s flash-granting ability for Commander play. After removing the ability, it wasn’t clear that the card would have an audience or a home, something that is important for every card we make. Ultimately, my intention was to create a build-around aimed at Commander play, which resulted in the final text.

    If the card is for Commander, put it into a Commander set! This is also extremely damning from a design perspective–they removed the flash ability and then didn’t think the card would be played at all!

    So much of this seems to be preventable with better processes or using technology in even basic ways, ways they are no doubt not even close to taking advantage of. It’s a shame because these sets could be better and the playerbase wouldn’t have months of crap like this, or a Pro Tour absolutely ruined by a preventable card.







  • AndrewMAtoMTGEternal Weekend Returns in 2024!
    link
    fedilink
    English
    arrow-up
    3
    ·
    2 months ago

    Love the optimism! I for sure will hit my classic 1-3 drop but I’ll definitely be playing in this. I wish that card was for everyone on entry, though I’ll also never not use the DiTerlizzi original.

    Hopefully Grief and/or Psychic Frog eat a ban before November.