Chapter 16: Level Design Fundamentals — Space as a Design Language

There is a pillar in Super Mario World's first level. It is not described in any tutorial. There is no sign next to it. The game has not, by the time you encounter it, used a single word of text. And yet, when you reach it, you understand without thinking that you can either jump over it, walk past it on the ground, or — if you experiment — discover that the pipe nearby leads underground to a coin room. You read the space and act.

You did not learn to read the space from the manual. You learned it from the space itself. The pillar's height is exactly the height Mario can jump and clear comfortably. The pipe is colored differently from the surrounding terrain. The coins floating above guide your eye toward the next jump. The cliff edge ahead is far enough away that you have time to react but close enough that you must keep moving.

Every one of those decisions is the result of a deliberate choice by Shigeru Miyamoto and his team. Every pixel placement is intentional. The level is not a stage on which the game happens. The level is the game. Mario's mechanics — run, jump, stomp — are meaningless without the spatial choices that put a Goomba exactly here, a coin exactly there, a pipe at exactly that angle. The mechanics tell you what is possible. The level tells you what to do.

This is what level designers know that other designers sometimes do not: space is a language. Players read it constantly, fluently, and largely without conscious awareness. A wide-open room communicates safety. A narrow corridor communicates threat. A door that resists communicates "come back." A ledge just barely out of reach communicates "find another way." These are not arbitrary signals you teach the player. They are deeply embedded human spatial intuitions, refined across millions of years of navigating physical environments, that your level taps into the moment the player draws a breath.

This chapter teaches you that language. By the end, you will be able to look at a room — any room, in any game — and read the design intent. You will see the choke points and the sightlines and the leading lines and the bait. You will know why the lighting in this corner draws your eye and not that one. You will recognize the Nintendo school of pacing without anyone needing to name it for you. You will paper-prototype three levels for your project, with pacing charts, and you will understand why graph paper and a pencil are still the most powerful level design tools ever invented.

You will also start to see, for the first time, what your mechanics look like when they live in space rather than in a test room. This is where many designers discover that their carefully tuned systems do not work the way they thought. That is the point. Level design is the stress test for everything you have built — and the moment your game stops being a prototype and starts being a place.

16.1 What a Level Actually Is

Ask a hundred game designers what a level is and you will get a hundred answers, most of them too narrow. A level is not a map. It is not a setting. It is not the stuff between cutscenes. A level is the spatial arrangement of a designed experience — every object the player can see, every path they can take, every challenge they will encounter, every reward they might find, organized in space and sequenced through movement.

The most useful definition I have ever heard came from a senior designer at a now-defunct studio: "A level is a question the space asks the player, and the player's movement is the answer." Every level you design is asking the player something. Can you get past this? Can you find this? Will you risk this? Did you notice that? The player's path through the space is them answering. Good levels ask questions worth asking. Great levels ask questions the player did not know they were being asked, then surprise them with the answer they gave.

This framing matters because it forces you to think about levels as interactions rather than containers. A bad level designer says, "I need a forest section, a cave section, and a boss arena." A good level designer asks, "What does the player learn in this space? What do they do that they have not done before? What feeling do they leave with?" The difference is the difference between decorating a hallway and conducting an orchestra.

💡 Intuition: Try this. Pick any screenshot from any game and ask: what is the player about to do? You can usually tell within a second or two. The corridor narrows — combat is coming. The ceiling opens up — there is something to look up at. The path branches — a choice is being offered. You are reading the level designer's intent without conscious effort. Your players will read your levels the same way. The question is whether what they read matches what you meant.

A level operates on at least four registers simultaneously, and the great designers think about all four at once.

The mechanical register is the most obvious. What does the player do here? Jump? Fight? Solve a puzzle? Sneak? The level must afford the actions the mechanics make possible, and it must do so legibly — the player must be able to see, in the space, what kind of room they are in. A combat arena and a stealth corridor look different not because of art direction but because of layout: the arena is round and open, the stealth corridor is long and dark and full of cover.

The narrative register is the story the space tells without dialogue. A toppled chair in an otherwise empty room implies a struggle. Bullet holes in a wall imply a fight. A child's drawing on a refrigerator implies a family. A skeleton at the end of a dead-end tunnel implies that someone tried this before you and failed. None of these need text to be read. The space narrates.

The emotional register is the feeling the space evokes. A vast open vista evokes awe. A cramped corridor with a low ceiling evokes claustrophobia. A long approach to a distant landmark evokes anticipation. A descending staircase into darkness evokes dread. These emotions are produced by the spatial composition itself, often before the player consciously processes what they are seeing.

The pedagogical register is what the level teaches. Good levels are lessons. The first time you encounter a new mechanic, the level is teaching you what it is. The second time, the level is testing whether you learned. The third time, the level is twisting your expectation by combining the mechanic with something else. Every spatial choice can be interrogated through the question: what does this teach the player? If the answer is "nothing," you have decoration, not design.

Most designers start by thinking only about the mechanical register. The other three develop with practice and become invisible: the experienced level designer sees a vista and feels its emotional weight without having to name it; sees a corridor and recognizes the lesson it is delivering. The point of this chapter is to make those four registers explicit so you can begin to consciously coordinate them in your own work.

16.2 Spaces as Challenges, Puzzles, Stories, and Emotional Landscapes

A space can be many things to a player, and the most interesting levels are usually multiple things at once. Let us walk through the four primary modes and look at how they overlap.

A challenge space asks: can you do this? It is the combat arena, the platforming sequence, the timed escape. The space is configured so that the player's mechanical skills are tested directly. The Forest of Fallen Giants in Dark Souls II, the cliffside ascents in Celeste, the murderous bullet-hell screens in Hollow Knight's Path of Pain — these are challenge spaces. Their purpose is to push the player's execution to the edge of their ability.

A puzzle space asks: can you figure this out? The space contains an answer the player must discover through observation and experimentation. The shrines of Breath of the Wild are puzzle spaces — each one a small architectural problem with a solution that emerges from playing with the mechanics provided. Portal is almost entirely puzzle spaces. Tunic's map is a puzzle space embedded inside an action-RPG. The space rewards thinking, not reflexes.

A story space asks: do you see what happened here? The space contains the residue of events — past, present, or hypothetical. The Cathedral of the Deep in Dark Souls III, with its layered hierarchy of corrupted clergy. The empty hallways of the Overlook Hotel in any game that has homaged it. The abandoned research stations scattered throughout SOMA. These spaces tell their stories through arrangement — what was placed where, what was destroyed, what was preserved — without needing text or voice.

