Chapter 5 Key Takeaways

1. Mechanics are the verbs of your game.
A mechanic is a rule that defines what the player can do (input), how the system interprets it (rule), and what changes as a result (output). Listing a game's verbs is the fastest way to understand what it actually is. Every game, from Flappy Bird to Elden Ring, can be decomposed into a finite set of verbs.

2. The primary mechanic must feel good in isolation.
Your primary mechanic is the action the player performs most frequently. It must be satisfying to execute in an empty room with no enemies, no rewards, and no progression. If the primary mechanic is not intrinsically enjoyable, no amount of content or systems layered on top of it will fix the problem. Test it alone first.

3. Secondary mechanics serve the primary mechanic.
A secondary mechanic should expand the possibility space of the primary mechanic, not compete with it. Doom Eternal's glory kills and chainsaw kills exist to keep the player shooting. Celeste's wall-climb exists to extend the dash. If the player does the secondary mechanic more than the primary, investigate whether you have a hierarchy problem.

4. Progression mechanics can mask weak fundamentals.
Leveling systems, unlock trees, and crafting systems can keep a player engaged even when the moment-to-moment actions are not enjoyable. This is dangerous. When the progression runs out, the game collapses. Design the primary mechanic to be fun without progression, then add progression to make it more fun.

5. Classify mechanics to understand your game's profile.
Avatar mechanics (movement, combat) define what the player character does. Object mechanics (items, resources) define how things in the world behave. System mechanics (physics, economy, information) define how the world itself works. Most games have mechanics in all three categories, but the proportion determines the game's character.

6. The One Mechanic Test reveals your game's identity.
Describe your core mechanic in one sentence. If you cannot, your game lacks a clear identity. If the sentence could describe a dozen games, it is too vague. Be specific. "You time attacks and dodges against lethal enemies with deliberate, weighty combat" is a game. "You fight enemies" is a genre.

7. Mechanics are not meaning-neutral.
The same verb --- shooting, building, collecting --- carries different meaning in different games depending on the surrounding systems, narrative, and aesthetics. Shooting in Call of Duty is power fantasy. Shooting in Undertale is moral choice. Shooting in Spec Ops: The Line is moral indictment. Be aware of what your mechanics are saying, even when you are not intending them to say anything.

8. Mechanic clarity has three dimensions: discoverability, legibility, and predictability.
The player must be able to find the mechanic (discoverability), understand what happened when they used it (legibility), and anticipate what will happen before they use it (predictability). Failure in any dimension undermines the mechanic regardless of how well-designed the underlying system is.

9. Depth comes from interaction, not addition.
Adding mechanics increases the game's width. Making mechanics interact with each other increases its depth. Combinatorial depth --- the exponential growth of possibilities when mechanics combine and sequence --- is what separates games that sustain hundreds of hours from games that exhaust themselves in ten. Five mechanics that interact richly produce more depth than twenty mechanics that operate in silos.

10. Less is more.
Every mechanic you add costs learning time, content design, balancing effort, art and audio production, and testing. The greatest games in history are built on small mechanic sets polished to a mirror shine. Super Mario Bros. has five verbs. Celeste has five. Baba Is You has two. Start with one mechanic. Make it great. Add the second only when the game needs it. Stop before you think you should.

11. State machines enforce clean behavior.
The Player.gd state machine (IDLE, RUN, ATTACK) ensures that impossible states remain impossible. The player cannot move during an attack because the ATTACK handler does not read movement input. State machines scale from three states to thirty and are the professional standard for managing character behavior.

12. Build the foundation before the building.
Your core mechanic is the foundation on which your entire game rests. Test it in an empty room. Tune it until it feels right. Playtest it with someone who is not you. Do not move forward until the primary mechanic is satisfying. Everything else --- levels, enemies, story, progression --- depends on this foundation being solid.