efore I run through a brief introduction of the cast that brought you Gatecrash from the development side of things, let me note that there was a ton of work in the planning of this set within a greater context. Zac Hill and Mark Globus worked on setting up an Architecture team that went into full force for the sets in this block. They helped answer many questions that wouldn't otherwise have been explored by the time a set typically entered development. They also answered questions that would tie this set into sets and blocks, past and future, in ways we hadn't prioritized to the same extent with sets before this block.
Similarly, by the nature of the block structure, I owe a lot to the work done on Return to Ravnica. Erik Lauer and Ken Nagle, along with the Architecture team and the design and development teams, worked out many of the starting points for what would also create the framework for Gatecrash. How good and prevalent should the color-fixing be? How should card power be distributed between monocolored and multicolored cards for the best Limited play? Questions like these took a lot of time to solve and I had the benefit of their earlier conclusions in leading my team through a similar process. It left us in a great position from which to explore what Gatecrash should be.
On that note, here's the Gatecrash development team:
Dave Humpherys (lead)
Resident cloning expert. I've been immersing myself in development, becoming the most frequent development team member in the last while. Gatecrash marked my six development team of the last seven sets. In atypical fashion for the development lead of a set, I was also on the Gatecrash design team.
All-around awesome guy. And did I mention? My boss. Mark is a senior producer for Magic and has been around since the first Great Designer Search. Mark led Magic 2012 design and also led development of Magic: The Gathering Commander. He fills in as we need him and appears on one or two design or development teams each year. Mark brought wisdom to what was a relatively fresh development team and challenged us on the big picture items.
Zac led Magic 2013 development, and before too long you will see the work he put into leading Dragon's Maze development. Zac was a great ally in discussing designs, especially within the overall structure of the block. I also picked his brain for insights on what he'd newly learned in leading the development of sets.
This is Max's second development team, quickly following up on Magic 2013. Max spends much of his time working on the digital side of Magic R&D, especially with Duels of the Planeswalkers. He's also been an integral part of Cube for Magic Online by leading its development. Max has a reputation for finding some imbalance early on in draft format and then continuing to lean on it until he's trounced us enough times to realize we need to adjust.
Mark is the senior brand manager for Magic. Besides filling up our quota of Marks on Gatecrash teams, he was in charge of making sure we had perspective from outside our R&D pit. I was excited to have Mark on the team, since I'd worked with him a lot over the years and seen him enthusiastically help in combining R&D's and Brand's visions together to bring new products and experiences to life. It helped, too, that he's an avid player himself, and has been on past design and development teams, like Magic 2013 design and Scars of Mirrodin development. Mark was quick to let me know whenever a card wasn't Timmy enough for him.
You likely know Gavin from his ReConstructed column on this site. Gavin also spends a good amount of time working on Kaijudo. This was Gavin's first Magic development team. This meant he had a lot of new ideas he was eagerly waiting to share, so I grabbed a great many of them for cards in this set. Gavin brought a great deal of excitement to the team and a fondness for finding all the angles to take in playing Dimir.
Art by Clint Cearley
As we made the transition from design to development, we'd already gone through many playtests with evolve and battalion, which had existed largely unchanged since early in design. They each polled well within the company and were a good fit for the guilds. In development, we still had our work cut out for us with a couple of fledgling mechanics and making sure the guild cards and their mechanics worked well not only for the guild itself, but also with neighboring guilds, even those in Return to Ravnica. It was time to get a bunch of parts moving together well.
Bloodrush was the next mechanic to solidify in the design process. We toyed with a couple of variations that were more all-upside, but these versions subsequently cost more mana and weren't fulfilling the aggressive-minded role we wanted. I was a big proponent of bloodrush, since it fit in so nicely with the two adjacent color pairs. It could provide a remedy and stabilizing agent for the most frequent feel-bad of both evolve and battalion—simply not drawing enough creatures—which goes hand in hand with not having enough creatures in your deck in the first place. There'd typically be a concern that a deck full of creatures can lead to some messy stalemates and for not the most exciting game play. Fortunately, bloodrush helps out in both of those regards.
Simic decks can pack extra bloodrush creatures where they might otherwise use pump spells. To create a diversity of pump effects, we also were already inclined to use a bunch of varied and big stats for bloodrush, which was a good fit for what Simic would want from creatures entering the battlefield. For the Boros deck, bloodrush creatures are an even better fit. White and red creatures most often want a helping hand in getting through other, bigger creatures, and pump spells are great here. Needless to say, so is having a pump "spell" that can also substitute as that third creature you need to set up your battalion.
While each guild was given options for both aggressive- and defensive-minded strategies, as we'd worked toward in Return to Ravnica, the bloodrush creatures admittedly fit best into the more offensively minded strategies. As our next mechanic also directly incentivizes attacking, bolstering defensive strategies in the set further was among the areas in which we especially looked to fortify strategies as development proceeded.
Next up was cipher. Cipher was very appealing to those we first exposed it to. It was like rebound that kept going and going. This was a big change in direction within the set. The original Dimir mechanic was all about milling. While we held on to many of those card designs (without keywords), we didn't feel it was going to do the work it needed as the central guild mechanic. This was particularly true as we started to think intra-guild, including those we'd see more of with Dragon's Maze. While synergies need not just be about the primary guild mechanic, the overload/mill/unleash triad, for example, created a seemingly humorous pairing of objectives. Mill opened up some fun with scavenge but didn't otherwise do enough work for us with the other guilds.
As such, Dimir has a clearly defined secondary strategy of milling. But the milling isn't all about entirely depleting a library; there's an exploration of the many ways in which making progress on that axis can lead to improved play from your other cards. Cipher is more flexible in its application and can have good roles in either aggressive or more controlling strategies. Cipher isn't as natural a fit with evolve since, in many cases, you are looking to build up a fortress of creatures, but we looked to make sure there were both worthy early evolve creatures like Cloudfin Raptor that could quickly become targets for cipher, assuming you could evolve it at least once. Meanwhile, we looked for early cipher cards, like Hands of Binding, that could help you buy the time to build up.
Cipher figured to be the hardest mechanic to balance, but I'll get to more on that later as I introduce my preview card. It turns out that our implementation of cipher worked well with the final mechanic we settled on, extort, because you can keep casting the spells with cipher and thus can keep triggering extort. Both mechanics could come together well in a variety of deck types.
In leading a mini-team to brainstorm ideas for an Orzhov mechanic, I had a number of items on my wish list for the group. Extort really delivered on all of them, and I'm glad Shawn Main came up with the idea. As the last piece of the mechanics puzzle, I really wanted a mana-sink to provide more to do in games that progressed to later turns, like scavenge was doing for Return to Ravnica, since the set could use something in this regard. A bleeder-style mechanic was high on the desirable list as well for the guild, and this mechanic tied in perfectly to that. As we were already at three attacking-related keywords, I also wanted to steer clear of that. Extort wasn't the most impressive on a first read, and it was a tad odd thematically in mono-white, but otherwise I quickly started liking it more and more. It was doing really cool stuff for both aggressive and defensive decks as soon as we gave it a try. In terms of pairing up with guilds sharing a color, as I mentioned, it was convenient how it also worked well with cipher.
In terms of connecting the final gear within the set to Boros, extort was also exciting, since it gave them some reach, removing those last pesky points of life from an opponent. And since it mostly appears on creatures, extort provided yet more flexibility in reaching a "full" battalion.
This put us in a good place to focus on how we best play up the synergies between the guilds and fill in holes.
Crash and Burn
At the outset, we were interested in moving the Limited format a tad faster than Return to Ravnica, in part setting up a contrast between what we expected to be a slower format and what we predicted to be typical of more color-hungry decks likely to follow in Dragon's Maze.
We had to be careful, though, in that we had so many offense-minded mechanics, and ones that could potentially lead to some snowballing of early advantages. This meant that we needed to make sure there were enough ways to break apart early leads and to also embrace the mechanics encouraging you to build up. There are a number of cards, especially removal, that are very deliberately poised better for players on their heels. There are also a number of ways to only temporarily or surprisingly achieve the critical mass of battalion or the opportunity to get an encoded creature through, as opposed to keeping these situations entirely stable.
Consuming Abberation | Art by Karl Kopinski
Cipher was particularly challenging, and scary, with regard to swingy-ness. In our own internal New World Order document summarizing how to best tackle complexity we have a list of "Red Flags." These are kinds of cards that cause problems with one or more of our primary goals within New World Order.
What is the first entry on this list?
The notes in this section for repeatable effects are to make sure that on-board complexity is kept in check and to make sure we protect "fun." Given that we'd be using this mechanic at common, this meant we had to take particular care not to, for example, create something that would become a repeatable "kill" or create hard-to-deal-with permanents. It also meant we could create other effects that would spiral out of control and bog down the battlefield. We had to be careful that it wasn't too easy to curve into nasty card advantage engines or other seemingly insurmountable advantages that didn't require other work or other mana investments.
We created some hoops to jump through, even if small ones, in setting up mini combos with cipher for Limited. Meanwhile, in Standard, as our public was quick to note, we needed to test out many initial card designs with decks highlighting Invisible Stalker. These decks became the real testing ground for what we could and could not do with cipher.
On that note, let's look at one of the things we decided we could do with cipher.
But first, think about your favorite creature. Ideally a non-legendary one. Any guesses where I'm going with this?
See the card here.
I hope you are enjoying the preview so far!
Thanks for reading,