Magic: The Gathering Drive to Work Podcast - Drive to Work #133 - Designing Commons

Episode Date: June 20, 2014

Mark today talks about the challenges of designing common cards.

I'm pulling on my driveway. We all know what that means. It's time for another drive to work. Okay, so today I'm going to talk about design, specifically about designing commons. So, when you start a design, one of the things that I always do, and encourage all my other designers to do, is you always want to start with commons. Why is that? and encourage all method designers to do, is you always want to start with commons. Why is that? A couple reasons.

First off, when someone opens up your set, they're going to open up the booster pack, and of the 15 cards in the pack, one card's a land, one card is a rare, these are all on average, obviously, and three cards are uncommon. The remaining ten cards are common.

That means two-thirds of every booster pack are common cards. So when you talk about an experience that people get, whether it's through limited or even through casual constructed, two-thirds of all the cards they see are your commons. Well, if your set is going to work, two-thirds of it has to be conveying the message of what you're trying to do. So one of the things about doing commons first is they really are the basis of what your set's about. And that one of my dictums that I always say is, if your theme's not a common, then it's not your theme. And what I mean by that is that your comments make up such a large portion of what the

set is, that if your major themes aren't there, then they're not going to be as publicly seen as themes elsewhere. And so, for example, in Champions of Kamigawa, we did this thing where we made all the rare creatures

legendary. But, how many packs did you have to open before you could figure this out? A lot. You know, it wasn't because... Where I want you, for example, let's say we're doing Theros. Theros is the Greek mythology set.

Or Innistrad. It's the, you know, Gothic horror set. I want you to open one pack and get the theme of the set. You go, oh, oh, Gothic horror. Oh, oh, Greek mythology. You get it in one pack. Now that doesn't mean that all you get is one pack.

Obviously people open more, but it's really, really important that you get that across. So the reason you start with commons is to see, can I take my themes and do them very simply? Now, remember, New World Order says that there's limits of how much complexity we could have in common.

And I feel like those restrictions are important because if you combine the restrictions of New World Order along with the dictum of your theme needs to be in common, well, it says, okay, there's an overlap here. What can I do through New World Order but is conveying what I need to convey? Or another way to think of it is, I have this restriction that I have to deal with. And as those people who listen to me for a long time know, restrictions breed creativity. That having some restrictions are good. And what I think New World Order does for us, which I like a lot, is says you need a clarity of your message. Your message needs to exist in a simple enough form that people can understand and get it.

Now, it doesn't mean that comments can't have any complexity. The way New World Order works is 80% it has to be sort of toe of the line, and then 20% gets to sort of buck the line, if you will, but it has to buck it in a cohesive way, meaning the exception is not every single card in the 20% is its own exception. The 20% as a group tend to be a singular exception. So for example, in Zendikar, normally you don't care about land drops. That's not something you have to reference or care about. In Zendikar, we're like, okay, you have to care about them, but that's the thing you have to care about. So the thing that the 20% where it this not normal thing to care about, well, we concentrate it. Okay, so the first thing to

remember when doing common cards is, I'll use a metaphor, I'll use my packing metaphor. Let's say you need to pack. You have a suitcase and you want to put things in it, or you have a car and you're trying to, you know and you're trying to move. Maybe the car and the moving thing is better. I have my car. I have objects I have to get in my car because I'm going to move. Well, what do you do? What is the correct strategy to packing?

Well, number one, get the biggest, hardest-to-fit item and put it in first. Why is that? Well, let's say, for example, I'm moving a chair. In my first move, I'm moving a chair. I have many drives to do. But in my first drive, I'm going to move my chair. Well, the chair is big. It might only fit in the car a couple ways,

in that if I put other things in first, by the time I go to put the chair in, it just might not fit. So in magic, it's the same basic philosophy, which is you got to figure out what your biggest, hardest thing is, and you got to do that first. And the reason is, my parallel with packing, is that the empty set has room for lots of things. But every time you put something in, it becomes harder because now you've filled up space and when i say fill up space i mean it in two ways physically there's the file there's only so many cards in the file but the second thing is you only get to do certain things so many times

