Game Design
Teaching Through Design
**In Mega Man every boss teaches you before you meet them.** Enemies on the level use the boss's attacks in simplified form. By the time you reach the boss - you already know the patterns. Without a single 'Press X to dodge'. This is teaching through design.
The best tutorial is the one the player doesn't notice. When the player thinks 'Wow, I figured it out myself!' - the designer actually guided them by hand through invisible learning. This is the art of teaching without teaching.
Цели урока
- Understand 'Show, Don't Tell' in game design
- Study safe spaces for experimentation
- See constraint introduction patterns
- Break down Mario 1-1 as tutorial perfection
- Apply invisible teaching to any genre
Предварительные знания
- Level Design Fundamentals: space as a teaching tool
Teaching through design is communication without language. Works in any language, any culture, any age. This is pure design language. Understanding it = understanding how people intuitively learn.
- **UX/UI**: Onboarding through progressive disclosure
- **Education**: Scaffolding - support while the student learns
- **Architecture**: Wayfinding through space design
- **Sports**: Drills isolate skills before game situations
Nintendo's Design Philosophy
Miyamoto's philosophy: 'If you need to explain it in words - it's bad design'. Super Mario Bros. sold 40+ million copies - most buyers had never played a video game before. They learned without manuals, tutorials, or the internet. Pure design communication.
Show, Don't Tell
**Problem with text:** Breaks immersion, not everyone reads, different languages, doesn't prove understanding.
**Power of showing:** Player discovers → feels smart → remembers better → actually understands (not just memorizes).
Safe Spaces
Safe space - an environment where failure is not punishing, allowing free experimentation:
**First enemy easy:** Classic pattern. First Goomba in Mario walks toward you slowly. Can't miss. Teaches jumping = kills enemies.
Constraint Introduction
Constraint introduction - when level design forces the player to use a mechanic:
**Gate = forced learning.** If you must jump to continue, you will learn to jump. Simple but effective. Most tutorials use this.
**Reward = optional learning.** A visible reward encourages but doesn't force. Respects player choice.
Mario 1-1: Tutorial Masterpiece
World 1-1 of Super Mario Bros. - possibly the best tutorial in history. Every element is designed for teaching:
**Zero words.** 1985, millions of people who had never played a video game - and they learned in 30 seconds. Design > documentation.
Teaching Without Telling
What is the fundamental insight about Teaching Without Telling?
Portal's Teaching
Show mechanics through environment
**Teaching portals (Chamber 00-01):** - First room: See yourself through portal - Second room: Walk through portal to exit - No text explaining 'portals connect two points' **Teaching momentum (Chamber 10):** - High platform, pit below, portal at bottom - Player MUST figure out: fall → build speed → launch - Iconic 'Speedy thing goes in, speedy thing comes out' is AFTER player already did it **Lesson:** Show first, explain (if needed) after. Never the reverse.
Player needs to learn that fire damage is dangerous. Best way?
Player sees fire hurting something else - learns without risk. Then encounters fire themselves, already knowing. Forced damage is frustrating, text breaks immersion, NPC is telling not showing.
Celeste's Teaching Rooms
Safe spaces in a hard game
**Celeste approach:** - Each chapter starts with a 'teaching room' - New mechanic introduced with a simple setup - No death penalty (instant respawn) - Can't leave until understood **Example - Dash Crystals:** 1. Room with crystal, gap too wide for jump 2. Must touch crystal → learn it refills dash 3. Now dash over gap 4. Next room: crystal + spike timing 5. Then: crystal chains **Lesson:** Even brutally hard games have safe learning moments.
Zelda Dungeon Items
Constraint through item design
**Pattern in every Zelda dungeon:** 1. Get new item (bow, boomerang, hookshot) 2. Immediate puzzle using the item 3. Enemies weak to the item 4. Boss requires item to defeat **Design brilliance:** - Can't leave without mastering the item - Progression gated by item skill - Boss = 'final exam' on the item - Item becomes part of toolkit forever **Lesson:** Item received → must use → mastered → never forgotten.
You added a new mechanic - wall run. How do you guarantee the player masters it?
Gate constraint guarantees learning. Player won't progress without mastering the mechanic. A popup can be skipped/forgotten, optional discovery may be missed, an achievement doesn't teach.
Mushroom Design Genius
Teaching through environment
**Problem:** Mushroom = power-up. But in reality mushrooms are often poisonous. How do you show it's good? **Solution:** - Mushroom spawns from a block (connection to rewards) - Moves AWAY from the player first - Bounces off a pipe - Moves BACK toward the player - Block arrangement makes avoiding it difficult **Result:** Player 'accidentally' touches the mushroom, grows, understands 'good'. **Lesson:** If something is good - make it hard to avoid. If bad - make it avoidable but learnable.
Упражнения
- Why is the first enemy in most games very weak? — Safe space for learning combat. Player can experiment, make mistakes, understand mechanics. Low risk means they can focus on learning, not survival. First Goomba, first slime in an RPG - all the same: teaching without punishment.
- A puzzle game introduces a teleportation mechanic. Design the first 3 puzzles. — Puzzle 1: Two platforms, teleporter between. Just walk in, appear on the other side. Teaches basic function. Puzzle 2: Goal behind a wall, teleporter lets you through. Teaches: teleport goes through walls. Puzzle 3: Moving platform, timed teleport. Teaches: can use mid-action. Isolation → application → combination.
- How do you teach a complex combo system (fighting game) without text tutorials? — 1) Single-player training mode where AI visually shows combos. 2) 'Shadow' opponent performs combo on you, then you repeat. 3) Ghost hands show inputs. 4) Slow-motion replay of successful combo. 5) Rhythm-game style timing windows visible. 6) Each mission/challenge isolates one combo, gates progress. Combination: show → repeat → practice → test. Difficulty escalates.
Teaching Design in Context
How teaching through design connects to other concepts:
- Difficulty Curves — Teaching = early difficulty curve
- Flow State — Good teaching maintains flow
- Pacing — Teaching needs pacing (not everything at once)
- Level Design Fundamentals — Space is the teacher
Итоги
- **Show, Don't Tell:** Demonstration > explanation
- **Safe Spaces:** Low-risk environments for learning
- **Constraint:** Force mechanic use through level design
- **Mario 1-1:** Zero words, teaches everything
- **Player feels smart:** Best teaching is invisible teaching
Вопросы для размышления
- Recall a game where the tutorial was frustrating or boring. What specifically was bad? How could the same thing have been taught through design?