Chapter 7 Key Takeaways

1. Constraints create the game, not limit it.
A game with no rules is not a sandbox --- it is a void. Constraints focus the player's attention, define the problem space, and transform "do whatever you want" into "figure out how to do what you want." The second is engaging. The first is aimless. Every interesting game in history is interesting because of its constraints, not despite them.

2. Rules operate on three layers: constitutive, operational, and implicit.
Constitutive rules are the abstract logic (what the code computes). Operational rules are what players do (what you would explain to a new player). Implicit rules are the unwritten contract (what players expect). A well-designed game aligns all three layers. When they misalign --- when the math says one thing, the player does another, and the expectation is a third --- the result is confusion, frustration, or betrayal.

3. Good rules create choices, not just situations.
A situation is an event that happens to the player. A choice is a moment where the player must decide between multiple viable options with differentiated outcomes and enough information to reason with. Bad rules produce situations. Good rules produce choices. If your game has long stretches without meaningful choices, the problem is in your rules, not your content.

4. Meaningful choices require trade-offs.
Every choice in your game should pass the "interesting trade-off" test: can you articulate what the player gains and what the player loses by choosing each option? If one option has no downside, it is not a choice. If the trade-off is unclear, the choice needs more information. If the trade-off is trivial, the choice needs higher stakes.

5. Constraints fuel creativity for both players and designers.
Hardware limitations produced Super Mario Bros., Pokemon, and DOOM. Game jams produce disproportionately creative games in 48 hours. The PICO-8 version of Celeste had 128x128 pixels and spawned a commercial masterpiece. When you can do anything, you waste time deciding what to do. When you can only do specific things, you spend time figuring out how --- and that is where creativity lives.

6. The possibility space is defined by rules, and its depth is determined by rule interactions.
Rules define the boundaries of what can happen in your game. But depth --- the number of meaningfully different strategies available to the player --- comes not from the number of rules but from how they interact. Chess has six piece types and more possible games than atoms in the universe. Baba Is You has two mechanics and hundreds of unique puzzles. Add rules slowly. Maximize interactions. Depth is multiplicative, not additive.

7. Fairness is a contract, and violating it destroys trust.
Players expect your game to be consistent, transparent, and honest. If a rule works one way in one room, it must work the same way in every room. If the player fails, they must understand why. If the player succeeds, it must be earned. "Unfair" is not the same as "hard." Hard games with fair rules produce determination. Hard games with unfair rules produce resentment. Players forgive difficulty. They do not forgive betrayal.

8. Rule-breaking is a design tool --- when used deliberately.
Baba Is You makes rule-breaking the core mechanic. Undertale uses it for emotional impact. The Stanley Parable uses it for meta-commentary. These work because expectations are established first and then subverted for a meaningful purpose. Rule-breaking without established expectations is just inconsistency. Rule-breaking with purpose is one of the most powerful moments a game can create.

9. Every new rule cascades through the entire system.
A game with 5 rules has 10 pairwise interactions. A game with 10 rules has 45. A game with 20 rules has 190. Adding one rule does not add one thing --- it adds interactions with every existing rule. This is why experienced designers obsess over elegance: maximum depth with minimum rules. Add rules slowly. Test after every addition. Remove rules that do not justify their interaction cost.

10. Write your rules down.
A written rule set forces implicit assumptions to become explicit. If you cannot write a clear, specific sentence describing a rule, you do not understand it well enough to implement it. Write the rule set. Share it with another person. If they understand your game from the document alone, your rules are clear. If they do not, your rules need work.

11. The rules you choose NOT to add are as important as the rules you add.
Chess has no randomness --- that absence makes every outcome a product of skill. Minecraft has no objectives --- that absence makes every goal a product of imagination. Every rule you do not add is freedom you give to the player. Make the choice deliberately. Create two lists: rules you are adding and rules you are deliberately not adding. The second list defines your game's identity as much as the first.

12. Rules have an aesthetic.
The rules you design express a feeling and a worldview. Dark Souls' rules say "this world is hostile but fair." Animal Crossing's rules say "this world is gentle and patient." Celeste's rules say "you will fail, but you will try again." When you design rules, you are not just designing a system. You are designing a feeling. The rules are what the player remembers, even when they think they are remembering the story.