for example um you only get so many direct damage spells well if you really really want to have your new mechanic interact with direct damage well well, you better do that early while there's space to do that. Because eventually, you might have too many direct damage spells. You're like, oh, I can't make any more direct damage spells. So when I talk about having space, I don't just mean physically in the card slot, but also sometimes you only get so much of something.

And so, you want to make sure that the things are the most important, maybe most important isn't even the correct word, but the things that are the hardest to fit in. Now, as a corollary, you also want to make sure that the things that are hard to fit in

are worth fitting in. For example, I'm going to move, you know, let's say I have a very hard to fit chair. I have to ask myself when I'm moving,

do I really want this chair? Is this chair worth moving? Is it worth fitting in my car? Now, the answer might be, oh, this is the best chair ever. I love this chair. Then, yes, it is. But if the answer is, eh, I'm not too crazy about it. Wow, this is going to be hard to move, and I'm not crazy about it.

Maybe I just want to sell it, you know. And so, when you're making your common, filling in your commons, you have to figure out whether something is worth it. Does something make sense? Now, remember, when you are making a card file, the key to making sense is what we call iteration, which means that you basically make things, play them, change them, play them,

change things, play them, and you do that for the duration of your design. And then at some point, you're like, okay, I'm happy, and you turn it over to development. I mean, it's a preset time, obviously. So when you're making your commons, you have the ability to take some flexibility. Usually the first pass of commons is not about it being exactly what it's going to be at the end. The first pass of commons is trying to make sure that you are sampling what you need to sample.

And so when you first start making commons, like I said, you are trying to figure out whether you can fit the things that you need to fit. You're trying to figure out whether you can get the things simple enough that you need to be simple enough. And you are trying to sort of experiment a little bit and see how things feel. So normally when I first make a set, the very, very first thing I'll do is I figure out what is the essence of the set. So let's take, I'm going to take Zendikar, because Zendikar is a clean example. The first thing I did is I said, okay, I want to do a set that's about land mechanics. So the first thing I did is I sat down with my team and I said, okay, team, let's make land mechanics.

In Innistrad, I sat down with my team and I said, I want to make horror. Let's figure out what conveys gothic horror. Theros, obviously, sat down and said, I want to do Greek mythology. What has to feel like Greek mythology? You know, when I sat down for Gatecrash, because I led Gatecrash, it was like, here are our five guilds.

How do we play up our five guilds? You always start from some vantage point. And then those things go first. For example, in a multicolor set, multicolor cards' designs are tough. And the reason is that you have to make something that takes

two different elements and pushes them together, but in a way that feels right. I had a podcast on design. I think I had a podcast on designing gold cards. I believe I did. I wrote an article on it, I know. Oops, and there's... Get out of the way of the fire truck. So, we'll go back to Zendikar.

So, the first thing we did is we figured out, okay, it's a set about land. Well, we did experimentation in figuring out what we wanted for land. So, once we found some different land mechanics, I made some commons with those land mechanics. Then once that was in the file, I figured out what else we needed. Pretty early on, we realized we needed something to do with mana. And so Kicker went in the file pretty early just as a way to spend mana. The funny thing is when I put Kicker in, it wasn't necessarily that I thought Kicker was going to stay. It's that Kicker accomplished the job and it was a known quantity

and I really wanted to test my land mechanic. So sometimes early on, you're just putting things in that fill the space that you need. That's another important concept to understand, which is when you are testing early on, you kind of want to put the things in you don't know, and then surround it with things you do know, so you have a better sense of the things you don't know. And that's a very important concept, which is, if I put too many things in that are completely foreign,

it's very hard for me to tell what is working and what's not working. I mean, I can play it. If I get lucky and everything works, okay, it works. But if it isn't working, sometimes it's very hard to tell why it's not working if you have too many unknown variables. So what often happens early in playtesting is you pick the variable you want to mess around with. In Zendikar, that was land mechanics. So I put a bunch of different land mechanics in.

More than I knew I was going to use and at a lower amount. So let's say, for example, I know in the end I want one major land mechanic. In early design, what you will do is you'll make a bunch of different versions of it, put them all in at a lower level so that you have a chance to experience them. Now remember, I've talked about this before. When you do design,