An emotional landscape asks: how does this make you feel? The space is composed primarily for affective response. The Great Plateau in Breath of the Wild, viewed from atop the Temple of Time, is an emotional landscape — a vast horizon promising freedom. The descent into the Painted World in Dark Souls is an emotional landscape of melancholy. The dance hall in Spec Ops: The Line is an emotional landscape of horror. These spaces exist primarily to produce feeling, even when challenges or puzzles are layered on top.

Real levels usually mix all four. The opening of Half-Life 2 is famous because it is simultaneously a story space (the Combine occupation revealed through environmental detail), an emotional landscape (the oppressive weight of City 17), a puzzle space (the player must figure out where to go), and — eventually — a challenge space (the rooftop chase). Valve's level designers were not building four levels stacked on top of each other. They were building one space that operated on four registers at once. That is the craft.

🎯 Tradeoff Spotlight: Levels that try to do all four registers equally often do none of them well. The strongest levels privilege one register and let the others support it. Ravenholm in Half-Life 2 is primarily an emotional landscape (horror), with challenge and story stacked on as reinforcement. The Spirit Temple in Ocarina of Time is primarily a puzzle space, with story and emotion as accents. Choose your dominant register first. Let the rest harmonize.

When you sit down to design a level, ask yourself which mode is dominant. The decision shapes everything that follows. A challenge space wants visible obstacles and clear goals. A puzzle space wants ambiguity and hidden logic. A story space wants details to discover. An emotional landscape wants composition and silence. The same space cannot serve all four equally — and the attempt to make it do so is one of the most common failure modes of inexperienced level designers.

16.3 Linear, Branching, and Open: Three Structures

The architecture of a level — how the spaces connect — falls roughly into three families, and each carries a different set of design implications.

A linear level has one path from beginning to end. The player moves through a sequence of rooms or sections in a fixed order, with no significant alternative routes. Most Call of Duty levels are linear. Most Uncharted levels are linear. The campaign of Half-Life is essentially linear, with brief branching pockets. Linearity is sometimes treated as a dirty word in level design discourse, which is a mistake. A linear level gives the designer total control over pacing, escalation, and revelation. The designer knows what the player will see, when they will see it, and what state they will be in when they encounter the next event. This control is enormously powerful for designed experiences with strong emotional or narrative arcs.

A branching level offers the player meaningful choices about which paths to take, but the choices are bounded. There might be three routes through a city block, or a fork that leads to either the rooftops or the sewers, or alternative paths that reconverge later. Deus Ex is the canonical branching design — every level has multiple solutions and multiple physical routes, and the player chooses a style (combat, stealth, hacking, social) and pursues it through the available options. Dishonored extends this approach. Branching levels trade some of the designer's control for player expression: the player gets to feel like they are choosing their own way, which produces a different kind of engagement than the linear ride.

An open level has no fixed sequence. The player chooses goals, paths, and order of engagement. Breath of the Wild's overworld is open. Skyrim's map is open. The dungeons of Diablo are technically generated, but the player's traversal of them is open in the sense that the order of engagement with rooms within a level is largely free. Open levels maximize player agency at the cost of designed pacing. The designer cannot guarantee the player will encounter event A before event B, which means individual events must work in any order — and the dramatic arcs of a designed experience must be built into something other than the level structure (often into quest design or main-story scripting).

Most real games mix these structures. Even Breath of the Wild, which presents itself as fully open, has linear sequences inside its shrines and a tightly designed linear sequence on the Great Plateau. Even Call of Duty, which is mostly linear, has occasional branches and hubs. The decision is not "which structure does my game use" but "which structure does this level use, given what I want it to accomplish."

⚡ Quick Reference: When to Use Each Structure

• Linear: Strong emotional arcs, narrative beats, scripted set pieces, tutorials, climactic sequences. When you need the player to see X before Y.
• Branching: Player expression of style, replayability, multiple-solution puzzle/stealth/combat encounters. When the how matters more than the what.
• Open: Exploration-driven games, sandbox emergence, player-set goals. When the player discovering their own path is part of the experience.

A common mistake among new designers is to default to "open" because it sounds cooler and more freedom-respecting. In practice, fully open design is brutally difficult to pace well, requires enormous content density, and often produces players who are bored despite having "infinite choice." A tightly designed linear level can be a transcendent experience. A poorly designed open one is just an empty field. The sophistication of your structure matters less than the sophistication of your decisions within it.

16.4 The Critical Path and Optional Content

Inside any non-linear level, there is usually a critical path — the route the designer expects most players to take to reach the level's primary goal. Around the critical path, there is optional content — secrets, side rooms, collectibles, alternate routes, lore items, hidden bosses. The relationship between these two is one of the most important design tensions in level design.

If the critical path is too obvious, the level feels on-rails even when it isn't. The optional content becomes invisible — players don't notice the side passages because the main path is too clearly marked. If the critical path is not obvious enough, players get lost, miss the main objective, and become frustrated. The designer must signal the critical path clearly enough that no player gets stuck, while still leaving the optional content discoverable enough that players who explore are rewarded.

The standard tools for this are visual hierarchy, lighting, and environmental contrast. The critical path is usually slightly brighter, slightly more visually emphasized, slightly more obviously a "way." Optional content is in the visual periphery — visible if you look, invisible if you don't. The Legend of Zelda: A Link to the Past is a masterclass in this: the main dungeon path is always clearly indicated (often through visible architectural cues like a particularly large door), while side rooms hide behind bombable walls, in corner shadows, or off the obvious route.

The ratio of critical path to optional content is a design parameter. Call of Duty-style levels are nearly 100% critical path. Hollow Knight-style metroidvanias might be 40% critical path and 60% explorable side content. Skyrim dungeons are typically 80% critical path with 20% side rooms. The right ratio depends on your game's identity. Exploration-driven games need lots of optional content; story-driven games can get away with very little.

A useful discipline for managing this balance: when you design a level, mark the critical path on your prototype with a colored line. Then mark each piece of optional content with a smaller note. The visual ratio of "main line" to "side notes" should match the kind of game you are making. If you find yourself drawing a critical path that fills the entire space and crowds out the side notes, your game is more linear than you may have intended. If you find the critical path getting lost in a sea of optional content, your players may get lost too.

