Level design consulting based on "Level Design: Processes and Experiences" (CRC Press). Use when helping with spatial game design, environment layout, player guidance, pacing, open-world planning, hiding linearity, themed environments, procedural vs handmade content, play-personas, or evaluating level quality. Covers horror level design, indie game practices, and AAA open-world techniques. NOT for coding - focused on design philosophy and player spatial experience.
A design consulting framework based on "Level Design: Processes and Experiences" edited by Christopher W. Totten (CRC Press, 2017).
Level design is the thoughtful execution of gameplay into gamespace for players to dwell in. It sits at the intersection of programming, design, and art—implementing the game design vision while leading players through experiences without revealing the designer's presence.
"Level designers don't merely create things for players to do. They create situations that invite players to interpret who they are." — Brian Upton
| Type | Key Considerations |
|---|---|
| Linear | Hide linearity through visual choice, narrative lures, environmental storytelling |
| Open-World | POI density, anchor locations, subregions, orientation landmarks |
| Horror | Anticipatory play, corners, one-way doors, visible-but-blocked escape |
| Procedural | Horizontal vs vertical integration of handmade content |
| Indie/Focused | Expand single core mechanic through level variation |
Players must feel in control even when following a predetermined path.
| Technique | Description |
|---|---|
| Coerced Progression | Time pressure, pursuing enemies—no time to question the path |
| Environmental Signage | In-world signs, color coding (Mirror's Edge red) |
| NPC Guides | Companions who lead, escort targets who follow, enemies to chase |
| Narrative Lures | Visible objectives, story hooks that pull forward |
| Forced Choice Illusion | Block one path as player approaches, making "choice" feel organic |
See: references/hiding-linearity.md
Horror isn't about jump scares—it's about dread before the corner.
"Anticipatory play requires variety—the situation must evolve so players continually reassess. Static horrors become played out."
See: references/anticipatory-play.md
Three living documents for large-scale world design:
The frequency of points of interest defines exploration feel:
See: references/open-world-planning.md
Model player behavior before and after implementation.
High-level behaviors: Center vs periphery dwelling, early vs late pill eating, linear vs broken paths
→ 8 persona combinations including "Fraidy Cat" (periphery, early pills, linear) and "Risk Taker" (center, late pills, broken)
See: references/play-personas.md
Classic environmental themes with established mechanics and expectations:
| Trope | Core Elements | Design Advantages |
|---|---|---|
| Fire/Ice | Environmental hazards, timing puzzles | Color variety, physics tweaks |
| Dungeon/Cavern | Tileable textures, traps, treasure | Easily repeatable, expected danger |
| Factory | Moving platforms, conveyers, gears | Repurposable mechanics, scalable difficulty |
| Jungle | Vines, branches, water, wildlife | Fluid movement, colorful outdoor |
| Spooky | Atmosphere, surprise, undead | Combines with any theme |
| Pirate | Ships, treasure, melee, water | Action-ready, clear rewards |
| Urban | Verticality, cover, vehicles | Real-world familiarity |
| Space Station | Tech hazards, airlocks, zero-G | Sci-fi dungeon equivalent |
| Sewer | Pipes, rats, rising water | Modern dungeon stand-in |
Mexican Pizza Technique: Combine two tropes for fresh results (fire + graveyard, jungle + urban ruins)
See: references/themed-environments.md
When working with limited resources:
| Practice | Description |
|---|---|
| Expand Core Mechanic | One strong mechanic explored through level variation (VVVVVV) |
| Iterative Level Design | Rapid prototyping, playtest early and often |
| Design Modes Not Levels | Create systems that generate challenge (endless runners) |
| Embrace Emergence | Simple rules, complex interactions |
| Object-Oriented Design | Modular elements that combine predictably |
See: references/indie-practices.md
Two integration models:
Handmade thread runs through procedural content (FTL quest chains, Spelunky secrets)
Best for: Narrative, puzzle sequences, coherent story beats
Procedural and handmade content interchangeable in same slot (Dungeon Crawl vaults, URR buildings)
Best for: Ensuring specific gameplay moments, quality floors
Should players see which is which?
See: references/procedural-handmade.md
When evaluating a level design:
| Pitfall | Symptom | Solution |
|---|---|---|
| Obvious Rails | Player comments on being "on rails" | Add visual choice, narrative justification |
| Empty Space | Players comment on emptiness | Increase POI density or justify sparseness |
| Lost Players | Players wander aimlessly | Add orientation landmarks, environmental cues |
| Played-Out Scares | Horror stops being scary | Keep threats evolving, limit exposure time |
| Arbitrary Barriers | Players frustrated by blocked paths | Use narrative-justified or natural boundaries |
| Tutorial Overload | Players skip to "real game" | Teach through safe early gameplay |