we do what we call a flat power level, which means we price every card so that it's playable, or mostly every card. I mean, no matter what you do, some cards will be more playable than others in context. But we do as flat a power level as we can. And the reason is, I want my playtesters, my designers, to play everything they can to see whether it is fun to play or not. So this begs the question, hey, if you do that in design, why don't you do that in the real set? Wouldn't Magic be wonderful if everything was playable? And the answer is, you can't do that.

One is, there are power issues. One of the things you have to be careful of is what we call power creep, which is, if I make my cards, you know, you only get so much power to put in your set. If you increase the amount of power you put in, then it's fighting with the power in previous sets. And the only way then to make cards that people want to play is to make the power a little higher. And over time, your game spirals out of control. We don't want to do that. Also, the game is much more fun if there's a variance of power. You don't want every card to be of equal power. And the one way I try to explain it is, let's say we do a draft. You want the

better player to do better in the draft. And if all the cards are of the same power, well, the worse the player can't go that much wrong. I mean, the better player will have a little bit more synergy, but the worse player is going to have decent cards. Where if you put a little more respect from, knowing what the right card is becomes a skill that you need to understand in drafting. Now, we try to make it so that which card is more powerful is contextual, meaning there was a time and a period where this card is just the best card in red, no matter what. And we try to get to the world where this card is the best in red if you're playing this deck. But if you're playing this deck, maybe this card's the best in red.

That it's not so clear cut. But anyway, in design we do a flat power level because we are not, once again, we are not yet testing the environment in early design. We are testing, we are trying to get a sense of all the different cards. We are trying to play the different facets. And one of the things about doing design is understanding what development is going to do. And I, as a designer, do not need to do development's work. Development will do development's work.

Development's going to figure out what to push, where to price things. There's a lot of energy to balancing the environment. Design is constantly changing cards. There really is a lot of lost work trying to balance the environment when every time you make a change, you have to rebalance it. Now, one of the things we do do is we do curve. And what I mean by that is we make sure that with our creatures especially that there is a range of spells from one drop up to, you know,

a common six, maybe seven drop in certain colors. So the idea is we want to make sure that when you play, there's a range of things to play. And so we do curve. That's important in design, just to make sure when people play that there's a flow to the play. Okay, so I'm making my commons. I have to figure out what is the thing I care most about.

So, for example, Zendikar, I care about land. So I make a bunch of land mechanics. I put the land in. Next, I go, okay, what else do I need? And I realized pretty early on that since we had more land mechanics and they were encouraging to play land, we needed some way to spend the extra mana. And I put kicker in. And like I said, oftentimes when you are doing early design, you put in a mechanic that's a known quantity rather than an unknown quantity. Now, we also have a dictum in R&D. We try to make sure that every block has at least one returning mechanic. Now, sometimes there's more than one. That's fine. It doesn't have to be solely one, but there needs to be at least one. And there are exceptions. For example,

I mean, I guess you could say technically in Return to Ravnica block, we brought hybrid back. But the 10 mechanics were new mechanics because we didn't want to give one guild a returning mechanic and the other nine a brand new mechanic. Maybe as time goes on, we'll feel less about that with Ravnica, especially as we start getting to a third Return to Ravnica, the first Ravnica, the mechanics there start to be something that people haven't seen for a while. Okay, so we figured out we needed the land.

We put the land in. And like I said, in early commons you put a bunch of different things in because you're trying to sample it. And that's another big thing about early design is you are trying to sample. You are trying to figure out what is fun. How do you figure out what is fun? By playing it. So one of the rules that I do in early design is, with a few exceptions, if that needs it,

I have a two-of rule. And the rule is, if you get more than two of any one card, you can turn them in for other cards in the same color, random cards, but you are not allowed to play more than two copies of a card. Why is that? Because I want you to experience a lot of different interactions. I want you to experience a lot of different cards. And it's not just playing the card itself.