There is a special case worth naming: the mandatory-feeling optional. This is content that is technically optional but designed to feel essential — heart pieces in Zelda, mantles in Monster Hunter, codex entries in Mass Effect. The player can skip them, but the game's reward systems make them feel like part of the main experience. This is a powerful tool for extending engagement in optional content without requiring it. The cost is that completionist players will feel obligated; the benefit is that exploration-oriented players will feel rewarded.

16.5 Pacing Through Space: Tension and Release

Levels have rhythm. A well-designed level alternates intensity and quiet, threat and safety, action and contemplation, in a sequence that lets the player breathe and then yanks the breath away. This is pacing, and it is largely produced by the shape of the space itself.

The principle is borrowed from music and from theater: continuous high intensity is not intense. It is exhausting. After about ninety seconds of sustained combat, the brain begins to habituate. The third explosion is less impactful than the first. The fifth jumpscare provokes annoyance, not fear. To preserve intensity, you must release it — return the player to a low-intensity state — so that the next high-intensity moment lands again.

Spaces produce intensity through density and constraint. A narrow space full of enemies is intense. A wide-open space with no visible threats is calm. A dark room with limited information is anxious. A bright room with clear sightlines is reassuring. By varying these qualities sequentially, you produce the intensity curve — a wave shape that rises into combat encounters and falls into safe rooms, crests at boss arenas and troughs at vista views.

The classic pattern, common to Resident Evil, Half-Life, Dark Souls, and many Nintendo games, looks roughly like this:

1. Low intensity: A safe room. The player heals, saves, looks around. Heart rate drops.
2. Building tension: A corridor with no immediate threat but increasing visual hints of danger. Bloodstains on the walls. Distant sounds. The player's awareness sharpens.
3. First contact: A small encounter — one or two enemies, manageable. The player's combat brain engages.
4. Mounting threat: Two or three escalating encounters, each slightly harder than the last. The player begins to feel pressed.
5. Peak: The boss room, the ambush, the set piece. Maximum intensity.
6. Release: A safe room or vista. The player exhales. Heart rate drops.
7. Quiet space: Often a moment for environmental storytelling, reward collection, or a beautiful view. The player processes what just happened.
8. Return to building tension: The cycle repeats.

This pattern is so consistent across decades of games that you can identify it almost immediately in any well-paced level. Dark Souls' bonfires are explicit pacing devices — they are the safe rooms, marked unmistakably as the trough between intensity peaks. Half-Life 2's vista moments (the bridge, the canals, the highway) are explicit release valves between combat sequences. Hollow Knight's benches are the same device — quiet space, healing, save, optional purchase — placed at calculated intervals along the path through difficult content.

⚠️ Common Pitfall: New designers often build levels with monotonic intensity — every room is a fight, or every room is empty. Both produce the same problem: the player habituates, and nothing feels like anything. The fix is not to remove combat or to add it, but to vary. Build a pacing chart before you build the level. Mark each section's intended intensity on a vertical axis. Look at the resulting curve. If it is flat, your level is flat.

The pacing chart is the single most useful tool in level design and will be the central artifact of your project work for this chapter. You will draw a horizontal line representing the player's progress through the level and a vertical axis representing intensity (loosely defined: combat density, threat, time pressure, emotional weight). You will plot the level's intended emotional arc as a wave. Then you will design the spaces to produce the wave.

16.6 Sight Lines and Wayfinding: How Players Know Where to Go

The most invisible work in level design is making sure the player knows where to go without ever being told. The player who is never lost feels confident. The player who is never on rails feels free. Reconciling those two is wayfinding — the art of leading without leashing.

The primary tool of wayfinding is the sightline. A sightline is a line of vision the level affords the player from any given vantage point. What can the player see from where they are standing? What is in the foreground, the midground, the background? What is illuminated and what is in shadow? What stands out by contrast and what blends in? The sightline is the channel through which all spatial communication flows.

A well-composed sightline directs the player toward the next destination by making it visually dominant. The destination might be lit more brightly than its surroundings. It might be the only colored object in a desaturated environment. It might be framed by leading lines — corridor walls, tree branches, architectural features — that point toward it. It might be elevated, so the eye naturally rises to it. It might be in motion, so the eye is drawn to the change. The level designer composes these signals so that the player's eye is repeatedly captured by the next thing the designer wants them to notice.

Mirror's Edge is the textbook case. The game is built around running through urban environments along precise, designed routes, but the routes are not marked with arrows or waypoints. They are marked by color — specific objects (pipes, doors, ledges) are painted red against an otherwise white-and-cool environment. The player learns within minutes that red means "go here," and from then on the routes are legible without HUD elements. The art direction is the wayfinding.

Half-Life 2 uses lighting. Almost every key destination in the game is lit more brightly than the surrounding space. Doorways glow. Important objects pool with light. The player's eye is constantly being pulled toward illumination, and the illumination is placed by level designers who know that this is how attention works.

The Last of Us uses a yellow paint marker for climbable ledges and yellow tape for crucial objects. Naughty Dog knew that the eye in a desaturated post-apocalyptic environment would lock onto yellow instinctively, and they used that fact to mark every interactive surface without ever explaining the convention to the player.

Dark Souls uses the absence of these techniques to disorienting effect. Many areas have no clear visual hierarchy — every direction looks equally promising or equally hostile. The player must explore, get lost, and rebuild a mental map. This is a design choice. Dark Souls wants you lost. Most games do not. Know which you are designing.

Pause your reading for a moment and recall the last time you were lost in a video game. Why were you lost? What was the level not telling you? Was there no clear visual hierarchy? Was the lighting flat? Were there too many equally promising paths? Was the destination not visible from your position? Now recall the last time you felt perfectly oriented in a game world. What was the level doing to keep you oriented? Could you trace the techniques? Holding both experiences side by side is how you begin to notice the machinery.

The negative version of wayfinding is also useful. Sometimes you want the player to hesitate, to feel uncertain, to choose. In those moments, you deliberately balance the sightlines so that no single destination dominates. You offer two equally lit paths. You make both feel like the way. The choice produces engagement — the player must commit, and committing means caring. But this technique should be used sparingly. Most of the time, players need to know where to go. Hesitation feels like uncertainty for a beat; sustained uncertainty feels like being lost.

16.7 Leading the Eye: Composition From Film and Photography

The techniques of cinematography and photographic composition transfer directly to level design. The level designer is, in a meaningful sense, a director — composing shots that will be assembled by the player's movement into a sequence of frames.

