Lesson 9 · Part 3: The Machinery

Rules and Mechanics

The small action-and-answer parts every game is built from, which rules to say out loud, and how to make the game's answers impossible to miss.

11 min read

Rules and Mechanics

Go find the cupboard where the board games live and tip a few boxes out onto the floor. (Ask first if they aren’t yours.) You’ll get a pile of dice, a couple of decks of cards, a sand timer, some pawns, a spinner with a slightly bent arrow, and a bag of little wooden cubes that nobody can remember the purpose of.

Now sort the pile by what each thing does. The dice make a number nobody chose. A shuffled deck hands things out in an order nobody knows. The sand timer turns dawdling into a cost. The pawns mark where you are. Here’s the funny part: games that play nothing alike, about pirates or farming or murder in a country house, are built from the same handful of little machines. The magic is in how they’re put together.

A mechanic is a part

A game mechanic is one small loop between a player and the game: something you’re allowed to do, and the way the game answers. Rolling a die and moving that many spaces is a mechanic. So is “draw a card, and if it matches the color on the pile, you can play it.” So is a locked door: you try to open it, the answer is “no,” and that “no” comes with a question attached about where the key might be.

In Level 8 we said a game is a kind of language, with nouns and verbs. Mechanics are its phrases. Each one is a short exchange you can have with the game, and playing is stringing those exchanges together into a conversation.

It helps to think of mechanics the way a mechanic thinks of a car. (Sorry. It had to be done.) There’s an engine, some wheels, brakes, a steering wheel. Almost all of those parts have been in thousands of other cars, and nobody thinks less of a car for having ordinary wheels. Now and then a design needs a part that doesn’t exist yet, and somebody invents one. Either way, nobody judges the part on its own. They judge how the whole car drives.

That matters if you’re starting out, because it’s tempting to think a game needs some never-before-seen mechanic to be worth making. Plenty of good designers work the other way around. Start with the experience you want people to have, then go shopping for the parts that produce it. If an old part does the job, use it. Invent a new one only when nothing on the shelf fits the gap.

“It’s more like this is the right mechanic, whether it was invented by me or somebody else.”

Will Wright

The one you do most

Most games have one mechanic that does the heavy lifting: the action you perform over and over, the one you’d mime if someone asked what the game was. That’s the core mechanic. In tag, it’s chasing and touching. In Jenga, it’s easing a block out of the tower without knocking it over. In a game of snap, it’s slapping the pile at the right moment. Everything else in those games exists to make that one action more interesting.

Getting the core mechanic right is worth a ridiculous amount of time, because the player is going to do it a thousand times. If pulling a Jenga block weren’t nerve-racking, no amount of clever scoring would save the game. A good test: strip away everything except the core mechanic and see if it’s still fun to do for five minutes. If it is, you’ve got a loop you can build on. If it isn’t, more parts won’t fix it.

Rules you announce, rules you hide

Every mechanic runs on rules, and you get to decide which ones you tell people. That’s the idea behind overt and hidden rules.

Overt rules are the ones you say up front: whose turn it is, what you’re trying to do, how a piece moves. In a board game, they’re in the rulebook. In a video game, they used to live in a printed manual, and these days they’re usually folded into the first few minutes of play, the onboarding we met in Level 8. Either way, the player needs these to even begin.

Hidden rules are the ones players work out for themselves. Nobody tells you that in hide-and-seek, the best spots are the ones the seeker checked first. Nobody tells you that the cards left in a deck are worth counting. Hidden rules give a game depth, because they leave something to figure out. If every rule were printed on the box lid, the game would be a diagram you’d already read. When some of the machinery stays out of sight, players keep poking at it, building and testing their mental model, and the poking is a big part of the fun. Finding a hidden rule is one of the nicest kinds of discovery.

So, when you write rules, sort them into two piles: what players must know to start, and what they’ll enjoy figuring out. Start with the smallest first pile you can get away with.

The game has to answer clearly

Here’s a thing about people that’s worth knowing: we’re cause-hunting machines. If a light flickers or a floorboard creaks, your brain starts building a theory before you’ve decided to think about it. Was that me? Is someone there? Players do exactly the same thing inside a game, even when an event was pure coincidence, and they usually assume the cause was something deep and meaningful. Every player is running a little hypothesis loop in their head: guess what caused that, try something, check what happens, guess again. Your job is to give that loop good material to work with.

That gives you two kinds of event to manage. Signal is anything that carries real information. Noise is everything else: background bustle, decoration, the world getting on with its business. Some noise is lovely. A market full of chatter feels alive in a way an empty one doesn’t. The trouble starts when players can’t tell which is which.

The most important signal is the game’s answer to the player’s own action. That answer is called player feedback, and it has to stand out from everything around it. Think of a pedestrian crossing button. Good ones click when you press them, and a light comes on that says “WAIT.” That’s feedback. Bad ones do nothing visible, so you stand there pressing them six more times, wondering if anything is happening. When feedback disappears into the background, players never learn that the mechanic exists at all.

Clear answers make losing feel fair

Clear feedback does one more job. When you lose, it tells you why. In Level 10 we’ll call that fairness: the feeling that your losses trace back to something you did. A player who can see the cause of their failure can learn from it and try again. A player who can’t just feels cheated.

So the craft of mechanics boils down to three habits. Choose parts that make the experience you’re after, whether they’re old or new. Tell people only what they need to start, and leave the rest to discover. And make sure that whenever a player does something, the game’s answer is the loudest, clearest thing on the table.

Try it · Pocket Game, step 9Name the parts

Lay your Pocket Game out and list every mechanic in it as if you were labeling parts on a workbench: “flick to move,” “capture by landing on,” “three tries per turn.” Give each one a two-word name. Circle the one players do most. That’s your core mechanic. Now swap one of the other parts for a different one that does a similar job. “Three tries” might become “count slowly to ten,” for example. Play a round each way, and keep whichever version gave you the better round.

Carry forward: Pick the parts that make the experience you want, then make every answer the game gives the clearest thing on the table.