I want you to experience the playing of the cards. I also want you to experience the interaction of the cards. Oh, well, it's neat when this and this come together. Because one of the other things you're doing early on when you're doing commons is you're trying to start to figure out synergies. One of these days, I'll do a whole podcast on synergy. I'm a huge synergy fan. In fact, people have asked me what my biggest design weakness is. And I think it is my love of synergy. Synergy is good and sets should have synergy, but I sometimes

put in a little too much synergy. Development sometimes I have to take out a little synergy because I really enjoy putting synergy in my sets. Some is good. A lot can be okay. Too much of anything can be bad. Remember,

your greatest weakness is your greatest strength push too far okay so you put in the thing that you want to test have some variance of it you put in the supporting thing often that's a known quantity

so you can test it then a lot of what you want to do is you want to fill out your set with cards that either are basic effects put in your cancel

put in your naturalize or sometimes you put things in that just are simple cards that match what you're trying to do. So one of the jokes I have is I always ask my designers early on to design common cards. And my joke is I usually fill up my own commons before I get done asking for commons. What that means is it is very, very common when you design a common card, and I'm talking about professional magic designers, that a lot of the stuff that could turn in isn't actually common, it's uncommon. Every once in a while you turn in a common

that's actually rare. And what happens is, you get good ideas, and you get inspired, and you make things, but one of the keys to common, and this is what they call KISS, keep it simple, stupid, you really want your commons to be doing one central thing, and a simple thing, not a complex thing. Now, it's fine if that one simple thing has a lot of ramifications. For example, when we were doing Zendikar, we did the reprint of Harrow,

which was a card from Tempest, originally called Crop Rotation, by the way, which technically, by the way, is a better name for this card. We would later use Crop Rotation on a different Rambit Grothy card. So what Harrow does is you sack a land, and then you go get two basic lands

out of your library. Well, in a world with landfall, Harrow is very interesting. Now, it also fixes your mana. Everything that Harrow did in Tempest, it did in Zendikar, but all of a sudden, land takes on a different meaning, and this card, it's very simple,

but it has a lot more interesting value to it. Same with Mulch, which also... Did mulch end up in the car? It was for a long time. But it's another thing that helps you get your land. Oh, no, sorry. We put mulch in Innistrad to help you get cards in your graveyard. Because that's a neat way.

Normally what you care about is getting the land, but mulch also lets you get things in the graveyard, and in Innistrad, green cared about things in the graveyard. Anyway, so you want to fill your comments cared about things in the graveyard. Anyway, so you want to fill your comments with things that are very simple. They do one thing. And here's another thing, which is a very good thing to remember is

you need some very simple things. Why? Magic is a complex game. Why do I need to have a vanilla creature? And the answer is it has to do with board complexity. There is a lot going on, a lot going on. And I think sometimes that people, it's very easy when you look at things in a vacuum. Like, for example, let's say I said to you, I need you to hold some stuff. And then I showed you one

thing and I go, can you hold this? You'd probably look at it and go, yeah, okay, I give you a, let's say I give you a can of Coke. And you're going to go, can you hold this? You go, yeah, okay, yeah, I can hold that can of Coke. And then I say to you, okay, can you hold this, you know, carton of cream cheese? Yeah, I can hold this carton of cream cheese.

Can you hold these 10 hangers? Yeah, I can hold this carton of cream cheese. Can you hold these 10 hangers? Yeah, I can hold it. And at some point, all these little things add up that in a vacuum aren't that bad, but once you're holding 20 of them, there's a lot of the problem that comes with magic is

you can take a lot of simple things and add them together and it makes it complex. And that part of what you need to do is we want you to focus where we want to put the complexity where it's fun. And of what you need to do is we want you to focus where, we want to put the complexity where it's fun. And then what we want to do is, so here's a very important concept to understand,

which is you only get so much complexity in the game. We want to limit the complexity. And that's not because there's not complexity in Magic. There's tons and tons of complexity. It is not like I'm trying to make this into tic-tac-toe. Magic is probably the most complex game that is currently sold that has been around for five plus years. Magic is a very complex game. Our goal here is to minimize just how complex it is, not to make it not complex. It is impossible to make magic not complex. It's complex.

And part of doing that is you need some breathers. You need to concentrate your complexity where it matters. And the way I like to think about it is imagine that you had points for your complexity and you had a limit. You only get so many complexity points. Well, every time you make a common card, you have to add, you have to say,