Leading lines are the most basic tool. Any line in the visual field — the edge of a wall, the curve of a railing, a row of trees, a cracked floor tile, a beam of light — pulls the eye along its length. Used deliberately, leading lines direct the player's attention toward whatever the designer wants them to notice. A corridor with parallel walls pulls the eye to the vanishing point. A staircase pulls the eye upward. A set of arrows painted on a wall (or a more elegant equivalent) pulls the eye toward what the arrows point at.

Framing is the use of foreground elements to surround the focal point. A doorway in the middle of the screen frames whatever lies beyond it. A tree branch in the foreground frames the vista visible past it. The frame elevates the framed — the player understands that what is enclosed is meant to be seen. Breath of the Wild uses this technique for its iconic vista shots: the player emerges from a cave or rounds a hilltop and finds Hyrule Castle framed by terrain and foliage, an explicit visual proclamation that this is the destination.

Rule of thirds governs how compositional weight distributes across a frame. A focal point placed at the intersection of vertical and horizontal thirds (rather than dead center) feels more compositionally interesting and draws the eye more efficiently. Level designers use this when placing landmarks, vistas, and key encounters: the boss arena's centerpiece is rarely centered in the room — it is placed off to one side at a third-line, so that the player approaches with the focal point already compositionally weighted.

Contrast of all kinds — light vs. dark, warm vs. cool, saturated vs. desaturated, large vs. small, simple vs. complex — pulls the eye to the contrasting element. A single warm light in a cool environment becomes a beacon. A single tall structure in a flat landscape becomes a destination. A single moving figure in a still scene becomes the focus. The level designer choreographs contrast to control where attention lands.

Depth cues create the illusion of three-dimensional space even on a 2D screen. Foreground, midground, background are layered, with elements in each layer at different scales and clarity levels. Atmospheric perspective (distant things become hazier and bluer) reinforces depth. Parallax scrolling — closer layers moving faster than farther ones — does the same for 2D games. Depth is what makes a space feel like a place rather than a stage backdrop. Without depth cues, even beautiful environments feel flat and uninhabited.

📐 Project Checkpoint: When you paper-prototype your three levels, sketch each level's "iconic shot" — the moment the player emerges into a space and sees the composition. What is in the foreground? What is in the midground? Where is the focal point? Which leading lines pull the eye? Which contrasts emphasize what? You should be able to draw three thumbnail compositions per level, one for each major spatial reveal. If you cannot, your level is not yet composed — it is just laid out.

These techniques are not film references applied artificially to games. They are perceptual principles about how human visual attention works, and they apply in any visual medium. The level designer who understands cinematography composes spaces that direct the player's experience without constraining it. The player feels free; the designer is in complete control of what the player sees and when.

16.8 The Nintendo School: Introduce, Test, Twist, Master

There is a pattern of teaching through level design that has come to be called the "Nintendo school," and it is the most influential pedagogical structure in game design. It emerged from Shigeru Miyamoto's philosophy at Nintendo — most explicitly visible in the Super Mario and Legend of Zelda franchises — but it has been adopted, often unconsciously, by virtually every well-crafted game since.

The pattern has four phases:

1. Introduce: The player encounters a new mechanic, enemy, or obstacle in a safe context. The game gives them space to figure out what it is and how it works. There is no penalty for failure. Often the introduction is in isolation — only the new element is present, nothing else competing for attention.

2. Test: The player encounters the same element in a slightly more demanding context. Now there is consequence. The element appears alongside others the player already knows, requiring them to apply the new knowledge under mild pressure.

3. Twist: The element appears in a configuration the player has not seen — combined with another element, used in an unexpected way, or modified. The player must recognize the familiar piece in an unfamiliar arrangement and apply their understanding flexibly.

4. Master: The element is used as a building block in a complex challenge. The player has fully internalized the mechanic and now uses it as a tool, no longer thinking about it as a "new thing." It has joined their toolkit.

