I was watching the cat this morning. Not doing anything remarkable—just sitting on the windowsill, watching a bird on the lawn. The bird hopped closer. The cat's tail twitched. The bird hopped again. The cat's ears rotated forward, tracking the sound. The bird took one more hop. The cat's hind legs tensed, weight shifting backward—not yet springing, but ready.
The cat didn't need a tutorial. No on-screen prompt told it that birds are prey, that movement attracts attention, that a crouch precedes a pounce. It learned all of that through observation, pattern recognition, and the quiet logic of cause and effect.
Games do the same thing—or at least, the best ones do. They teach you rules without explaining them. Not through tutorials, not through tooltips, not through NPCs shouting instructions. Through design.
I. The Sensation
You've felt it. You're playing a game for the first time. You don't know the controls. You don't know the mechanics. And yet—somehow—you know what to do.
In The Legend of Zelda: Breath of the Wild, you leave the Shrine of Resurrection and step onto the Great Plateau. The game doesn't tell you that you can climb anything. It doesn't tell you that you can chop down trees. It doesn't tell you that cooking ingredients together produces food. It shows you a tree, shows you an axe, and trusts you to connect the dots.
In Elden Ring, you walk into Limgrave and see a giant walking in the distance—the Tree Sentinel. The game doesn't tell you not to fight it. It doesn't tell you that it's a miniboss meant to teach you that not every enemy is meant to be fought immediately. It simply places a majestic, mounted knight in your path, gives you a weapon, and lets you discover the consequences of your choices.
In Super Mario Bros., you approach the first goomba. You don't know that you can stomp on it. But the game has trained you—through coin blocks, question marks, and the simple logic of jumping on platforms—to understand that jumping is your primary interaction. You jump. The goomba flattens. You learn.
This is not tutorialization in the traditional sense. It is teaching by doing—or rather, teaching by letting you try.
II. The Suspected Machinery
This kind of teaching—invisible, implicit, experiential—is built on a handful of design principles.
1. Affordance
An affordance is a property of an object that suggests how it can be used. A door handle affords pulling. A button affords pressing. A tall wall in a game with a jump button affords climbing.
Good game design creates strong affordances. In Breath of the Wild, everything—every cliff, every tree, every rock—affords interaction. The visual language is consistent enough that when you see a sparkly mineral deposit, you immediately reach for a weapon to break it open.
But affordances are culturally learned. A player who has never played a game before might not know that a sparkly deposit means "break me open." So the game reinforces the affordance through repetition and feedback: you break one deposit, it gives you loot, you break another, it gives you more loot. The connection becomes automatic.
2. The Golden Path
Games are often designed with a golden path—an intended sequence of actions that teaches the player the mechanics gradually. The path isn't always a literal corridor; it can be a spatial arrangement, a sequence of challenges, or a carefully curated set of encounters.
In Super Mario Bros., the first level is a masterpiece of implicit teaching:
Coin blocks teach you that hitting things from below produces rewards.
Goombas teach you that stomping on enemies kills them.
The first pit teaches you that falling is death.
The first ? block teaches you that some blocks are special, and that you should hit all of them.
The flagpole teaches you that reaching the end is the goal.
These lessons are layered, sequential, and never explained. You learn each one through a combination of curiosity, trial, and error. The game trusts you to figure it out.
3. Feedback Loops and Signal-to-Noise
Implicit teaching relies heavily on feedback loops:
Positive feedback signals success. In Dark Souls, an enemy dissolving into souls is a dopamine trigger—you did the right thing.
Negative feedback signals failure. In the same game, the "YOU DIED" screen is unambiguous—you did the wrong thing.
But it's not just binary success/failure. The quality of feedback matters. A hit that feels heavy—with screen shake, audio crunch, and enemy flinch—tells you that you're making progress. A miss that feels empty—with a whiff animation and no hitbox response—tells you that you're doing something wrong.
The best implicit teaching uses feedback to guide the player toward the desired behavior. In Elden Ring, the Tree Sentinel's attacks are massive, sweeping, and devastating. The feedback is visceral: you try to fight it at level one, you get one-shot, you learn that some enemies are not meant to be fought immediately.
4. Mechanical Scaffolding
Games often introduce complex mechanics by scaffolding—starting with simple versions and gradually increasing complexity.
Hades is a masterclass in this. The game gives you a simple weapon (the sword) with a simple moveset (attack, special, dash) in your first run. You learn the basics of combat, then you die. On your second run, you unlock a new weapon (the bow), which teaches you about range and positioning. On your third run, you encounter a new enemy type that forces you to use your dash differently. The mechanical lessons build on top of each other—each run introduces new layers while reinforcing the old.
You never read about these systems. You experience them.
III. Field Test
I tested this by observing a new player—someone who had never played Elden Ring—go through the first hour of the game. I recorded what they learned through implicit teaching vs. what they needed to look up.
Lesson | Implicitly Taught? | How? |
|---|---|---|
Enemies can be locked on | Yes | The targeting reticle appears when you face an enemy; button prompt appears eventually |
You can parry | No | Not introduced through natural gameplay; requires experimentation or external knowledge |
You can't fight the Tree Sentinel yet | Yes | One-shot death; immediate feedback |
Bonfires heal you and respawn enemies | Yes | Using one demonstrates the effect |
You can upgrade weapons | No | Requires exploration and NPC interaction; not explicitly signaled |
You can craft items | Yes | Crafting menu is available; resources are plentiful enough that discovery feels natural |
The game is hard | Yes | You die. A lot. |
The pattern is clear: Elden Ring teaches you about the world through the world—but it doesn't teach you how to play. The implicit teaching is strong for the "what" (this is dangerous, this is safe, this is important) but weak for the "how" (press this button, use this mechanic).
This is intentional. Elden Ring is designed to be opaque. But it's a good illustration of what implicit teaching can do and where it needs to be supplemented.
IV. Competing Explanations
Is implicit teaching always better than explicit tutorials?
Explanation A: No. Some players—especially new players, or players unfamiliar with the genre—need explicit instructions. Not everyone has played Super Mario Bros. Not everyone understands what an affordance is. For accessibility reasons, some form of explicit teaching is necessary.
Explanation B: Implicit teaching can be misleading. If a game teaches you a rule implicitly and that rule turns out to be situational—or wrong—the player will feel cheated. Breath of the Wild teaches you that you can climb almost anything; then, in the final boss fight, you can't climb certain walls. The game breaks its own implicit rule.
Explanation C: Implicit teaching is culturally specific. A player who grew up on Japanese game design might recognize certain patterns (sparkly things are important, red barrels explode, chests contain loot) that a player from a different gaming background might not. The "universal" language of games is not actually universal.
Explanation D: The best games do both. Portal is often cited as a masterpiece of implicit teaching—but it also has explicit messages. "The companion cube cannot speak." "We do not recommend you eat the cake." The game uses implicit teaching for mechanics and explicit teaching for tone. Both are valid tools.
V. Conclusion
Games teach us rules without explaining them. They always have. Super Mario Bros. taught us that goombas can be stomped. Breath of the Wild taught us that the world is ours to explore. Elden Ring taught us that death is a teacher, not a punishment.
The best games treat their players as intelligent, curious, and capable of pattern recognition. They don't hold our hands. They trust us to figure it out—through careful placement, consistent feedback, and the quiet logic of cause and effect.
That trust is a form of respect. It says: "You are smart enough to learn this. You don't need a tutorial. You just need to pay attention."
And when we do—when that click happens, when the pattern reveals itself, when we see the golden path for the first time—it feels like discovering a secret. Not a secret the game is hiding from us. A secret it was waiting for us to find.
No entries yet — sign the first.