how many complexity points are on this card and is it worth it? Do I need this to be? And the reality is, I need some creatures. Common creatures. I mean, I'm not saying that all of them are vanilla or French vanilla. Vanilla meaning that they have power and toughness, but no rule stacks. French vanilla meaning they have power and toughness, but they have creature keywords.

First strike, flying, and such. You need to have a lot of simple stuff like that, only because you need to allow your brain to be able to focus. Because what happens is, if you give your brain too much, instead of being able to focus, it kind of just blurs things out.

And what will happen is, when we do focus testing and watch people playing Magic, and even more experienced players watching Magic, that if you get past the overload point, once your brain can't handle it all, you kind of just like, your brain just like dulls out and goes, okay, and then you kind of don't think about things. And what we want to do is we want people to be able to spend the time and energy to think about things, so it's a matter of focusing

your complexity. And once again, a big part of design is saying, there's a cost that comes with making what I'm making. Do I want to spend that cost? And one of which is complexity. That's a big one, which is, this is complex. How complex? And the way I think of it, I always use the term complexity points.

People think like we have a system where we have actual points. We don't. It's just easier to think of it this way, which is if I'm looking at a file and I have three cards in common, let's say, that I know are all sort of causing a certain amount of mental strain on my player, I might have to say to myself, where do I want the mental strain? It's not that I don't want to have some mentally taxing cards, but I want to be careful that the mentally taxing cards are what contribute to making it fun. So here's another thing to remember, which is, I learned

this in my writing class. You as a writer, or as a designer, as a creative person, you have the ability, so this is actually, this was from film school, not from writing, but from, I had to take a cinematography class. And so what the class was teaching is, and this is true in writing too, but when you are making, so one of the things you're doing, and this is true in photography, cinematography is just photography that moves, essentially, is a lot of what photography and cinematography are about is where are you making the eye go? Where you, the person crafting the picture, will control where the eye of the person is.

And if you have contrasting things, so let's say, for example, I have a picture which is pretty muted and I have a red object. Your eye is going to go to the bright red object. Why? It's just the brightest thing. Your eye will go there. Now, let's say I have two bright objects. What happens? Well, I start to give up control where your eye is going to go.

Because your eye is going to go to one of the bright objects, but I don't know which one, because it can go to either object. So as a cinematographer, you learn conservation of your resources, which meant if you want to control where the eye of your viewer is going to go, you can't put two things at the same time that are going to draw their eye. If I want them to focus on a certain portion of the screen,

then I only get to have one eye-grabbing thing. And this philosophy carries right over to design, which is if I want my players to focus on something, if I pull them in too many directions, I don't control what their focus is. And so I have to think about what I'm trying to do. Now, that doesn't mean that in a game there can't be different focuses.

It's a little bit different than, obviously, in cinematography where they're looking at a singular screen at one moment. But you do have to think in the same sense, which is if I put too much stuff in, then I don't have the ability to control what my audience is supposed to appreciate and where they're supposed to look. If I overload my set and I put too many things in, that my audience doesn't know what's important. And I want them, I as an artist, want to lead and direct my audience in a certain direction.

I, for example, as a game designer, I'm trying to create experience for you. I want you to have fun gameplay. And I talk about this all the time, which is the players will go where you leave them, but if where you leave them isn't fun, they blame you, the game designer, because it's your job to lead them to fun.

It's their job to go where they're led. And that role of a game player more experienced game players actually do some self editing but most game players just say what does the game tell me to do? Well I'm going to do that and if the thing the game tells me to do isn't fun well they get mad at the game

and rightfully so they get mad at the game it's the job of the game to lead the game players to the fun to do that listen up game designers, to do that, you have to make clear messaging. In order to make clear messaging, you can't muddy your message. What that means is, you got to pick and choose what your messages are. You got to pick and choose your themes. You got to pick and choose your complexity. And all this shows up in common. All this matters in common. The reason that a vanilla creature is a wonderful thing is