This pattern repeats for every mechanic the game introduces. Super Mario World introduces Yoshi in a benign context (you find him in a block, ride him for a while, learn that he eats berries and enemies). It tests Yoshi (you encounter pits where Yoshi's extra jump becomes useful). It twists Yoshi (you encounter level segments where Yoshi must be sacrificed to clear a jump, where you find different-colored Yoshis with different abilities, where Yoshi can fly with certain enemies in his mouth). And it masters Yoshi (late-game levels assume Yoshi is part of your toolkit and design challenges that depend on his abilities).

The whole game is a sequence of these four-phase loops, layered and overlapping. By the time you reach the final levels, you are operating with a vocabulary of internalized mechanics that the game introduced one at a time, tested deliberately, twisted creatively, and integrated into your reflexes.

🚪 Threshold Concept: A level is a lesson. Every well-designed level has a pedagogical structure, even if the player never notices the teaching. The introduce-test-twist-master pattern is the most robust pedagogical framework available to game designers, and recognizing it in great games is the first step toward using it in your own work. When you find yourself unable to articulate what your level teaches, the level probably teaches nothing — and the player will feel that, even if they cannot say why.

The reverse — teaching through frustration rather than scaffolding — is what most amateur games do. They introduce a mechanic by killing the player with it. They test by killing the player with it. They twist by killing the player with several at once. There is no progression from comfort to challenge; there is only challenge. Players bounce off these games not because the games are too hard but because the games refuse to teach. The Nintendo school's insight is that teaching and challenge are not opposites — teaching produces the foundation that makes challenge meaningful. A player can only be challenged by something they understand. The level's job is to make sure they understand it before it tries to defeat them.

16.9 Affordances and Signifiers

In the early 1990s, the cognitive scientist Donald Norman introduced two concepts that have become indispensable to designers of all kinds: affordances and signifiers. They are useful in level design specifically because they name the precise mechanisms by which players read what a space is for.

An affordance is a relationship between an object and an actor that makes a particular action possible. A door affords being opened. A chair affords being sat on. A button affords being pressed. The affordance is not a property of the object alone — it is a relationship between the object and someone who can use it. A doorknob does not afford turning to a creature without hands.

A signifier is the perceptible cue that indicates an affordance. It tells the actor that the affordance is present. The doorknob signifies the door's openness. The chair's seat signifies its sittability. The button's protrusion and color signify its pressability. Signifiers are what make affordances visible and usable.

In level design, every object the player can interact with has affordances. The question is whether those affordances are signified. A climbable ledge that looks identical to a non-climbable one is an affordance without a signifier — and the player will never use it, because they have no way to know they can. A locked door that looks identical to an unlocked one is similarly unmarked, and the player will repeatedly attempt to open it and feel frustrated.

Good level designers signify aggressively. Every ladder is visible as a ladder. Every climbable surface has a distinct visual treatment (the yellow tape in The Last of Us, the white-paint chalk marks in Uncharted, the slightly lighter colored stones in Skyrim). Every interactable object stands out from its non-interactable equivalents. The player learns the conventions of the game within the first hour and applies them throughout.

💀 Design Autopsy: Aliens: Colonial Marines (Sega, 2013) shipped with a notorious problem: the AI of the alien enemies was so broken that they often did not engage the player. Players moved through corridors with no sense of threat, then occasionally encountered an alien standing in the open. The level design compounded the problem: the corridors contained dozens of objects that looked interactive but were not. Vents that could not be opened. Doors that did nothing. Computer terminals with no function. The signifiers of interactivity were placed throughout the environment — but the affordances were absent. Players learned, painfully, to ignore most of what the environment showed them. The result was a game that felt simultaneously empty and cluttered: full of things the player could see but not engage with. Compare to Alien: Isolation (Creative Assembly, 2014), where every signified affordance is real: every locker can be hidden in, every vent can be entered, every terminal does something. The player learns that the environment is honest, and the resulting attention is what makes the horror work.

The dual failure mode is also worth naming. An affordance with no signifier is invisible. A signifier with no affordance is a lie. Both produce frustration; both undermine the player's trust in the environment. The level designer must continuously audit: every interactable thing must look interactable; every thing that looks interactable must be interactable. Consistency is more important than any individual signifier — the player's mental model of "what kind of object can I use here" is built across the whole game, and inconsistency breaks the model.

16.10 Spatial Literacy: Reading Space Like a Language

Players have a vocabulary for spaces that they have built across thousands of hours of gaming. They can read a space the way a reader reads a sentence: instantly, fluently, often without conscious processing. The level designer who understands this vocabulary can compose spaces that "speak" precisely to the player's expectations — sometimes confirming them, sometimes subverting them, but always engaging them.

Some elements of the spatial vocabulary are nearly universal across games:

• A corridor narrowing signals a transition or an oncoming encounter. Players brace.
• A corridor opening into a wide room signals an arena. Players prepare for combat.
• An obvious choke point (a doorway, a bridge, a narrow ledge) signals a forced confrontation. Players check resources.
• A long line of sight to a distant object signals a destination. Players orient toward it.
• A locked door near the level start signals "come back later." Players note its location and continue.
• A closed door with light leaking under it signals "something is in there." Players approach with care.
• A high ledge with something visible on it signals "find a way up." Players begin looking for a route.
• A pit with no visible bottom signals "do not fall." Players stay back from edges.
• A ledge just out of reach signals "find another route." Players look around for an alternative.
• A graveyard of bodies signals "many have failed here." Players proceed cautiously.

These are not invented by individual games. They are conventions that have accumulated across the medium and that any moderately experienced player has internalized. The level designer who places a chokepoint can reasonably assume the player will read it as a chokepoint. The designer who places a high ledge with a visible reward can reasonably assume the player will start looking for a way up.

But conventions can also be subverted, and the subversion is one of the most powerful tools in level design. The locked door that the player notes for "later" but in fact never opens — because there is nothing behind it — teaches the player a kind of false-positive caution that the rest of the game can exploit. The pit that turns out to be the only way forward (drop into it) violates the "do not fall" convention and rewards the player who is willing to break their own rules. The wide arena with no enemies — the calm that should precede the storm — that simply remains calm, because the storm is somewhere else, plays with the player's anticipation in a way that produces real surprise.

🧩 Productive Struggle: Pick a level from your favorite game and try to write down its spatial "sentences." What is each space saying? Which conventions is it deploying? Are there any places where it subverts a convention? Most levels are written in a fairly conventional spatial grammar, with the occasional poetic flourish. Identifying both the conventions and the deviations is how you start to write spatial sentences yourself.

The vocabulary develops over time, both for the medium as a whole and for the specific game. The first hour of any game is when the designer establishes the local conventions: what color means interactive, what light means safe, what shape means door. By hour three, the player is reading the game's specific dialect fluently. By hour ten, the conventions are invisible and the player is operating on intuition. The designer's job in the first hour is to teach the dialect; the job thereafter is to use it musically.

16.11 Silence Spaces and Intensity Spaces

A useful refinement of pacing is to think of levels as alternating between silence spaces and intensity spaces, with the silence as critical to the experience as the intensity. Silence spaces are moments where the level steps back — quiet rooms, breathing-room corridors, vista views, save points, places where the player can pause and process. Intensity spaces are where the level pushes forward — combat encounters, puzzles under time pressure, horror sequences, bossfights.

Most amateur designers underweight silence. They build levels that are 90% intensity, with brief gaps, on the theory that the player came to play and quiet moments are wasted time. This is wrong, and the wrongness compounds: by removing silence, the designer does not get more intensity, they get less, because intensity requires contrast.

The best games are extravagant with silence. Shadow of the Colossus spends most of its runtime riding a horse through empty wilderness between giant boss fights. The wilderness is not filler — it is the silence that makes the colossi enormous. Journey is mostly walking through quiet sand and ruins, with brief moments of motion or revelation. Dark Souls uses bonfires not just as save points but as silence rooms — places where the player sits, exhales, and prepares to re-enter the threat. Hollow Knight's benches are the same. Breath of the Wild's campfires.

Silence can take many forms. It can be visual silence — emptiness, simplicity, large open spaces with little detail. It can be audio silence — the score drops out, the ambient sound thins, the player hears their own footsteps. It can be mechanical silence — no enemies, no puzzles, no demands, just movement. It can be temporal silence — a section that does not need to be completed quickly, where the player can take their time.

The function of silence is multifold. It allows the player to recover from intensity. It allows them to process what just happened. It allows the next intensity moment to land. It establishes the world as a real place rather than a sequence of game scenarios. It produces the contrast that makes everything else feel like something.

🎮 Play This: Play the first hour of Shadow of the Colossus and pay attention to how much of the runtime is the player riding through empty space. Then play the first hour of any modern action game (God of War, Horizon, anything from the AAA action canon). Count the minutes of sustained low-intensity time in each. The contrast is dramatic, and once you notice it, you will start to notice it everywhere — and to recognize which games are confident enough in their world to leave you alone in it.

The discipline required to design silence is real. You will be tempted to fill it. You will worry the player will be bored. Resist. The bored player can be addressed by minor decoration; the player who never gets to breathe is exhausted regardless of how good the intensity is. Trust your silence. Build it deliberately. It is half of your level.

16.12 The Arena Pattern and Its Variations

The combat arena is the single most common spatial pattern in action game design. It is so common that it has become almost invisible — most players have walked into thousands of arenas without thinking about the pattern. But the pattern has structure, and the structure has variations, and understanding both is essential level design literacy.

The basic arena pattern: the player enters a wide open room. Doors close behind them, sealing them in. Enemies spawn. The player fights until all enemies are defeated. Doors open. The player exits. This is the arena in its purest form — used in Doom (1993), Halo, Devil May Cry, God of War, almost every action game ever made.

The arena works because it isolates the combat encounter from the surrounding navigation, providing a contained space where the player can focus on combat without distraction. The closed doors prevent the player from running away (which would trivialize the encounter), force commitment, and signal clearly that this is a combat moment. The open space gives the player room to maneuver, dodge, and use all of their abilities. The defeat condition (all enemies dead) is unambiguous.

But the basic arena has weaknesses, and the variations exist to address them. Here are the most common.

Arena with verticality: The space includes elevation changes — platforms, ledges, ramps. This adds movement options for the player and creates positional combat (high ground is advantageous). Halo uses this pattern constantly. The variation makes the arena less repetitive across multiple instances.

Arena with cover: The space contains pillars, walls, or terrain that breaks up sightlines. This rewards positioning and movement, creates flanking opportunities, and protects the player from ranged enemies. Standard in Gears of War, where the cover-based combat depends on it.

Arena with hazards: The space contains environmental dangers — pits, fire, electrified floors. The player must navigate the space while fighting, and skilled players can use the hazards against enemies. DOOM Eternal uses environmental hazards constantly to add layers to combat.

Arena with waves: Instead of a single set of enemies, multiple waves spawn sequentially. This produces a longer encounter with escalating intensity and gives the designer control over pacing within the arena. Devil May Cry and Bayonetta use this pattern.

Arena with objectives: The player has a goal beyond "kill all enemies" — protect an NPC, hold a position, destroy a structure, escape within a time limit. This adds tactical complexity and forces decisions about prioritization. Used in horde modes everywhere, in many Halo missions, and in objective-based encounters in tactical shooters.

Open arena: No doors close. The player is free to retreat, reposition, or even leave. This trades the focused intensity of the closed arena for a more emergent encounter where the player's choices about engagement become the design content. Breath of the Wild's overworld combat is essentially open arena.

Multi-layered arena: The space connects to other arenas through corridors or branches, and combat spills across multiple connected spaces. Dark Souls uses this — fights begin in one space and pull through doorways and around corners as enemies and the player move.

The variations are not exclusive. Most modern arenas combine several — verticality plus cover plus environmental hazards plus waves, for example. The skill is in choosing which combination produces the experience you want. A boss arena often uses the basic closed pattern with verticality. A horde mode uses waves with hazards and objectives. A stealth game's "you've been spotted" panic moment is essentially an open arena.

Once you can name and recognize these patterns, you can begin to design counter-patterns — encounters that intentionally violate arena conventions to produce surprise. DOOM 2016's "the doors don't close" moments, where you expect an arena and get free traversal, work because they violate the convention. Hotline Miami's entire design subverts the arena pattern: each combat space is a tiny apartment with no clear arena boundaries, and the encounter is over in seconds rather than minutes. The conventions are powerful precisely because their violation is recognizable.

16.13 Choke Points and Resource Placement

A choke point is any spatial constraint that funnels player movement through a narrow passage. Doorways, bridges, narrow corridors, single-file ledges — any place where the player cannot easily go around. Choke points are powerful design tools because they create forced confrontations: the player and whatever is in the choke point must encounter each other.

Choke points can be used to enforce combat (enemies positioned in the doorway), to force a decision (a difficult enemy at the only path forward), to create suspense (a long approach through a narrow passage), or to produce a sense of risk (a single ledge above a long fall). They are also the easiest way to script a dramatic moment without breaking the player's agency: a scripted event triggered when the player crosses a specific line is invisible if the line is the only way forward.

The opposite of a choke point is an escape valve — a spatial feature that lets the player avoid or retreat from confrontation. A side passage, a staircase to a higher level, a hidden alcove. Escape valves give the player tactical options and reduce the feeling of being trapped. The balance between choke points and escape valves shapes the game's combat texture: lots of choke points produce intense, committed encounters; lots of escape valves produce fluid, mobile encounters.

Resource placement is the level design counterpart of resource management. Where do you put the health pickups, the ammunition, the save points, the upgrades? The placement is not arbitrary — it shapes the entire pacing of the level.

The classic principle: place resources just before the player needs them, but with slight uncertainty. If you place health right before the boss, the player knows the boss is coming. If you place health right after a hard fight, the player is rewarded for surviving. If you place health in a hidden corner the player must explore to find, the fight becomes harder but exploration becomes meaningful. Each placement choice produces different play.

Resource scarcity is a design parameter. Resident Evil places very few resources, forcing the player to ration carefully and producing the genre's signature anxiety. DOOM places resources liberally, encouraging aggressive play. The same enemies in the same spaces play completely differently depending on which resource regime is in effect — and the designer's choice is one of the most consequential a game can make.

A particularly powerful pattern: the forced trade. Place a desirable resource (a powerful weapon, a key item) in a position where collecting it requires committing to a fight, taking damage, or risking death. The player must decide whether the resource is worth the cost. This produces meaningful choice without dialogue, without options menus, just through spatial arrangement.

Choke points and resource placement are where level design and combat design overlap most tightly. The combat designer tunes the enemy and weapon stats; the level designer determines the spaces in which those stats are tested. Without coordination between the two, neither's work survives. This is why most studios have level designers and combat designers in tight collaboration — their decisions are inseparable in the player's experience.

16.14 Spaces of Different Sizes: Player-Sized, Intimidating, Comforting

The size of a space, relative to the player's character, produces strong emotional response — and the designer who controls scale controls a lot of the player's experience.

Player-sized spaces match the character's scale. The corridor is wide enough for the player and a couple of enemies. The ceiling is at a normal head height. The room is sized for ordinary movement. Player-sized spaces feel functional, neutral, comfortable. Most of any game's runtime is spent in player-sized spaces because they are where the actual gameplay happens.

Intimidating spaces are larger than the player needs. The room is vast. The ceiling is impossibly high. The doors are oversized. The architectural features dwarf the character. Intimidating spaces produce awe, vulnerability, and unease — the player feels small, observed, possibly crushed. Cathedral interiors, throne rooms, boss arenas, and the lairs of ancient powers all use intimidating scale to communicate "you are not in control here." Dark Souls' Anor Londo plaza, with its enormous architecture, communicates the divinity of the gods who built it through scale alone.

Comforting spaces are smaller than the player might expect. The room is tight. The ceiling is low. The walls press close. Comforting spaces produce safety, intimacy, focus — a small cabin, a cozy room, a secret enclave. The player feels enclosed and protected. Stardew Valley's farmhouse interior is a comforting space. The save rooms in Resident Evil are comforting (intentionally small, intentionally protective). The benches in Hollow Knight are placed in comforting little nooks.

The same character can occupy different spaces in the same game and feel entirely different. Dark Souls moves you through cramped sewers (claustrophobic), open castle plazas (intimidating), tight bonfire rooms (comforting), and player-sized combat corridors (functional). Each transition produces a shift in emotional register. The level designer is choreographing not just where you fight but how you feel about being there.

📝 Note: Scale is most powerful when it changes. A consistently intimidating space stops being intimidating; the player adapts. A consistently comforting space stops being comforting; it becomes baseline. The intimidating space lands hardest right after a comforting one. The comforting space is most reassuring right after an intimidating one. The composition over time is what matters, not any individual scale choice.

A common mistake is to make every "important" space large. Boss arenas, climactic moments, story beats — designers feel that important things deserve big spaces. Sometimes this works (the Shadow of the Colossus arenas are enormous because the colossi are enormous). Sometimes it does not (a critical character death in an oversized room loses intimacy and becomes melodramatic). The size of the space should match the emotional register of the moment, and emotional register does not always mean big.

16.15 Scale and Awe: Vistas, Towers, and Giants

The deliberate use of scale to produce awe is one of the most distinctive achievements of three-dimensional games and remains one of the most powerful tools in any spatial designer's kit. It works through the contrast between the player's character — small, mortal, fragile — and an environmental element of overwhelming size.

Shadow of the Colossus is the canonical example. The entire game is built around encounters with giants whose size makes the player feel like an insect. The colossi are not just big enemies — they are spaces, with terrain you climb, hair you grip, ledges you traverse. The fight is the act of scaling something larger than any other game had previously asked you to scale. The emotional register is awe and reluctance: the colossi are not evil monsters, just massive, slow, indifferent beings, and your work of killing them is sad in proportion to their grandeur.

Breath of the Wild uses towers and Sheikah Towers as instruments of vertical scale. Climbing one is an enormous physical undertaking — the player traverses what feels like an actual structure, with weight and effort, until reaching the top. The view from the top — the entire region of Hyrule sprawling below — is an awe response engineered by scale. The towers function pedagogically too (they reveal the map and orient the player) but their primary effect is emotional: the player has climbed up here, and the world spreading out below feels both knowable and infinite.

Journey uses scale in the opposite direction — vast horizontal vistas across desert and ruins, with the tiny character moving through enormous, sun-baked space. The scale is not vertical but horizontal, and the awe is of distance, of the immensity of the journey ahead.

Dark Souls uses architectural scale ironically — the Lord's Bowed bow before vast architecture, but the architecture is decayed, ruined, broken. The awe is of past grandeur reduced to remnant, and the player is small among the leavings of greater things. Bloodborne uses the same technique on a different aesthetic register: vast Gothic spires, impossible cathedral interiors, all meant to communicate that the player is in a world of forces too large to contain.

The mechanics of producing awe through scale are reliable. You need:

1. A small character. The player's avatar must be visually recognizable as small — usually framed against the background so that scale is comprehensible at a glance.

2. A massive element. A vista, a tower, a giant, a vast architectural space. Something that exceeds the player's normal frame of reference.

3. A long approach. The element should be visible from a distance and remain visible as the player moves toward it. The duration of the approach builds anticipation. A massive thing seen for the first time from up close does not produce awe; a massive thing seen on the horizon, then approached for ten minutes, then encountered up close, does.

4. A composed reveal. The first time the player sees the element should be choreographed — emerging from a tunnel, cresting a hill, opening a door. The composition of the reveal frames the moment.

5. Emotional space afterward. After the reveal, give the player time to look. Do not immediately throw enemies at them. The awe needs space to settle.

💡 Intuition: Awe is fragile. It depends on novelty (the player has not seen this before), composition (the framing of the reveal), and contrast (with the player's smallness). All three can be destroyed easily. A game that shows you twelve identical massive vistas teaches you to ignore vistas. A reveal that happens off-camera or in the middle of combat does not register. A massive thing without clear smallness for contrast just looks medium-sized. The awe-producing scale moment is one of the highest-return investments in level design — and one of the most easily wasted.

The opportunities for awe in your project will be smaller than Shadow of the Colossus, but they exist. The first time the player sees the full level laid out below them. The first time they realize how far the world extends past their starting area. The first sight of the boss they will eventually fight. Plan these moments. Design them deliberately. Awe is not an accident.

16.16 The History of Level Design as a Discipline

Level design did not always exist as a recognized job. In the earliest commercial games — Pong, Space Invaders, Pac-Man — the entire game was a single screen, and the design of that screen was inseparable from the design of the game itself. The level designer and the game designer were the same person, and the distinction would not have made sense.

The first identifiable level designers worked on games with multiple stages — Donkey Kong (Miyamoto, 1981), Super Mario Bros. (Miyamoto and Tezuka, 1985). The discipline emerged within Nintendo as Miyamoto's stages required someone to think about the order and progression of challenges across many small playable spaces, distinct from the design of the underlying mechanics. Takashi Tezuka, who collaborated with Miyamoto, is often considered the first dedicated level designer. The designs were sketched on graph paper before any code was written — a practice that persists today.

The 1990s saw the explosion of the discipline. Doom (id Software, 1993) shipped with a built-in level editor, which empowered amateurs and produced a generation of level designers who learned by making Doom WADs. John Romero's level design for Doom and Quake established conventions for first-person spatial design that are still in use. The release of Half-Life (Valve, 1998) and Deus Ex (Ion Storm, 2000) demonstrated that level design could carry narrative and immersion at a level previously thought to require cinematics.

The early 2000s saw the rise of "designer-as-architect" thinking, partly through Halo's level designer Jaime Griesemer's writings and talks, partly through the influence of architecture critics writing about games. The discipline began to formalize: level design as distinct from environment art, distinct from systems design, with its own techniques and theories.

The 2010s expanded the discipline in several directions. Dark Souls demonstrated interconnected world design as a discipline in its own right (which we will cover in Chapter 19). Breath of the Wild showed open-world level design at unprecedented scale, with what designer Hidemaro Fujibayashi has called "multiplicative gameplay" emerging from spatial systems. The Witness showed that puzzle design and level design were the same discipline executed at the granularity of a single screen.

Today, level design is a recognized specialty with its own conferences (GDC level design tracks), its own publications (Christopher Totten's An Architectural Approach to Level Design, Mark Brown's Game Maker's Toolkit video series), its own analytical traditions, and its own job descriptions in studios. Most large-studio level designers come from architecture, theater, or film backgrounds, or from years of personal modding — paths that develop the spatial reasoning and compositional intuition the discipline demands.

What unites the discipline across its history is the recognition that space is a design medium. The arrangement of geometry, light, color, and interactive objects is not just a setting for the game — it is the game's most direct channel of communication with the player. Every level designer is, in this sense, doing what Miyamoto and Tezuka did with graph paper in 1985: deciding what the player will see, when, in what order, and what they will be able to do with it.

What is the difference between level design and environment art? Both deal with the visual content of the space, but only one is responsible for the interactive structure of that space. What is the difference between level design and game design? Both deal with the player's experience, but only one is responsible for the spatial arrangement of that experience. Articulating these distinctions helps you locate level design within the broader practice and recognize what is and is not your job when you are doing it.

You are now joining this discipline. Your project work for this chapter — paper-prototyping three levels with pacing charts — is the same work the founders of the field did. Graph paper, pencil, eraser. The tools have not changed because the work has not changed. The medium is space, and the space is composed before any pixel is rendered.

16.17 Project Work: Paper-Prototyping Three Levels

Your project work for this chapter is hands-off-the-keyboard. You will paper-prototype three levels for your action-adventure project, with pacing charts. No Godot. No code. Just graph paper, pencil, colored pens (red, blue, green at minimum), and an hour or two of focused work per level.

The three levels should serve different purposes. Choose three from these five candidates, based on what your project most needs:

1. Level 1 — Tutorial/Opening: Introduces the player to the world and the basic mechanics. Should be linear, gentle, and visually distinct from later areas.
2. Level 2 — First Major Area: Establishes the game's identity. Should mix combat, exploration, and a clear destination. Often features the first significant boss or set piece.
3. Level 3 — Mid-Game Challenge: Tests the player's mastery of mechanics learned so far. Often introduces a new mechanic or tool that the rest of the game will assume.
4. Level 4 — Late-Game Complexity: Combines multiple mechanics in challenging configurations. Should feel like a culmination, not an introduction.
5. Level 5 — Climax/Boss Area: The final or near-final space. Maximum intensity, tightly designed, often linear.

For each level, produce four artifacts:

1. The map. A top-down sketch on graph paper showing the spatial layout. Walls, doors, key objects, enemy positions, item placements. Use symbols you define in a legend (X for enemies, dots for items, vertical lines for doors). The map should be clear enough that another person could read it and understand the level.

2. The pacing chart. A horizontal axis representing player progress through the level (left to right). A vertical axis representing intensity (low at the bottom, high at the top). Plot the intended emotional arc as a curve. Mark the high points (combat encounters, boss fights, set pieces) and the low points (safe rooms, exploration moments, quiet vistas). The curve should have visible peaks and valleys, not a flat line or a monotonic rise.

3. The critical path / optional content map. Take your map from artifact 1, and use a colored pen to trace the critical path the designer expects most players to take. Use a different color to mark optional content (side rooms, secrets, collectibles, alternate routes). Both should be visible. The ratio of critical path to optional content tells you what kind of level you have built.

4. The composition sketch. For each major spatial reveal in the level (typically 2-4 per level), draw a thumbnail of the scene the player sees. What is in the foreground, midground, background? Where does the eye go first? Which leading lines pull the eye where? Which contrasts emphasize what?

The work will take you four to six hours per level if you do it carefully. Resist the temptation to skip the pacing chart or the composition sketches. These are not academic exercises — they are the design tools that will save you weeks of iteration when you start building the levels in Godot in the next chapter.

When you have finished all three levels, lay them out side by side and compare them. Are the pacing curves similar shapes or different? Do the critical-path-to-optional ratios feel right for your game? Do the composition sketches share a visual language, or do they feel like three different games? Use the comparison to identify inconsistencies before you commit to building anything.

📐 Project Checkpoint: Bring your four artifacts per level (map, pacing chart, critical/optional map, composition sketches) to a friend or fellow designer. Walk them through your levels using only the artifacts. Watch what they ask about and where they get confused. The places they struggle to understand are the places your level is unclear — and those are the places you need to revise before you build anything in Godot. Iteration on paper costs minutes. Iteration in code costs hours.

This is the single most important habit a level designer can build. Paper first. Always paper first. The level designers who skip this step waste years of their careers building things that should have been thrown away on paper.

16.18 Thinking Forward

This chapter laid the conceptual foundation. You now know that space is a language, that levels operate on multiple registers simultaneously, that pacing matters as much as content, that wayfinding is invisible art, that the Nintendo school's introduce-test-twist-master pattern underlies most great design. You know what affordances and signifiers are. You know the arena pattern. You know about scale and awe.

In the next chapter, we move from theory to practice in 2D. You will take the paper prototypes you have built in this chapter and begin to translate them into Godot — tilemaps, enemy placement, camera setup, the actual physical realization of the levels you have designed. The translation will reveal the gaps in your designs. Ideas that looked good on paper will reveal problems in execution. Iteration begins.

After 2D, we examine 3D level design (Chapter 18) for the lessons it teaches about depth, verticality, and composition that inform 2D design even when you never build in 3D. And then we zoom out, in Chapter 19, to world design — the architecture of how your individual levels connect into a larger whole.

Level design is, as I said in the opening, the most creative, most iterative, most immediately rewarding part of game development. It is also where many designers discover they have been working in the wrong field — where they realize that they care more about systems than spaces, or more about narrative than mechanics. That is fine. Not every designer is a level designer. But every game has levels, and every game designer needs to understand them well enough to talk to the level designers who will build them — or to recognize when they themselves are the person who should.

You are now equipped to begin. Pick up the graph paper. Sharpen the pencil. Build three levels. The discipline of the medium is older than the medium itself, and you are joining it. The tradition is honest about how hard the work is, and it is also honest about how good the work feels when it is done well.

I will see you in the next chapter, with your paper prototypes in hand, ready to make them real.