Theme first or mechanics first? It doesn't matter.

DSC_0477_taoist_temple_yin_yang

Game designers often get asked whether they start with theme or mechanics, but I'm never quite sure what the questioner is hoping to glean about the process of game design. It seems to assume a binary, decoupled state of gameplay. It even seems to be the definitive divide in Euro/American game design. (We can address our very weird tendency to ascribe game design to either America and Europe another time, but that's worth discussing too.)

The truth is, if your game is working as it should, no one should be able tell whether you thought of the theme or the mechanics first.

If you focus too much on theme, the mechanics might be burdened with too much simulationist cruft. The game is inaccessible to all but the tiny demographic who really cares about how accurately you represented that theme. In my case, if I begin with a theme, I also spend a long time in development.

If you focus too much on mechanics, they might be too abstract. Your game might have a lot of depth, but that is only worthwhile if players can see that depth. A theme can help create the metaphors and allegories that make the strategy and tactics much more accessible.

So here's my ideal process, call it a sandwich. It's not right for everybody, and it might not even be right for me in a few years, but for now it's been the most efficient method for me to design fast and iterate rapidly.




1. Find an interesting interaction between people.
Haggling for a deal? Coming to an agreement? Divvying up resources? Bluffing? Getting rid of stuff while avoiding getting new stuff, or vice versa? There is usually a mechanical element implied in this interaction, often a slight twist on an existing mechanic from an existing game.

For example, I thought it would be interesting if players were forced to divvy up a supply of resources into different play spaces, those spaces would then score in different ways and reveal a little bit of information to other players about their long-term goals. You've seen this sort of gameplay in several games, including Guildhall and Biblios.



2. Find a theme that fits the interaction.
You often hear gamers complain about games whose theme feels "tacked on." As if the whole game had been designed and developed with no thematic input at all. To avoid this pitfall, I try to bring in the theme very early on into the design process.

For example, in order to score points, you have to reveal some cards and have matching cards hidden in your hand. Thus, players could see what you may be trying to score, but couldn't be absolutely sure. I saw the interaction between players as being sort of "coy." I couldn't resist the pun of "koi pond," so I pursued that theme.




3. Let the theme suggest secondary mechanics.
So at this point you might say I start with mechanics, and to some extent that is true. It would be more accurate to say I start with a mechanic, singular. But I go no further until I've found the right theme to fit that mechanic, then I filter any further development through that theme.

For example, I decided the game would be about koi ponds, in which players collect, display or release koi fish. What other elements of koi ponds might be interesting gameplay interactions? Perhaps a competition for visitors? Best decor? How about fish breeding? How about the pests that can be a nuisance to a koi pond? From all these questions came the secondary mechanics of Koi Pond: You deploy turtles, cranes and housecats in order to score points from your opponent's collections. You release koi to the river in order to win ribbons. Those river koi eventually flow into a central lake accessible to all players.



Okay, sure, you can call me a mechanics-first designer, but I'm also a mechanics-last designer. I'm thinking about theme and mechanics all the time, at the same time. My ideal is that both are so integrated with each other that the game just makes too much sense for the theme and mechanics to ever be decoupled. They're just supposed to be that way.

Comments

Post a Comment

Popular posts from this blog

5 Graphic Design and Typography Tips for your Card Game

Image
Chris Farrell of Illuminating Games just wrote a thorough critique of card games setting their body text to be so small that they cannot be read at arm's length, let alone across the table. Here's an excerpt, but the whole thing is worth a read for any would-be card game designers out there. (Myself included.) Break out your copy of the base set of Dominion, and look at the Chapel. This has a text box roughly 3.5cm by 4.5cm. It's got a single line of text. That line of text is 1 (one) millimeter high. 1mm! For me, it's only clearly readable at half an arm's length even in the bright light of day. (...) Compare this to a more sane game like Glory to Rome, where the font size is 2-3 times as large (text is 2mm high, keywords 3mm and usually highlighted). I can generally read Glory to Rome cards across the table, and can certainly see the important keywords. To heap insult upon injury, not only does Glory to Rome have far more legible text than Dominion it also has...
Read more

Low-High Dice Game

Image
A dice game inspired by the stock market (and playing lots of Martian Dice). Roll a bunch of dice and choose which sets to keep. Choose your strategy wisely! Stuff You Need Two-to-Six PLAYERS A PENCIL and PAPER to keep score Thirteen standard six-sided DICE How to Play The shortest player takes the first turn. On your turn, first roll all thirteen dice. Several dice will have matching results. These are called SETS. (A single die result is a set, too.) You must choose a set to keep. For example, your first roll results are 111124445555 . The sets are four 1 s, one 2 , three 4 s, and four 5 s. After keeping a set of dice, lock them up in a row. This is called the GOOD TRACK. For example,  you could keep the set of four 1 s, one 2 , three 4 s, or four 5 s . You decide to keep the four 1 s and line them up in your good track. After keeping a set, you may end your turn or re-roll the remaining unlocked dice. When you re-roll, immediately set aside any results tha...
Read more

One Thing to Avoid in Game Design

Image
When game designer Paul Peterson was interviewed for the upcoming Titans Series of games from Calliope Games, there was one segment at 1:55 that really caught my attention (emphasis mine): "A couple years ago I was teaching people how to play Guillotine and I hadn't played in a while. The first thing I did was say, 'The first thing you gonna do when you open your game is you look through this deck and you take this card.' I pulled out the Callous Guards card and threw it over my shoulder. Everybody laughed. I said, ' That's the biggest mistake I ever made as a game designer in my life.'" Oof. Those are strong words. What's the big deal? For context, the game Guillotine is all about collecting the heads of French nobles during the revolution. There is only one guillotine, with a line of nobles waiting for their grim fate. On your turn, you play action cards to change the order of the line, then take the Noble card from the front of the ...
Read more