Appendix G: Design Pattern Catalog
Software engineers have the Gang of Four patterns book. Architects have A Pattern Language. Game designers have… a loose collection of blog posts, GDC talks, and folk wisdom passed down via Twitter threads. This appendix is an attempt to assemble a practical catalog of the patterns that show up across game design so often they deserve names, definitions, and a section you can flip to when you hit the problem they solve.
A pattern is not a formula. It is a shape. A design pattern says: here is a recurring problem; here is a recurring shape of solution; here is when that shape works and when it breaks. You do not apply a pattern the way you apply a recipe. You apply it the way a jazz musician applies a chord progression — as a framework you decorate with the specifics of your particular project.
Use this catalog as a reference, not a menu. Reading patterns end-to-end is a survey. Picking up the catalog when you are stuck on a specific problem is where it earns its keep. Each entry follows the same structure: Name, Also Known As, Problem, Solution, Examples, When to Use, When NOT to Use, Related Patterns, Chapter Reference.
Thirty-five patterns. Eight categories. Let's start.
MECHANICS PATTERNS
1. Core Loop
Also Known As: Gameplay loop, primary loop, compulsion loop.
Problem: Players need a repeatable, satisfying cycle of action and reward that defines what the game is, moment to moment. Without a defined loop, a game is a collection of disconnected activities that fails to cohere.
Solution: Identify a 10-to-60-second sequence of actions that the player will repeat hundreds or thousands of times. Engineer that sequence to be intrinsically satisfying, so repetition is pleasurable rather than tedious. Build everything else on top of it.
Examples: Tetris (piece falls → rotate → place → clear lines → next piece). Doom (see enemy → shoot → dodge → pick up loot → next enemy). Stardew Valley (water crops → chop trees → mine → return → sleep → next day). Hades (enter room → fight → choose boon → next room). Dead Cells (explore → fight → loot → die → restart with upgrades).
When to Use: Every game. This is the root of the design tree. Skip it at your peril.
When NOT to Use: There is no "not using" this. What exists is "not identifying it explicitly," which is a mistake. Even narrative-heavy games have core loops (walk → dialogue → choose → consequence).
Related Patterns: Risk/Reward, Variable Ratio Reward, Flow Channel.
Chapter Reference: Chapter 6 (The Core Loop).
2. Risk/Reward
Also Known As: Cost-benefit, stake-payoff.
Problem: Players need meaningful decisions. If every action has equal risk and equal reward, there are no decisions, just inputs.
Solution: Offer the player a choice between a safer option with a smaller payoff and a riskier option with a larger payoff. The risk can be resource cost, time cost, damage, opportunity cost, or failure probability. What matters is that the player must weigh something.
Examples: Spelunky (grab the idol for gold, but it triggers a trap). Dark Souls (keep souls you've earned by retreating, or push on for more and risk losing all). Risk of Rain 2 (time scales difficulty; loot longer gets more loot but faces harder enemies). XCOM (take the high-percentage shot or save it for a better angle next turn).
When to Use: When you want player decisions to feel meaningful. Anywhere the player has agency over resource expenditure.
When NOT to Use: In zen / flow / relaxation games where decision pressure would break the mood. Abzû does not need risk/reward; the experience is the experience.
Related Patterns: Push-Your-Luck, Resource Management, Core Loop.
Chapter Reference: Chapter 10 (Randomness and Probability), Chapter 12 (Motivation and Reward).
3. Rock-Paper-Scissors
Also Known As: Triangle of counters, intransitive balance.
Problem: Balance in games with multiple strategies, units, or weapons. If one option is strictly best, everyone uses it and the others become dead content.
Solution: Design three (or more) options such that each beats one and is beaten by another in a cyclic relationship. A beats B, B beats C, C beats A. No option is strictly dominant, so the player must read the situation and adapt.
Examples: StarCraft (Terran Marine → Protoss Zealot → Zerg Zergling in rough triangles). Pokémon (fire → grass → water → fire). For Honor (top/left/right attack stance counters). Mount & Blade (cavalry beats archers, archers beat infantry, infantry beats cavalry when braced).
When to Use: Competitive multiplayer; strategy games with unit selection; fighting games with stance systems.
When NOT to Use: Single-player experiences where the "counter" is obvious and becomes rote. Over-applied, RPS creates artificial friction — players hunt the counter instead of experimenting.
Related Patterns: Asymmetric Roles, Combo System.
Chapter Reference: Chapter 26 (Combat Design).
4. Resource Management
Also Known As: Economy pressure, scarcity design.
Problem: How do you generate interesting decisions across the length of a play session without constantly requiring reflex challenges?
Solution: Make at least one resource scarce. Force the player to allocate it across competing demands. Every allocation becomes a decision.
Examples: Civilization (gold, science, culture, production all trade off). FTL (fuel, missiles, drone parts, scrap — choose what to spend on). Frostpunk (coal, food, wood, steel, children). Into the Breach (grid squares to cover, turns to plan, power to spend).
When to Use: Strategy games, survival games, RPGs, roguelikes, anywhere you want decisions without real-time pressure.
When NOT to Use: Action games where resource-counting interrupts flow. In Doom Eternal, resources refill through play so the loop never stops; that is the opposite pattern.
Related Patterns: Sink/Source, Risk/Reward, Faucet and Drain.
Chapter Reference: Chapter 24 (Game Economy Design).
5. Push-Your-Luck
Also Known As: Press-your-luck, escalating commitment.
Problem: Create tension in a low-information environment where the player must repeatedly decide whether to continue or stop.
Solution: Offer the player an action that accumulates reward each time they take it, but also accumulates risk. At any moment, they can stop and keep what they have — or push once more for a bigger prize, with a non-trivial chance of losing everything.
Examples: Slay the Spire's relic events (take the reward, or keep opening chests). Balatro's hand-scoring (stop scoring now with your current multiplier, or roll for bigger). Dicey Dungeons (reroll for a better face, but each reroll costs). Dungeon Dice-style board games; blackjack itself.
When to Use: Games that want a tension arc without requiring mechanical skill. Great for turn-based roguelikes.
When NOT to Use: Games with no "bail-out" point. Push-your-luck requires the option to stop; if the player cannot choose to walk away, the pattern is just escalating difficulty.
Related Patterns: Risk/Reward, Variable Ratio Reward.
Chapter Reference: Chapter 10 (Randomness and Probability).
6. Production Line / Factory
Also Known As: Optimization game, throughput design.
Problem: Create satisfaction from the act of optimization itself — building, refining, and scaling systems of production.
Solution: Give the player inputs (raw resources), outputs (refined products), and a toolkit (machines, belts, logic) for transforming the former into the latter. The "fun" is in designing the pipeline. Scale incrementally — each new output unlocks more complex inputs.
Examples: Factorio, Satisfactory, Dyson Sphere Program (the genre defining trio). Shapez (abstract factory). Mindustry (factory + tower defense). Big Pharma (factory for medicine). Infinifactory (puzzle factory).
When to Use: You want deep replayability from emergent complexity, and your audience enjoys systems thinking. Long play sessions are expected.
When NOT to Use: Casual audiences. The onramp to factory games is steep; they alienate players who do not find optimization intrinsically rewarding. Short sessions are impossible — minimum satisfying play is ~30 minutes.
Related Patterns: Emergence, Resource Management.
Chapter Reference: Chapter 9 (Emergence), Chapter 24 (Game Economy Design).
7. Deck Building
Also Known As: Progressive toolset, card-driven character construction.
Problem: Give the player a feeling of growing power and personalization while keeping decisions strategic. Flat stat-growth is boring; hand-picked loadouts are too front-loaded.
Solution: Start the player with a small, weak set of tools (cards, abilities, items). Over the course of play, they acquire new tools, choose which to keep, and build an increasingly synergistic set. The player's identity IS the deck.
Examples: Slay the Spire (genre defining — cards as abilities, choose one of three after each fight). Hearthstone (classic deckbuilder). Monster Train (deckbuilding + lane strategy). Inscryption (deckbuilding + horror). Hades (boons function as a run-specific deck). Balatro (jokers build a deck of modifiers).
When to Use: Runs-based games (roguelikes, roguelites) with 30–90-minute sessions. Games where "who the player is" should vary per run.
When NOT to Use: Games where the player character should have a stable identity across play. Dark Souls would be a worse game if your abilities rerolled every run.
Related Patterns: Skill Tree, Combo System, Power Creep.
Chapter Reference: Chapter 25 (Progression Systems).
8. Combo System
Also Known As: Chain, sequence bonus, synergy.
Problem: Reward skilled execution. Give players a reason to go beyond "did the thing" to "did the thing elegantly."
Solution: Chain individual actions into sequences that produce bonus effects greater than the sum of parts. The combo may multiply damage, increase score, or unlock special moves. It breaks if the player stops or fails, creating tension.
Examples: Devil May Cry (stylish combat ranks). Tony Hawk's Pro Skater (combo meter is the entire game). Bayonetta (attack strings). Crypt of the NecroDancer (rhythm combo multiplier). Cuphead (parry-chain for super meter). Balatro (hand-type combos).
When to Use: Action games, score-attack games, rhythm games. Anywhere mastery should visibly reward the player.
When NOT to Use: Puzzle games or strategic games where individual decisions should stand on their own. Combos in turn-based combat often degenerate into single "optimal chain" solutions.
Related Patterns: Deck Building, Variable Ratio Reward.
Chapter Reference: Chapter 26 (Combat Design).
PROGRESSION PATTERNS
9. Skill Tree
Also Known As: Talent tree, ability web, unlock graph.
Problem: Give players long-term progression choices without overwhelming early decisions. Support diverse builds and replayability.
Solution: Arrange unlockable abilities in a branching graph. Starting points are simple; deeper branches require earlier unlocks. Players earn currency (XP, skill points, resource) and spend it along paths, making the tree a visible record of who they are.
Examples: Path of Exile (genre-extreme — a passive tree the size of a constellation). The Witcher 3 (skill trees per discipline). Horizon Zero Dawn (combat / stealth / collector trees). Borderlands (character-specific trees). Diablo IV (skill-and-talent hybrid tree).
When to Use: RPGs, long games (20+ hours), games with build diversity as a selling point.
When NOT to Use: Short games. A skill tree needs 10+ hours to earn; in a 3-hour game it is just noise. Also avoid when every branch unlocks strictly better versions of earlier skills (that is just XP with extra steps).
Related Patterns: Deck Building, Ability-as-Key, Power Creep.
Chapter Reference: Chapter 25 (Progression Systems).
10. Ability-as-Key
Also Known As: Metroidvania gating, power-as-gate.
Problem: Gate areas without using literal keys or arbitrary walls. Make progression feel earned through capability, not token collection.
Solution: When the player gains a new ability, they can now access areas that ability permits. Double jump reaches higher ledges. Water breathing lets them enter the flooded cave. Wall climb opens the mountain. Backtracking becomes rewarding because old areas reveal new paths.
Examples: Metroid (the pattern's namesake genre). Castlevania: Symphony of the Night. Hollow Knight (mantis claw, monarch wings, crystal heart). Ori and the Blind Forest. Celeste (feather, dream-jump — variant version). Tunic (the sword itself is a late-game ability-key).
When to Use: Metroidvanias. Open-world games with capability-gated regions. Any game where you want backtracking to feel rewarding.
When NOT to Use: Linear games where players are not expected to revisit areas. Ability-gating with no backtracking is just arbitrary locks.
Related Patterns: Skill Gate, Skill Tree, Hub World.
Chapter Reference: Chapter 19 (World Design), Chapter 25 (Progression Systems).
11. Power Creep
Also Known As: Escalating scale, numbers inflation.
Problem: Keep the game feeling exciting as players progress. Later content must feel more significant than early content.
Solution: Progressively increase the scale of numbers (damage, HP, enemy count, resource volume) so later play has bigger numbers and larger effects than earlier play. Handled well, this creates a sense of growth; handled poorly, it creates unbalanced content and invalidates early gameplay.
Examples: Diablo series (carefully tuned power creep across acts). Disgaea (intentional absurd-scale power creep — damage numbers in the millions). Warframe (weapons and frames scale over years of post-launch updates). Cookie Clicker (the entire game IS power creep).
When to Use: RPGs, action games with progression, clicker/idle games.
When NOT to Use: Competitive multiplayer where power creep = balance nightmare. Skill-expression games like Celeste where the challenge is consistent movement mastery, not numerical growth. Power creep in a Tetris would destroy it.
Related Patterns: XP Curve, New Game+, Skill Tree.
Chapter Reference: Chapter 25 (Progression Systems), Chapter 32 (Game Balancing).
12. XP Curve
Also Known As: Leveling curve, experience scaling.
Problem: Pace the feeling of progression across a game. Levels cannot come too fast (rewards become meaningless) or too slow (grind).
Solution: Design a mathematical curve where each level requires more XP than the last. Common shapes: linear (every level +1000 XP), polynomial (level² ×100), exponential (each level 1.5× previous). The curve must match the pacing of content: levels should arrive roughly when new content is ready to greet them.
Examples: Final Fantasy series (polynomial). World of Warcraft (tuned to expansion-length). Runescape (notoriously slow late-game curve, by design). Disco Elysium (almost flat curve — leveling is frequent but small).
When to Use: RPGs, MMOs, any game with character levels.
When NOT to Use: Games where growth is discrete (unlock-based), not numerical. Games with no progression at all (puzzle games, competitive shooters without progression).
Related Patterns: Power Creep, Skill Tree, New Game+.
Chapter Reference: Chapter 25 (Progression Systems), Chapter 32 (Game Balancing).
13. New Game+
Also Known As: NG+, Carryover replay, Tempered replay.
Problem: Extend engagement past credits. Reward players who want to replay with something beyond "the same game again."
Solution: After finishing the game, let the player start over with selected progression retained — abilities, levels, equipment — but with new challenges scaled to match. Often includes enemies scaling up, new content unlocked, or twist versions of existing encounters.
Examples: Chrono Trigger (originated the term in 1995). Dark Souls series (NG+ through NG+7 with scaling). Nier: Automata (NG+ is actually new narrative content, not just harder). Hades (Heat system is NG+ by another name). Tunic (a second-layer puzzle that is, effectively, a hidden NG+).
When to Use: Games with strong moment-to-moment play that some players will want to revisit. Games with narrative that benefits from re-reading.
When NOT to Use: Games where mechanical mastery has a ceiling that ~15 hours already hits. Shorter games often benefit more from branching outcomes than NG+.
Related Patterns: Power Creep, Skill Tree.
Chapter Reference: Chapter 25 (Progression Systems), Chapter 39 (Post-Launch).
SOCIAL / PSYCHOLOGICAL PATTERNS
14. Flow Channel
Also Known As: Flow state design, difficulty curve.
Problem: Keep the player in the sweet spot between boredom (too easy) and frustration (too hard). This is the zone where flow — the psychological state of full engagement — happens.
Solution: As the player's skill grows, increase challenge in step. Design a "channel" where challenge tracks skill — never static, never ahead, never behind. The channel can oscillate (spike-then-recover) for dramatic pacing, but its center line rises with player capability.
Examples: Celeste (every chapter's difficulty curve, with Assist Mode as explicit flow-channel widening). Hades (Heat system lets players choose their flow channel). Portal (each chamber is one notch harder than the last, with perfect incremental teaching).
When to Use: Every single-player action or puzzle game. This is foundational.
When NOT to Use: Cannot not use it; you can only do it well or badly. A game without any flow-channel thought is a game that bores or frustrates players, not a game that skipped the pattern.
Related Patterns: Challenge Gate, Core Loop, Coyote Time.
Chapter Reference: Chapter 11 (Flow), Chapter 13 (Challenge and Mastery).
15. Variable Ratio Reward
Also Known As: Skinner-box schedule, random reward.
Problem: You want players to repeat an action many times without it feeling routine.
Solution: Reward the action unpredictably. Most iterations produce nothing exciting; occasional iterations produce significant rewards. This is the same schedule that slot machines use — it is the most psychologically sticky reinforcement pattern known to behavioral science, which is exactly why it requires ethical care (Chapter 33).
Examples: Diablo (loot drops). Hearthstone (pack openings). Genshin Impact (gacha). Spelunky (chest contents). Any mob-loot RPG. Most modern mobile games.
When to Use: When you want to extend play time through anticipation, and you have considered the ethical implications (Chapter 33).
When NOT to Use: When the underlying loop is not fun on its own. Variable-ratio reward attached to a boring loop produces addiction without enjoyment — the pattern becomes exploitative. Also avoid in competitive contexts where the random reward creates unfair outcomes.
Related Patterns: Push-Your-Luck, FOMO, Streak, Core Loop.
Chapter Reference: Chapter 12 (Motivation and Reward), Chapter 33 (Game Design Ethics).
16. Streak
Also Known As: Daily login, consecutive bonus, momentum reward.
Problem: Build habitual engagement. Encourage regular play without constant novelty.
Solution: Reward the player for consecutive actions — consecutive days logged in, consecutive wins, consecutive days meditated. Break the streak, lose the bonus. The pressure to "not break the chain" drives return visits.
Examples: Duolingo (the canonical streak design). Destiny 2 (weekly powerful engrams). Fortnite (daily challenges). Candy Crush (daily-play rewards). Slay the Spire (daily climb scores).
When to Use: Live-service games, free-to-play games, retention-focused products where regular engagement is the business model.
When NOT to Use: Single-player narrative games. Games where play should feel optional and joyful, not compulsory. Streaks can become anxiety — the "I don't want to lose my 400-day streak" treadmill. Be ethically careful (Chapter 33).
Related Patterns: Variable Ratio Reward, FOMO, Collectible.
Chapter Reference: Chapter 12 (Motivation and Reward), Chapter 33 (Game Design Ethics).
17. Collectible
Also Known As: Completionism, set-completion drive.
Problem: Give players an optional, self-directed goal that extends engagement without requiring new content per unit of content.
Solution: Scatter discrete collectible items throughout the world. The player's drive to complete the set provides motivation. Collectibles can be purely cosmetic (achievements), mechanically meaningful (upgrades), or narratively meaningful (lore).
Examples: Hollow Knight (grubs, charms, journal entries — every collectible both rewards and informs). Breath of the Wild (Korok seeds, 900 of them). Assassin's Creed series (feathers, flags, whatever the trope is that year). Tunic (pages of the manual). Donkey Kong 64 (the cautionary tale — 201 of each of five collectibles).
When to Use: Open-world games, exploration-driven games, games with rich worlds that benefit from extended inhabiting.
When NOT to Use: Short linear games where collectibles pad length. Games where collectibles feel mandatory when they should be optional. Collectibles with no payoff beyond existence (the Donkey Kong 64 problem).
Related Patterns: Ability-as-Key, FOMO, Breadcrumb.
Chapter Reference: Chapter 14 (Curiosity and Exploration), Chapter 19 (World Design).
18. FOMO
Also Known As: Fear of missing out, limited-time pressure, scarcity marketing.
Problem: (From a business perspective.) Drive conversion, engagement, and spend. (From a design perspective:) Create urgency in a long-running live game.
Solution: Limit the availability of content, rewards, or items to a specific time window. After the window closes, the content is gone. Players who want it must act within the window.
Examples: Fortnite (seasonal battle passes). Genshin Impact (limited-time character banners). Destiny 2 (vaulted content). Animal Crossing (holiday-specific items). Overwatch (seasonal skins).
When to Use: Live-service games that need rhythm and event structure. Limited-time events (as opposed to permanently missable content) can be legitimate narrative pacing.
When NOT to Use: Standalone games. FOMO in a non-live game is just cruel. Also ethically fraught — when FOMO exploits compulsion, it crosses from design into manipulation (Chapter 33). If you use this pattern, watch the ethical line and do not encourage purchase-under-pressure from minors.
Related Patterns: Streak, Variable Ratio Reward, Collectible.
Chapter Reference: Chapter 33 (Game Design Ethics).
19. Asymmetric Roles
Also Known As: Asymmetric gameplay, hidden role, one-vs-many.
Problem: Create distinct, non-identical experiences for players in the same multiplayer session. Different roles, different objectives, different tools.
Solution: Assign players different roles, capabilities, or information at session start. Player A has one experience; Player B has another. Victory conditions may differ. Tools may differ. The fun comes from the collision of asymmetric systems.
Examples: Dead by Daylight (one killer vs. four survivors). Evolve (one monster vs. four hunters). Hidden in Plain Sight (couch multiplayer with hidden-identity roles). Keep Talking and Nobody Explodes (one sees the bomb, one reads the manual). Among Us (crew vs. impostors). Destiny 2 Trials (asymmetric power within a shared frame).
When to Use: Multiplayer games where you want to create distinct experiences per role. Co-op games where specialization is satisfying.
When NOT to Use: Competitive games where fairness across players is paramount (ranked PvP generally demands symmetry). Small-audience games where matchmaking cannot consistently fill both sides of the asymmetry.
Related Patterns: Rock-Paper-Scissors, Companion Bond.
Chapter Reference: Chapter 28 (Multiplayer Design).
LEVEL DESIGN PATTERNS
20. Hub World
Also Known As: Central space, sanctuary, nexus.
Problem: Connect multiple levels or missions in a coherent structure. Give players a "home" to return to between expeditions.
Solution: A central safe area from which multiple paths or portals lead to game content. The hub itself is often populated with NPCs, services, and small interactions. Progress feels cyclical: expedition → return → upgrade → expedition.
Examples: Dark Souls (Firelink Shrine). Hollow Knight (Dirtmouth). Destiny 2 (the Tower). Hades (House of Hades — perfectly integrated with narrative). Super Mario 64 (Princess Peach's castle). Risk of Rain 2 (each stage's drop site, looser interpretation).
When to Use: Games with discrete levels or missions, especially with meta-progression. Roguelikes, metroidvanias, mission-based action-adventures.
When NOT to Use: Seamlessly continuous worlds (Breath of the Wild, Elden Ring) where a hub would break the open-world illusion. Linear games with no branching — no point in a hub if there is one path.
Related Patterns: Safe Room, Ability-as-Key, Hub-and-Spoke narrative.
Chapter Reference: Chapter 19 (World Design).
21. Breadcrumb
Also Known As: Visual pull, affordance trail, sightline.
Problem: Guide the player through space without explicit directions that break immersion.
Solution: Use visual language — light, color, motion, scale, contrast — to create focal points that pull the player's eye forward. The player chooses to follow because following feels right, not because a quest marker tells them to.
Examples: Half-Life 2 (often cited as the textbook case — light, scripted motion, color). Journey (the mountain on the horizon). The Last of Us (yellow paint on climbable surfaces, a debated but functional signal). Dishonored (rooftop silhouettes in the middle distance).
When to Use: Linear or semi-linear levels where you want to direct flow without UI. Narrative-driven spaces.
When NOT to Use: Open exploration games where the player's curiosity should determine direction. Puzzle games where "figuring out where to go" is the point.
Related Patterns: Environmental Storytelling, Ability Gate, Safe Room.
Chapter Reference: Chapter 17 (2D Level Design), Chapter 18 (3D Level Design).
22. Skill Gate / Ability Gate
Also Known As: Lock-and-key, capability check.
Problem: Prevent the player from reaching content they are not ready for, whether mechanically or narratively.
Solution: Place an obstacle that requires a specific skill or ability to pass. The player cannot brute-force their way through. Until they have the skill (earned through practice) or ability (unlocked through progression), the content is unreachable.
Examples: Dark Souls (the Capra Demon, effectively a skill gate for new players). Celeste (B-side and C-side chapters, gated on proving A-side mastery). Hollow Knight (many areas gated on traversal abilities). Super Mario Odyssey (moon-count gates to new kingdoms). Castlevania: SotN (the lycanthrope ability).
When to Use: Metroidvanias (ability gates), challenge-progression games (skill gates), any game with mechanical mastery as a pacing tool.
When NOT to Use: Games where the player should always have access to the full toolkit. Adventure games where narrative gates, not mechanical ones, do the pacing.
Related Patterns: Ability-as-Key, Flow Channel, Boss Gauntlet.
Chapter Reference: Chapter 13 (Challenge and Mastery), Chapter 19 (World Design).
23. Safe Room
Also Known As: Sanctuary, save room, bonfire, checkpoint.
Problem: Give players a moment of recovery between high-pressure content. Let them save progress, heal, plan, and breathe.
Solution: Periodically punctuate dangerous space with designated safe zones. Enemies cannot enter. Saves can happen here. Healing restores. The pacing of a level is largely defined by the rhythm of safe-room placement.
Examples: Resident Evil series (the trope's namesake — the save room with the typewriter and the calm music is iconic). Dark Souls (bonfires). Hollow Knight (benches). Celeste (every sub-chapter break). Metroid (save rooms). Hades (between-run hub is a macro-scale safe room).
When to Use: Tense, difficulty-driven games where players need recovery rhythm. Long sessions where quit-points matter.
When NOT to Use: Roguelikes where permadeath is the point. Short session games where safe rooms would slow the pace.
Related Patterns: Hub World, Flow Channel, Boss Gauntlet.
Chapter Reference: Chapter 16 (Level Design Fundamentals), Chapter 19 (World Design).
24. Boss Gauntlet
Also Known As: Boss rush, final gauntlet, culmination sequence.
Problem: Provide climactic late-game challenge that tests the full range of skills the player has developed.
Solution: A sequence of difficult encounters, typically bosses, delivered back-to-back with limited or no recovery between them. Tests not just skill but stamina, resource management, and pattern recall.
Examples: Mega Man games (always end with a boss rush). Cuphead (the Mausoleum gauntlet). Hollow Knight (Path of Pain, Pantheon of Hallownest). Dark Souls III (Ashes of Ariandel / Ringed City endings). Celeste (B-side and C-side ending gauntlets).
When to Use: Games with multiple bosses where a culmination is narratively or mechanically appropriate. Post-game challenge content.
When NOT to Use: Games without strong boss design in the first place — a gauntlet of mediocre bosses just multiplies the mediocrity. Narrative-focused games where a gauntlet would clash with story pacing.
Related Patterns: Skill Gate, Flow Channel, Safe Room.
Chapter Reference: Chapter 26 (Combat Design).
25. Optional Difficult Challenge
Also Known As: Skill-check side content, challenge dungeon, secret boss.
Problem: Cater to skilled players who want more, without punishing casual players who do not. Provide a ceiling of challenge beyond what the main game requires.
Solution: Add content — bosses, levels, challenges — that is significantly harder than the main path but entirely optional. Reward completion with bragging rights, cosmetics, or gameplay bonuses. Never place progression-critical rewards inside.
Examples: Super Meat Boy (dark-world levels). Celeste (B-sides, C-sides, Farewell chapter). Hollow Knight (White Palace, Path of Pain). Dark Souls (optional bosses like Nameless King). Ratchet & Clank (weapon mastery challenges).
When to Use: Games with a broad skill distribution in the audience. Games that want to reward the top 5% without gating content behind them.
When NOT to Use: When rewards locked behind the challenge are required for full progression — that crosses the line from optional to mandatory. Also when the optional content is not clearly labeled as harder; surprising casual players with a wall creates frustration.
Related Patterns: Skill Gate, Boss Gauntlet, New Game+.
Chapter Reference: Chapter 13 (Challenge and Mastery), Chapter 16 (Level Design Fundamentals).
NARRATIVE PATTERNS
26. Branching Dialogue
Also Known As: Choice tree, dialogue tree.
Problem: Give the player agency in narrative moments without requiring branching full-motion cutscenes.
Solution: At dialogue points, present the player with multiple response options. Different options produce different responses, sometimes different outcomes, and sometimes diverge the plot. Graphically organized as a branching tree; often implemented via a node-based tool.
Examples: Disco Elysium (dialogue IS the game, at an exceptional level). Mass Effect (signature dialogue wheel). The Witcher 3 (choices with delayed consequences). Oxenfree (interrupt-driven dialogue). Pentiment (dialogue-driven narrative detective game). 80 Days (nearly pure dialogue-as-game).
When to Use: Narrative-driven games, RPGs, adventure games, games where player voice matters.
When NOT to Use: Action games where dialogue interrupts flow. Games with large linear narratives that do not benefit from branching. Branching dialogue in an action-platformer is usually a drag.
Related Patterns: Companion Bond, Unreliable Narrator, Environmental Storytelling.
Chapter Reference: Chapter 21 (Dialogue and Characters).
27. Environmental Storytelling
Also Known As: World-as-narrator, show-don't-tell level design.
Problem: Tell story without stopping gameplay. Deliver exposition, mood, backstory, or character through what the player sees, not what they are told.
Solution: Embed narrative in the environment itself. A skeleton clutching a letter. A barricaded door with scratches on it. A child's drawing pinned to a wall. The player reads the scene like a detective, assembling story from evidence.
Examples: Dark Souls (the gold standard — entire plot delivered via level geometry and item descriptions). Gone Home (the genre-defining example, story IS the environment). BioShock (underwater dystopia told through architecture). Inscryption (the cabin as narrative). Tunic (a manual discovered page by page in-world).
When to Use: Any game where environment is present. This is a force multiplier — even a pure action game can add layers via environmental storytelling at near-zero cost.
When NOT to Use: Games where players skip environments entirely (bullet-hell shooters, rhythm games). Games with such fast pacing that players cannot pause to read the world.
Related Patterns: Breadcrumb, Unreliable Narrator, Collectible.
Chapter Reference: Chapter 22 (Environmental Storytelling).
28. Companion Bond
Also Known As: Buddy system, relational progression, partner.
Problem: Create emotional stakes via a non-player character the player grows attached to. Drive narrative tension through the risk of loss.
Solution: Pair the player with an NPC who accompanies them through significant game time. Develop the relationship mechanically (shared combat, cooperative puzzles) and narratively (shared dialogue, vulnerability, conflict). The bond is a system; the attachment is an output of that system.
Examples: The Last of Us (Joel and Ellie — the modern reference case). ICO (Ico and Yorda, one of the earliest). BioShock Infinite (Booker and Elizabeth). Brothers: A Tale of Two Sons (both playable, inverted pattern). Shadow of the Colossus (the horse, Agro). It Takes Two (cooperative, player-to-player variant).
When to Use: Narrative-driven games, emotional-arc games, games where the player should care about someone besides themselves.
When NOT to Use: Games where the companion becomes a leash on player agency. Games with such non-linear structure that a consistent companion is impractical.
Related Patterns: Branching Dialogue, Asymmetric Roles, Environmental Storytelling.
Chapter Reference: Chapter 15 (Emotion and Empathy), Chapter 21 (Dialogue and Characters).
29. Unreliable Narrator
Also Known As: Player-deception, twist perspective.
Problem: Create narrative surprise, force the player to reassess what they think they know, or deliver a thematic punch that relies on revelation.
Solution: Present the story from a perspective that is, in some way, lying. The narrator might be wrong, biased, mentally compromised, or outright deceptive. A twist reveals the gap between presented and actual reality.
Examples: BioShock ("would you kindly"). Silent Hill 2 (the entire game, in retrospect). Spec Ops: The Line (the player is the monster). Hades (Zagreus learns his history has been edited). The Stanley Parable (narrator as antagonist). Undertale (awareness of prior playthroughs).
When to Use: Narrative games with a clear arc that benefits from reassessment. Games where theme is more important than plot.
When NOT to Use: Games where players will replay many times — the trick only works once. Games where the twist would feel cheap rather than earned. Abuse of this pattern is why a lot of Metacritic 7/10 indie games get dismissed.
Related Patterns: Environmental Storytelling, Branching Dialogue, New Game+.
Chapter Reference: Chapter 20 (Narrative in Games), Chapter 22 (Environmental Storytelling).
ECONOMY PATTERNS
30. Soft Currency / Hard Currency
Also Known As: Dual-currency system, earnable vs. premium.
Problem: Distinguish between currency earned through play and currency purchased with real money (or reserved for important content). Prevent the earned economy from trivializing the premium economy.
Solution: Two currencies. Soft currency is abundant, earned by playing. Hard currency is scarce, purchased or earned slowly. Most content is priced in soft; premium or time-saving content is priced in hard. Conversion rates (if any) are deliberate and controlled.
Examples: Clash of Clans (gold vs. gems). Genshin Impact (mora vs. primogems). Fortnite (V-bucks). Hearthstone (gold vs. dust vs. real money). Destiny 2 (glimmer vs. bright dust vs. silver).
When to Use: Free-to-play games with monetization. Games with a distinction between casual and committed content.
When NOT to Use: Premium single-player games with no monetization. Overly complex dual-currency systems confuse players. Also ethically fraught when conversion rates obscure real costs (Chapter 33).
Related Patterns: Sink/Source, Faucet and Drain, FOMO.
Chapter Reference: Chapter 24 (Game Economy Design), Chapter 33 (Game Design Ethics).
31. Sink / Source
Also Known As: Inflow/outflow, economy flow diagram.
Problem: An economy needs balance. Too many sources (ways to earn) with too few sinks (ways to spend) causes inflation — the currency becomes worthless. Too many sinks with too few sources causes deflation — players cannot afford anything and disengage.
Solution: Map every way currency enters the system (sources) and every way it leaves (sinks). Balance the aggregate rates. Design a healthy flow where currency circulates rather than accumulating.
Examples: World of Warcraft (repair costs, travel costs, auction-house cuts — all sinks against quest-reward sources). EVE Online (ship destruction as the ultimate sink). Path of Exile (crafting materials as sinks). Stardew Valley (building and tool upgrades as sinks).
When to Use: Any game with persistent currency. This is not optional — untended, every persistent economy drifts into dysfunction.
When NOT to Use: Single-session games where persistent economies do not exist. Pay-once premium games where player purchasing of in-game content is the only source.
Related Patterns: Soft Currency / Hard Currency, Faucet and Drain, Resource Management.
Chapter Reference: Chapter 24 (Game Economy Design), Chapter 32 (Game Balancing).
32. Faucet and Drain
Also Known As: Tap and sink, economy pump.
Problem: Related to sink/source but focused on flow rate and pacing. Currency that arrives too fast feels meaningless; that arrives too slow feels punishing.
Solution: Treat each source (faucet) and each sink (drain) not just as presence/absence but as a rate. Tune rates so that the player's cash balance sits in a target range — enough to afford meaningful purchases, not enough to buy everything. Inject temporary accelerators (double-coin events) or slowdowns (expensive new item tiers) to reset the balance.
Examples: Path of Exile (currency drops calibrated to map clear speed). Warframe (Platinum trade rates). Runescape (gold piece inflation managed over 20 years). Stardew Valley (season transitions pace the economy).
When to Use: Live-service games. Games with persistent economies where rate-of-flow matters across dozens of hours.
When NOT to Use: Short-form or single-session games.
Related Patterns: Sink/Source, Power Creep, XP Curve.
Chapter Reference: Chapter 24 (Game Economy Design), Chapter 32 (Game Balancing).
TECHNICAL / FEEDBACK PATTERNS
33. Screen Shake (Juice)
Also Known As: Camera shake, impact feedback, game feel.
Problem: Moments of impact — a hit landing, an explosion, a punch received — need to feel weighty. Pixels alone cannot convey weight.
Solution: Briefly displace the camera in response to impacts. Small shakes for small hits; large shakes for large hits. Tune the duration, amplitude, and falloff. Good shake is felt without being consciously noticed; bad shake is nauseating.
Examples: Nuclear Throne (textbook juice, aggressive shake that shaped a generation of indie games). Vlambeer games in general (Nuclear Throne, Luftrausers — Vlambeer's "The Art of Screenshake" GDC talk is mandatory watching). Dead Cells (precise impact shake). Celeste (subtle but present). Hotline Miami (violent shake matching violent theme).
When to Use: Action games, combat games, anywhere impact is a selling point.
When NOT to Use: Accessibility concerns — some players experience motion sickness from camera shake. Always provide an off-toggle. Also wrong for calm / zen games where shake would break the mood.
Related Patterns: Hit Pause, Coyote Time, Variable Ratio Reward.
Chapter Reference: Chapter 8 (Feedback Systems), Chapter 29 (UI and UX).
34. Hit Pause (Hit Stop)
Also Known As: Hit freeze, impact freeze frame.
Problem: Make hits feel like they land. A hit without weight is a hit without satisfaction.
Solution: Briefly (30–80 ms, sometimes longer) freeze all motion on impact. The player and enemy both freeze at the moment of contact. When motion resumes, the sense of impact is dramatically amplified. Commonly paired with screen shake and a brief flash.
Examples: Super Smash Bros. (hit-stop scales with damage; feels like physics). Devil May Cry 5 (every sword strike). Hades (every melee landing). Celeste (dash-into-enemy freeze). Hyper Light Drifter (impact pauses are part of the game feel).
When to Use: Every action combat game. Platformers with combat. Fighting games. This pattern, combined with screen shake, transforms the feel of striking mechanics.
When NOT to Use: High-flow games where any pause would break momentum (rhythm games, racing games). Cannot be overused — constant hit-pause creates choppy feel.
Related Patterns: Screen Shake, Coyote Time.
Chapter Reference: Chapter 8 (Feedback Systems), Chapter 26 (Combat Design).
35. Coyote Time
Also Known As: Late jump, edge forgiveness, jump grace period.
Problem: Players intend to jump at the edge of a platform; their input arrives a few frames after the character has walked off. From the player's perspective, the jump should happen. From the engine's perspective, the character is no longer grounded and cannot jump.
Solution: After the character leaves a grounded surface, allow "jump" input to register as if they were still grounded for a short window — typically 3 to 8 frames (50–140 ms). The player experiences the jump as intended; they never learn the platform was the issue.
Examples: Celeste (about 6 frames, tuned to feel generous without feeling cheaty). Super Meat Boy (introduced the pattern to wide awareness). Ori and the Blind Forest. Hollow Knight. Basically every modern 2D platformer uses this. The term "coyote time" comes from Wile E. Coyote running off cliffs.
When to Use: Every platformer. Every 3D action game with jumping. This is invisible quality — players never consciously notice, but they notice when it is absent.
When NOT to Use: Precision-puzzle platformers where pixel-exact inputs are the point (rare; even these usually use coyote time). Games where edge-leaving is part of a skill expression.
Related Patterns: Input Buffer (a related pattern for forgiving early inputs), Hit Pause.
Chapter Reference: Chapter 5 (Game Mechanics), Chapter 8 (Feedback Systems).
Using This Catalog
Thirty-five patterns is not the full set. It is the set that shows up most often in the kinds of games this book is about — small and mid-scale indie action-adventures, puzzle games, platformers, roguelikes, narrative games. There are patterns from AAA production, mobile F2P, board games, esports, and VR that could fill another catalog this size. When you hit a problem this catalog does not name, look for it in Adams, Schell, Koster, the GDC vault, or the Game Programming Patterns book — the pattern community is active, and the shared vocabulary is useful across the whole discipline.
Three habits that make the catalog useful:
First, name the pattern when you see it. When you play a game and notice a moment that works — say, a perfectly timed hit pause in Hades — name it. "That's the hit-pause pattern doing its job." Naming patterns in other people's games sharpens your eye for your own.
Second, when you are stuck on a design problem, browse the catalog. Your brain will hook onto names that relate to the problem at hand. "I need more replayability — Deck Building? New Game+? Skill Tree? Variable Ratio Reward?" Patterns are prompts.
Third, when you combine patterns, know what you are combining. A game with Variable Ratio Reward + Streak + FOMO + Soft/Hard Currency is a free-to-play mobile game using four engagement patterns in stacked configuration. The stack is a design choice, and an ethical choice (Chapter 33). A game with Coyote Time + Hit Pause + Screen Shake is a game investing in game feel. Both stacks produce specific, recognizable experiences. Naming what you are using makes it clearer what you are building.
You will outgrow this catalog. Good — that means your own vocabulary is growing. Write your own patterns. The patterns you coin from your own work, in your own words, will be more useful to you than any list I could give you.
Make the list. Use the list. Throw the list away when it stops serving.