Each of these "Designing for" articles follows a similar structure. I'll begin by answering the same four questions and then I will walk you through the design of the guild mechanics, the one from the original Ravnica block and the one from the Return to Ravnica block.
What's the Easiest Thing About This Color Pairing?
Blue and black tend to be the kings of card advantage. Blue is primary in card drawing and black is secondary (tied with green). Blue has counterspells and bounce. Black has discard and creature destruction. The two colors are excellent at slowly, and sometimes not so slowly, gaining the upper hand, often subtly enough that less-experienced players aren't even aware of it.
What this means is that blue and black thematically click together well. The two colors have a clear flavor and feel that mesh well. Blue is sneaky and cunning. Black in underhanded and ruthless. Mix them together and you have a guild you might not want to trust.
What's the Hardest Thing About This Color Pairing?
While philosophically the two colors mesh well, mechanically they are the two ally colors that have the least in common. Now, this is a pain for making hybrid cards, but shouldn't a clear mechanical identity make gold cards easier to design? The problem here is that while blue and black don't overlap much in actual mechanics, they have a lot of abilities that are close to the other but just a little different.
I'll walk through some of them to demonstrate:
Card Drawing: As I said above, blue is #1 and black is tied for #2. But blue always does its card drawing straight up, often these days at instant speed. Black always has to trade something for its cards—most often life. Black usually does this at sorcery speed.
Evasion: Blue and black both have flying. Blue also has unblockability and islandwalk. Black has intimidate and swampwalk. Black also has deathtouch, which doesn't technically give it evasion but heavily encourages the opponent not to block.
Library Denial Blue "mills," meaning it makes the opponent put some number of cards from the top of his or her library into his or her graveyard. Black "extorts," meaning that it goes into the library and exiles particular cards. The flavor here is that blue makes you forget in general while black lobotomizes you.
Hand Denial: Blue and black are the only two colors that can easily deal with a threat before it hits the battlefield. Blue has the ability to use counterspells while black has the ability to force the opponent to discard.
Tutoring: Blue and black are the two colors best at getting specific cards out of your library and into your hand. Blue tends to be more focused, with cards directing you what kind of card you can get, while black has the more blanket tutors, sometimes with an additional cost associated.
Stealing Creatures: Blue takes the opponent's creatures while they are alive, while black takes them after they've died.
Learning the Opponent's Hand: Blue has spells that peek. Black gets glances as part of certain discard spells where it needs to see the hand, such as Duress or Coercion, to make choices of what gets discarded.
In each case, they are similar but a little different. That's great for giving each its own identity but it makes it more difficult to make blue-black cards. The blue ability always feels close to black, and vice versa, often making the cards feel like they'd fit in one color or the other rather than in both.
What's the Mechanical Heart of This Color Pair?
Of the ten two-color pairs, this question is the trickiest for blue-black. Why? Because blue-black's mechanical heart is more about a feel than a concrete quality. Boros is about cheap aggressive creatures, Golgari is centered in the graveyard, but Dimir isn't quite as easily pinned down.
The easy answer is that blue-black is about the library. Blue and black are the two colors that interact with it most. They have card drawing, tutoring, milling, extracting, filtering. One of their win conditions is library depletion. But all that is more a secondary strategy in Gatecrash.
No, the thing that ties together blue-black is this sense that it's getting incremental advantage at every turn. If any color combination is the poster child for the two-for-one, it's blue-black. What this means is that when you build a blue-black theme, you have to figure out how it's getting its incremental advantage. Note that the two Dimir mechanics do it in different ways.
Transmute is about trading card utility, upgrading one card for a card more fine-tuned for your needs. Cipher is about setting up a situation where you can create raw card advantage, generating spells without the card. I'll talk about each more as I get to their creation, below.
What's the Focus of This Color Pair?
Blue-black's plans are not as straightforward as some of the other color combinations. Part of this, I believe, is because blue-black wants to keep the opponent guessing. Its advantage comes from the fact that the opponent doesn't know where the attack is coming from. The end result is that blue-black has three main ways to win.
Evasive Creatures: Blue and black are two of the colors with the best evasion. Once they take control of the game, they can use their evasive creatures as a kill condition. Because they have the tools to mess with the opponent's plan and slow things down, the small evasive creatures have time to do their thing. The cipher mechanic clearly plays into this space.
Library Depletion: Magic has an alternative win condition built into its very core. Blue-black are the two colors that most often win through this strategy. Blue has straight-up milling; black has extracting. All it has to do is stall and use its milling and extracting to win. This strategy is even more powerful in Limited, where the decks are only forty cards. Grind, the unnamed "mill until you get a land" mechanic from Gatecrash, plays into this strategy.
How'd I Lose?: The final strategy is the subtlest. Blue-black uses its incremental advantage to eke out every small gain it can. The opponent loses but never has any clear thing to point to. Somehow, he or she just lost. Transmute played in this space.
These strategies can be mixed together or run separately. They make blue-black extra hard to fight against because you're never quite sure where the danger lies. I know when playing against Dimir in Gatecrash, I'm always trying to figure out what strategy my opponent is using.
This focus is unique and not something I'd want to do a lot, but it philosophically fits blue-black to a T.
In the initial Ravnica block, Dimir was in the first set, Ravnica: City of Guilds . The design team (Aaron Forsythe, Richard Garfield, Mike Elliott, and Tyler Bielman, led by myself) approached Dimir as the "library guild," much as we approached the Golgari as the "graveyard guild." As I explained above, this comes about because blue and black have more interaction with the library than any other two-color combination.
I'll be honest, when I pushed us toward the "library guild" I had one goal in mind. I am a huge fan of alternative-win conditions so, of course, I was a huge fan of the one already built into the game: milling. I didn't know how exactly it was going to work, but I wanted milling to be a part of Dimir's identity. At the time, though, it never dawned on me to make milling itself part of the guild keyword. (That wasn't true for Gatecrash.)
While I was fiddling with milling, someone else on my team, Aaron Forsythe, decided to take a different approach in finding a mechanic for the "library guild." Rather than focus on the opponent's library, Aaron turned his focus onto the player's library. As I explained above, one of the areas where blue and black overlap is tutoring. Aaron wanted to see if he could make a mechanic that gave blue-black the ability to get the cards it needed out of the library.
Aaron's major problems were basically tutoring's major problems. First, we have what R&D calls "repetitive game play." Magic is fun if each game plays out differently. When games follow the same pattern, game after game, it becomes monotonous and less fun. The game solves this problem with the library, an item that is randomized such that the players get their cards in an unknown order, making each game play out differently. Tutors undo this tool by eliminating the randomness.
The second problem is a power-level concern; this is more of a development issue than a design one but design has an obligation to make things that can be developed. A combo deck stalls until it can get the pieces to its combination, which usually allows it to quickly win the game. Because a combo deck requires the player to collect a series of different cards, the randomness of the library tends to slow down the deck. Tutoring once again bypasses this safety valve, allowing a combo player to "go off" with a combo far faster than he or she would normally be able to. Aaron recognized both problems but he thought we could find a way to work around each.
As proof of concept, Aaron turned in a card with his mechanic proposal. You guys know the card as this:
But when Aaron first turned it in, it looked like this:
Counter target spell unless its controller discards his or her hand.
Transmute UB (UB, Reveal this card from your hand: Put this card on top of your library, then search your library for a card with converted mana cost three, reveal it, put it into your hand, then shuffle your library.)
There are a few differences between Aaron's original version of transmute (note the name never changed—that was what Aaron called it when he submitted it). Let's walk through them.
The cost: In Aaron's original proposal, blue-black cards would transmute for , blue cards for , and black cards for . In the finished version, the blue-black cards cost , the blue cards , and the black cards . This change was made by development because the design version proved to be a little too strong.
What you do with the card with transmute: In Aaron's original version, you put the card on top of your library, which would then be shuffled in at the end of the effect. The finished version just had you discard the card. Why this change? Mostly because everyone just discarded the card and forgot to put it on top of the library. Usually, in design, when the players keep doing something wrong, but do it consistently wrong, you want to seriously consider just making the mechanic do what everybody instinctively wants it to do.
Play only as a sorcery: The original version could be played any time you could play an instant. While this offered all sorts of cool moments where the card could tutor on the fly, it was just another thing making the mechanic too powerful. Development wisely also made this change. (Note that modern template now says, "Transmute only as a sorcery.")
Other than those few, mostly power-related issues, transmute was printed as submitted. The trick for the design team was figuring out what kind of cards wanted to have transmute on them. Aaron felt strongly that they had to be cards you would want to main deck but cards whose value would swing as the game progressed. Perplex, as an example, could be powerful early but often could be worthless later in the game, when the opponent doesn't have any cards in hand.
The other thing we had to monitor was making sure the transmute cards covered a range of converted mana costs. The transmute mechanic was linear, in that it made you want to include other cards with the specified converted mana cost, so we wanted to ensure there was a wide spread.
As mechanics go, we got it in early in the process and it made it cleanly all the way through development (with the few tweaks) to print. Cipher wouldn't be quite as easy.
Let me start by revealing something I've never revealed in an article before: I love grafting things. Let me explain. Grafting is an R&D slang term where you take some aspect, usually a sentence, and stick it into the rules text of another card. (Note that there also is a mechanic called graft used by the Simic in the original Ravnica block, but I'm not talking about that.)
Here's an example of a famous old card from Urza's Saga that grafts:
The point of grafting is that you take an existing card and expand what it can do by grafting on additional words and/or abilities. Why do I enjoy grafting so much? I don't know. My best guess is that it's my Johnny sensibility enjoying turning cards into other cards.
I bring this up because my love of grafting has led me to design numerous mechanics that incorporate it. Two of the most famous are imprint, from Mirrodin, and splice, from Champions of Kamigawa (best known for its original use, "splice onto Arcane").
I bring these two up because cipher essentially is the love child of these two mechanics. Let me explain. When Gatecrash design started I pushed hard for a milling mechanic with the playtest name of "grind." While grind stayed in the set, we decided we wanted a different mechanic to be the Dimir keyword, so I spent some time thinking about a new replacement. (For the full, longer story of grind's creation and ultimate removal as the guild's keyword, check out this earlier article where I tell the full story.)
Much of design is spent realizing that something you'd worked on isn't quite right and then having to search through all the existing parameters to find a solution. When I do this, I find it works to write down as many things as I can that I know to be true. The more restrictions I have to my problem, the more I can figure out which areas I need to explore. Here's what I had when I started trying to find a new mechanic:
- The mechanic had to feel Dimir: I talk a lot about how I design by feel. I'm a big believer that a game designer has to be very conscious of the emotional reaction his or her game mechanics will create. As such, my number-one priority in finding the replacement mechanic was finding something that just oozed Dimir.
- We couldn't mess with milling: Grind had been shifted from keyword to nonkeyword status. That meant anything in the similar space was off limits.
- It needed to play into the focus of the guild: Up above, I outlined three ways Dimir could win. Restriction #2 eliminated the mill option, so that left evasion and card advantage. Card advantage is tricky to work with (and we already went there in original Ravnica—see above) so I decided to focus on evasion. What did Dimir creatures want to do? Well, they liked sneaking in and damaging the opponent. Was there a way to make doing that even better?
- It wanted to be a spell mechanic: Boros? Creature mechanic. Simic? Creature mechanic. Gruul? Creature mechanic. Orzhov? Not totally a creature mechanic but it was on a bunch of creatures. That meant we really needed a spell mechanic, so while I was solving one problem, I might as well solve another.
- It wanted a little bit of splash: The other guild mechanics were all solid and they played well but none of them tended to jump out at you when you first heard about them (okay, maybe evolve). This was another problem we could solve while finding the replacement.
With all this in my head, I started walking through my options. What follows is a rough approximation of my train of thought:
Okay, we have rogues and scoundrels who sneak around and hit the opponent. How could I help that strategy? I could help make them harder to block. No, blue and black are already the best at evasion. What if I rewarded them for damaging the opponent? That shows promise. How do I reward them? Saboteur abilities (what R&D calls the ability that has an effect when it deals combat damage to the opponent). When you hit the opponent, something happens.
So I want to graft saboteur abilities onto my Dimir creatures, many of which would naturally have evasion. How do I do that? Creature Auras seem the cleanest. The problem with that solution, though, is that there's no keyword. Most sets have an Aura that grafts text. How do I make this mechanic something I could keyword? Also, what do I do to make this splashier?
This led me to the splice mechanic. What if I had a sorcery that I could graft onto a creature as a saboteur ability? That sounded cool. Also, I channeled imprint with the idea that you would exile the spell itself and then use the actual card as the reminder for what got grafted. Mark Gottlieb (my co-lead for Gatecrash) suggested that you get to cast the spell first, before it gets grafted, to allow you one use of your spell—and often two if you set it up correctly. This would help make sure the cards had enough value to play.
With this idea figured out, the next step was to actually make the cards. This proved to be a little more difficult than I initially realized.
First, we decided we wanted to keep the mechanic on sorceries because the timing with instants had the potential to confuse the players. It also raised the mechanic's power level and development was already scared of cipher (called "encode" in design).
Second, the effects all had to be something that were useful at the tail end of combat, when your creatures dealt damage. This meant they had to be proactive, not reactive, and they had to be effects that were generally useful at most times of the game. We also realized we could essentially make a few creature cards by making them sorceries that generated creature tokens.
Third, we had to keep the effects small enough that a creature with evasion that was doing this every turn would shift the game in the Dimir player's favor rather than just winning it outright.
Fourth, the abilities had to be short (meaning few words) because they had to fit on the card, as cipher was going to take up six lines of reminder text.
Luckily, blue and black's subtle differences helped make it easier to find enough effects, many of which were short enough to fit.
And that is how cipher came to be.
Black and Blue All Over
That's all the time we have for today. I hope you enjoyed my peek into the mysterious world of blue and black. As always, I would love to hear your feedback in my mail, in this column's thread, or in any of my social media (Twitter, Tumblr, and Google+).
Join me next week when the world is all black and white.
Until then, may you get in your damage before they even see you coming.
Drive to Work #25—Homelands
I have said on numerous occasions that I believe Homelands is the worst-designed expansion in Magic's history. Today I explore its design and talk about what went wrong.
- Episode 25 : Homelands (10.8 MB)
- Episode 24 : The Mana System (9.92 MB)
- Episode 23 : The Color Wheel (10.2 MB)
- Episode 22 : The Trading Card Game Genre (9.81 MB)
- Episode 21 : Innistrad Part 3 ()
- Episode 20 : Innistrad Part 2 (14.6 MB)