I don't want people to focus on the vanilla creature. It does its job. It will be fun. If the spice is in your set in the right places, sometimes I talk about my cake metaphor, which is that icing is fun. And icing is sweet. And, and icing is tasty. But you know what? A cake full of icing isn't that good. You need the cake.

In fact, you need a lot more cake than you need icing. But the icing is the sweet thing, and so you need your design to have a lot of cake. If you want people to appreciate the icing, you also need to make sure you give them good cake to go with the icing. And some of that is basic effects, which is... And for example, one of the things that's really important is the idea that a vanilla creature doesn't require design is actually wrong. That there's a very different animal between a 1-4 and a 3-3 and a 5-2. You know, what are you trying to do?

What toughness matters in your set? What power matters in your set? Where's the threshold? Are you trying to make more stall-y? Are you trying to make more aggressive? Like, just literally how you design a vanilla creature matters. That this idea that, oh, I have a slot,

it's a vanilla creature, whatever. No, we take long time and energy trying to figure out the right mix of that vanilla creature. That, very easy trap to get into is assume that things that are simple don't require a lot of thought. And the funny thing is, the reverse is true. Usually, the less going on on a card, the more thought that's required to figure out how best to use it. Just because something is simple does not mean it plays a simple role.

And that's an important thing to remember. That sometimes the most important aspects of your set are not the wordy cards, but the simple cards. In fact, one of the signs that you are doing your job as a designer is that the cards that matter most are the most elegant cards. That is when you have aced your design, when you're like, this thing is a thing of beauty, and this thing that's a thing of beauty is very central to what I'm doing.

So when you're making common cards, you have to, I mean, the way I like to think of it is, I use a lot of metaphors today, Michelangelo used to explain, he was a sculptor, for those that don't know, and a painter, that when he sculpted, that he felt that the finished product was already in the marble slab,

that he was freeing it. That what he was doing was knocking away all the things that weren't it. And in some ways, you can think of designing commons like that, which is when you start with a common, make your common, and then start figuring out what the common has that it doesn't need.

One of the most common mistakes people make in their common cards is they make them, there's too much. They do too much, they have too much focus, there's too much complexity, there's too much words, there's just too much going on. That part of a good design is that each card has a very simple role it's supposed to play. And I know, I know, I know, I know it's hard. I mean, trust me, I get complexity creep.

I get wanting to do lots of things in your set. You know, that one of the things that's really hard is there is this desire to try to fit as much as you can fit in. But the goal of design is not, you're not measured by how much you get in the set. You're measured by what is there, how it plays. And oftentimes, less is more. That just because you can cram as much stuff as you, like cramming things in does not make for a better, and I'll just jump back to my cinematography example. I want to make a beautiful picture, you know, a beautiful photo, a beautiful movie shot. I could stick beautiful things in it, but at some point, if I stick enough beautiful

things in it, it stops being that beautiful. That part of what makes something beautiful is the crispness of a single image. Oh, look at that beautiful flower. Well, you know what? That beautiful flower and that beautiful baby, they're each really. Well, you know what? That beautiful flower and that beautiful baby, they're each really beautiful. But you know what? If you put the beautiful baby with a beautiful flower,

well, either people are going to look less at the baby or less at the flower. Something's going to suffer. Maybe they look less at both of them. And that if you want people to appreciate the simple flower, show the simple flower. If you want them to appreciate the beautiful baby, show the beautiful baby.

But showing the baby and the flower means you pull focus. And that's a big, big lesson in making commons, is don't pull your focus. Figure out what you want, and make sure that each card does the least amount it can do. Carve away everything that doesn't need to be there, and leave what needs to be there. Anyway, as you can see, see, I, you think something as common as common cards should be simple. In fact, no. It's a very complex situation. In some ways, I talked about how when you fit your car, you put the hardest thing in first. Another reason you do commons is commons actually are the hardest thing. I know people think because they're so simple that they're the easiest thing.

And what you learn as you do a lot of design is easy is hard. Simple is difficult. And that, my friends, is the lessons of the day. So thank you very much for listening to me. As always, I love talking about magic design. But even more, I like making magic. So it's time for me to go. Thanks for joining me today, guys,

and I hope you appreciate my little peek into making commons. Ciao.