ark Rosewater mentioned earlier this week that there are a few new types of cards in Mirrodin. You saw one of them on Tuesday when Paul Barclay introduced you to Equipment and now I get to preview the second: Artifact Land.
For such seemingly simple cards, I actually have a remarkable number of almost unconnected stories I want to tell. I’m not sure where else to start so I’ll just start at the beginning.
You have to go all the way back to Tempest to find a large expansion that does not include a cycle of common lands. Lands aren’t the most exciting aspect of the game, but everyone always has to include a bunch of them in every deck they build, so we like to give players options. In addition, for each of the last several blocks we’ve been able to find ways for the common lands to fit into the theme of the set, and we’ve been pleased with the way those land cycles have been relevant to Limited play in addition to Constructed.
Anyway, way back when Mirrodin was still called “Bacon,” the design team knew they wanted a cycle of lands at common, but they weren’t sure what to do. Their theme – artifacts – was already set, so they kept trying to come up with lands that interacted with artifacts somehow. For a while they had lands with activated abilities of each color, like “, : Regenerate target artifact” but that had a couple of problems. First of all, we require all of our lands to tap for mana (otherwise, why are they lands instead of artifacts or enchantments?), but then if you add on the ability to tap for colored mana these are strictly better than basic lands. So they require a drawback, like coming into play tapped. Well the design team felt we have been making too many lands with this drawback in recent sets so they wanted to avoid using it again, plus they were just generally discontent with the way the cycle was working out.
At some point in this process Mark Rosewater had the brainstorm: Rather than interacting with artifacts, couldn't they just be artifacts?! The set was already chock full of cards that rewarded you for having artifacts in play so that might solve the puzzle perfectly. The design team immediately latched onto Mark’s idea and playtesting quickly showed that artifact lands were indeed quite interesting to play with.
Story number two begins when the development team took control of the set. One of the most important things we try to do is “break” the cards. Usually that refers to the power-level of the card and “breaking” a card consists of building a deck that abuses it in a way that we deem to be degenerate. However, that’s certainly not the only way a card be broken. Sometimes, the development team will point out situations where a card is too confusing, or where it’s not even clear how the card is supposed to work. In the case of the artifact lands, these circumstances kept coming up.
All the design team told us was that “they’re lands, but they also count as artifacts.” At first blush, that sounds like plenty of information, but it’s actually not nearly enough. Can you Counterspell an artifact land? Well you can’t counter lands, but you can counter artifacts. Do you draw a card from Vedalken Archmage when you play an artifact land? We kind of wanted the answer to be “yes” but much more important than that we wanted the answer to be unambiguous. Does playing an artifact land use the stack? We knew this one probably wouldn’t make a difference very often, but playing an artifact does use the stack while playing a land doesn’t so it was at least another point that required clarification.
The development team definitely liked the way these interacted with the rest of the set, so we wanted to do them, but we were worried for a while that we wouldn’t be able to solve all of these problems. Pretty early on in development, I called a meeting with everyone who works on card wordings to try to figure out if there was a way to do these. The first thing that emerged from those meetings was a very astute analysis of the problem: the rules for playing an artifact contradict the rules for playing a land. Most of the time it’s no problem for a card to be both a land and an artifact. You just merge the rules for being an artifact with the rules for being a land, similar to the way Artifact Creatures merge the rules for artifacts and creature. However, lands get from your hand into play in a way very different from artifacts. Artifacts go on the stack and your opponent has an opportunity to respond to them (including an opportunity to counter them). Artifacts also trigger effects that trigger whenever a spell is played. Lands, on the other hand, do not use the stack, and cannot be countered, and don’t count as spells, and can only be played once per turn.
What we realized was that the key to doing these cards was to clarify which set of rules applied when you played an artifact land. We definitely needed them to use up your land drop for the turn, and we didn’t really want to allow players to Annul their opponents’ artifact lands, so we decided that they should follow the rules for playing lands (and not the rules for playing artifacts).
Having decided the functionality we wanted, we still had to figure out how to communicate that functionality unambiguously on the cards. Many different sorts of reminder text were proposed, most of which attempted to list out answers to all of the potentially ambiguous or confusing situations. For quite a while what we had in the file was “CARDNAME follows the rules for playing a land.” It wasn’t very friendly, and we weren’t sure that everyone would understand exactly what that meant so we kept trying to come up with something better.
What we actually wound up with might be the most bizarre reminder text of all time, but I’m actually happy with how it turned out. All we really needed to communicate was that, when you were playing the card, you were supposed to ignore the fact that it’s an artifact and just play it like you would play any other land. “This is not a spell” is a surprisingly simple and friendly way of pointing out exactly what we needed to point out. There’s no problem when the card is in your hand or when the card is in play; the only potential problems come when the card is in between your hand and play. Well, if you just remember that you don’t play it like a spell (because it follows the rules for playing a land instead) then you’ll never go wrong.
Of course, our solution made everyone happy except for Vedalken Archmage. As the lands are not spells, he won't draw you a card when you play one.
My third story has to do with the creative concepts that wound up on the cards and it begins long before anyone dreamed up these cards. With each new block, our creative team builds a world for the card set to take place in. They spend a lot of time making sure the world is coherent and consistent. Part of that process includes working out details about both the cosmology and geography of the world. So they invent all these interesting details about what cities are in the world, what the forest is like, where the goblins live, etc. However, in the past these locations wouldn’t usually get cards to represent them. Since these are specific places (as opposed to generic places like “Swamp” or “Lonely Sandbar”) they would most naturally go onto legendary lands, but we just don’t do nearly enough legendary lands to work all these cool locations into the set.
As Brady Dommermuth alluded to in a recent Ask Wizards answer, we’ve decided to change this policy. We’re now going to start depicting specific places on some of our nonbasic lands. The first lands to benefit from this new policy are the artifact lands. Each depicts one of the most important landmarks to the creatures of that color. You can read a lot more about these locations, and also about the plane of Mirrodin in general, if you pick up a copy of the Mirrodin “Fat Pack” in a couple of weeks. The Player’s Guide included in that product includes a nice spread on the way this world works. Additionally, Rei Nakazawa has an article on the same subject that will be running here on MagicTheGathering.com next week.
This new policy actually underwent a bit of development when we were working on Mirrodin. The names of the artifact lands initially included the specific names of the places in addition to a description, so they were things like “Tel-Jilad, the Tree of Tales” and “Taj-Nar, the First Den.” When we played with stickered-up versions of the cards with those names, they felt wrong. They were too grandiose for common – mostly because they were named using conventions that we only use on legendary permanents. We wound up dropping their proper names and then things felt much better. The proper names are still there, but we moved them into the flavor text.
At first I was nervous about previewing the artifact lands because they obviously depend on other cards before they actually do anything cool. In retrospect, however, I see that Aaron was right – there are lots of stories to tell about these lands. They’re pretty interesting even before you know what else is in the set. Plus this way we also get to tease you guys and let you speculate about all the different ways they might turn out to interact with the rest of the cards.
This Week’s Poll:
Which artifact land location seems the coolest to you?
Last Poll Results:
How old are you?
Randy may be reached at firstname.lastname@example.org.