Game world design
Worldbuilding for games, where the audience walks around inside the world and pokes at its rules: how the world serves play, the main world structures, spatial design and navigation (Lynch's five elements, weenies, guiding the player), pacing, environmental storytelling, lore delivery, reactive factions, procedural generation, scale and density, the MDA framework, a level design process, Godot implementation pointers and playtesting. General method is on worldbuilding fundamentals; abilities as mechanics are on magic and technology; engine specifics are on nodes and scenes and the other Godot sheets; general usability thinking is on UX and UI. Invented examples are marked.
The world serves play
In fiction the world serves the story; in games it serves play, and the story is one of the things play produces.
| Approach | Starts from | Strength | Risk |
|---|---|---|---|
| Mechanics-first | a verb (jump, grapple, build, sneak) and the spaces that test it | the world fits the gameplay; systems feel native | lore bolted on after the fact; incoherent setting |
| Narrative-first | setting, characters, plot | strong identity and motivation | mechanics that contradict the story; levels as corridors between cutscenes |
| World-first | a place and its rules (ecology, factions, physics) | systemic, emergent play; exploration | aimlessness; the world is interesting but the game isn't |
| Iterative (most real projects) | a core loop plus a setting pitch, refined together | each informs the other | requires discipline to cut |
The best game worlds make mechanics and fiction say the same thing: the world explains why the player can do what they can do, and the rules express the world's themes.
Ludonarrative dissonance
Clint Hocking coined ludonarrative dissonance in October 2007 on his blog Click Nothing, in a post titled "Ludonarrative Dissonance in Bioshock". His argument (paraphrased): BioShock's gameplay rewards self-interest (the Little Sister choice), while its narrative forces the player to help another character without choice, so the game argues one thing through play and the opposite through story, and the contradiction breaks the player's engagement.
| Symptom | Example pattern | Fixes |
|---|---|---|
| Story says one thing, mechanics reward another | a peaceful hero who kills hundreds in gameplay | change the verbs, change the story, or make the contradiction the theme |
| World ignores player actions | NPCs praise a player who robbed them | reactive dialogue, reputation, consequences |
| Urgency without pressure | "the world ends tonight" in an open world with no clock | a real timer, or story framing that allows wandering |
| Rules the world breaks for cutscenes | a character killed by a wound the player shrugs off | keep cutscene stakes within game rules, or signal the exception |
World structures
| Structure | Shape | Examples | Strengths | Trade-offs |
|---|---|---|---|---|
| Linear | a sequence of spaces, one path forward | Half-Life 2, The Last of Us, Uncharted | authored pacing, spectacle, tight difficulty curve | low agency; replay value limited |
| Hub-and-spoke | a central hub with branches to levels | Super Mario 64 (the castle), Hades (the house between runs) | clear home base; choice of order; natural place for story and upgrades | backtracking through the hub; hub can feel like a menu |
| Open world | a continuous large map, mostly accessible early | The Legend of Zelda: Breath of the Wild, Skyrim, Elden Ring | freedom, discovery, emergent stories | pacing hard to control; content density; expensive |
| Metroidvania / interconnected | a connected map gated by abilities; shortcuts loop back | Super Metroid, Hollow Knight, Dark Souls | mastery of one place over time; satisfying shortcuts | players get lost; gating must be readable |
| Procedural | spaces generated by rules each run | Spelunky, Minecraft, No Man's Sky | replayability, surprise | sameness ("procedural oatmeal"); weak authored moments |
| Sandbox | a space plus tools; player sets goals | Minecraft, Dwarf Fortress | creativity, emergent narrative | onboarding; no inherent pacing |
| Instanced / mission-based | separate maps chosen from a menu or map screen | many tactics and action games | tight design per map | the world feels like a list |
Hybrids are the norm: an open world containing linear dungeons, a hub with procedural spokes, a linear game with optional side areas. Designing an open world in depth (landmarks, density, traversal, gating, streaming) is on open-world design.
Spatial design: making spaces legible
Lynch's five elements
Kevin Lynch's The Image of the City (MIT Press, 1960), based on studies of how residents of Boston, Jersey City and Los Angeles mentally mapped their cities, argued that people build a mental image of a place from five kinds of element. A city that supports a clear image is imageable (or legible). Level designers borrowed the framework because players have to do exactly what Lynch's residents did.
| Element | Lynch's meaning | In a game world | Design tips |
|---|---|---|---|
| Paths | channels people move along: streets, walkways, canals, railways | roads, corridors, rivers, ledges, trails | make main paths wider, brighter, better lit; vary them so players can tell them apart |
| Edges | linear boundaries not used as paths: shores, walls, cliffs, railway cuts | map borders, cliffs, water, walls, fog | make edges feel natural (mountains, sea) rather than invisible walls; edges also help orientation ("the sea is west") |
| Districts | medium-to-large areas with a recognizable common character | zones, biomes, neighborhoods, dungeon wings | give each a distinct palette, materials, music, enemies and name |
| Nodes | strategic focal points you enter: junctions, squares | hubs, crossroads, plazas, save points, camps, towns | put decisions, NPCs, shops and save points at nodes; make them readable from paths |
| Landmarks | external reference points, usually seen rather than entered | towers, mountains, giant trees, statues, a volcano | place a few global landmarks visible from most of the map, plus local ones per district |
Weenies
Walt Disney's term weenie (also spelled wienie) names a design element that deliberately draws visitors' attention and pulls them through a space. The term came from film production, where sausages were used to direct dog actors. Sleeping Beauty Castle at the end of Disneyland's Main Street is the classic example; Cinderella Castle, Spaceship Earth at Epcot and the Tree of Life at Animal Kingdom do the same job. Don Carson's Gamasutra essay on environmental storytelling (2000) carries the lesson to games: put your most decorative elements where you want the audience to go, and let them draw people on like a dangling carrot (paraphrased).
In games: a lit tower on the horizon, a column of smoke, a beam of light, a strange tree. The player walks toward it without being told to.
Guiding the player
| Technique | How it works | Notes |
|---|---|---|
| Lighting | players move toward light; darkness reads as danger or dead end | the strongest tool in 3D; light the exit |
| Color | a consistent accent color marks interactables or the route | see color theory; keep the code consistent across the game |
| Leading lines | roads, pipes, cables, cliff edges, rows of lamps point the eye | composition from painting and photography |
| Affordances | shapes that suggest actions: ledges look climbable, cracks look breakable | teach once in a safe place, then reuse |
| Breadcrumbs | a trail of pickups, footprints, blood, coins | reward-driven; don't overuse |
| Sightlines and framing | a doorway or gap frames the goal | reveal the next landmark from a high point |
| Motion | moving things (birds, NPCs, flags, water) attract attention | birds flying away from danger, NPCs running toward it |
| Sound | audio sources pull players: music, voices, machinery | spatialised audio is a guide in the dark |
| Gating | locked doors, broken bridges, ability checks | show the gate before its key (metroidvania rule) so the player remembers it |
| Pinching | narrowing a space funnels players to a point | before a set piece or boss |
| Reveal points | a vista after a climb shows the region ahead | lets players plan; a natural save or rest point |
| Explicit UI | waypoints, compass markers, quest arrows | reliable, accessible, but can make players stare at the HUD instead of the world |
"Yellow paint" and its critics
Yellow paint is the shorthand for brightly colored marks on climbable ledges, ladders and breakable objects. The debate flared around the 2023 Resident Evil 4 remake demo and again around Final Fantasy VII Rebirth in 2024. Critics call it immersion-breaking and patronizing, a patch for environments too detailed to read; defenders point to accessibility and to players who otherwise get stuck. Middle paths:
- Design readable geometry first; add markers only where playtests show confusion.
- Integrate marks into the fiction (worn handholds, chalk marks, a faction's paint).
- Offer a toggle or intensity setting.
- Keep markers consistent: one color, one meaning, everywhere.
Pacing and intensity
A world is experienced over time. Plan intensity like a film editor.
- Tension and release: alternate combat with quiet exploration; danger with safety; tight corridors with open vistas (Carson makes the same point about contrast in theme parks).
- The interest curve: Jesse Schell's The Art of Game Design: A Book of Lenses (2008) devotes a chapter to interest curves: a strong hook at the start, rising interest with peaks and dips, and a climax near the end. Plot your level or quest on one and look for flat stretches.
- Safe rooms: save points, camps, hubs and towns are the "release" beats; make them feel safe (warm light, music, NPCs).
- Teach, test, twist: introduce a mechanic safely, test it under pressure, then combine or subvert it.
- Density rhythm: open worlds need points of interest at intervals the player won't get bored crossing.
Environmental storytelling
Don Carson, for many years a senior show designer at Walt Disney Imagineering, wrote "Environmental Storytelling: Creating Immersive 3D Worlds Using Lessons Learned from the Theme Park Industry" (Gamasutra, March 2000). His premise: "One of the trade secrets behind the design of entertaining themed environments is that the story element is infused into the physical space a guest walks or rides through." Games can do the same.
| Technique | Example (invented unless noted) |
|---|---|
| Cause and effect vignettes: staged scenes that let players deduce what happened (Carson's term) | a barricaded door, claw marks on the inside, an empty rifle |
| Before and after | a flooded village map in the inn; the village itself half underwater |
| Wear and use | paths worn in carpets, polished handrails, a chair turned to face the window |
| Personal clutter | a desk with a half-written letter, a child's drawing pinned above it |
| Architecture as history | newer brick patched onto old stone; a temple converted into a barracks |
| Signage and graffiti | propaganda posters defaced by the resistance |
| Ecology as history | trees growing through a highway; animals nesting in a tank |
Real examples, briefly: Carson cites Half-Life, which tells much of its story through the player's experience of the Black Mesa facility rather than through cutscenes; BioShock's Rapture tells the city's collapse through architecture, posters and audio logs.
Embedded vs emergent narrative
Henry Jenkins's "Game Design as Narrative Architecture" (in First Person, eds Wardrip-Fruin and Harrigan, MIT Press, 2004) describes four ways game spaces carry story:
| Kind | Jenkins's idea (summarized) | Design implication |
|---|---|---|
| Evocative spaces | spaces draw on stories and genres players already know | use genre expectations (the haunted house, the frontier town) |
| Enacted stories | narrative built from the player's movement through space and localized incidents | structure the level as a journey with micro-narratives |
| Embedded narratives | a pre-structured story hidden in the space for the player to reconstruct | plant clues; let players assemble backstory |
| Emergent narratives | stories arising from systems, not pre-scripted | build systems rich enough to produce anecdotes (The Sims, Dwarf Fortress) |
Lore delivery
| Channel | Strengths | Weaknesses | Tips |
|---|---|---|---|
| Item descriptions | optional, dense, rewards curiosity | easy to ignore | one fact per item; hint at links between items |
| Audio logs, letters, diaries | character voice; plays while exploring | contrived (why record this?) | give each a reason to exist; keep them short |
| NPC barks and ambient dialogue | shows culture and opinion in passing | repetition gets annoying | large pools; react to player state and world state |
| Codex or encyclopedia | reference for completists | infodump in a menu | unlock entries by discovery; write in an in-world voice |
| Environmental detail | no interruption at all | ambiguity | back it with a clear internal answer |
| Cutscenes | spectacle, emotion, control | take agency away | keep short; let the player act soon after |
| Quest text | directly tied to goals | functional tone | give quest-givers personality and bias |
| Loading-screen tips | captive audience | forgettable | mix lore with gameplay advice |
Fragmentary vs explicit lore. FromSoftware's games (Dark Souls and its successors) are the best-known example of fragmentary lore: story scattered across item descriptions, architecture and sparse dialogue, leaving players to reconstruct it (communities form around the reconstruction). Explicit lore (codex entries, narrated recaps) serves players who want clarity. The fragmentary style needs a consistent hidden answer or the fragments won't add up; it is the game equivalent of Jo Walton's "incluing" (see worldbuilding fundamentals).
Factions, reputation and reactive worlds
Factions give a world politics players can act on. Faction design fundamentals are on societies and cultures.
| Mechanic | How it works | Example |
|---|---|---|
| Reputation meter per faction | actions raise or lower standing | Fallout: New Vegas tracks reputation with its factions |
| Mutually exclusive allegiances | joining one closes another | choose a side in a civil war |
| Faction territory | control of areas shifts with play | outposts change hands |
| Reactive dialogue | NPCs comment on past actions | guards mention the bridge you burned |
| World-state changes | quests alter the map permanently | a rebuilt town, a destroyed bridge |
| Economy reactions | prices and stock respond to player actions | flooding a market with loot lowers prices |
| Disguises and identity | factions judge by appearance or insignia | wear the uniform to pass the checkpoint |
Rules: show the player why standing changed; make consequences visible in the world, not only in a menu; and budget carefully, because every branch multiplies content.
Procedural generation for worlds
| Technique | What it generates | Notes |
|---|---|---|
| Noise (Perlin, simplex) | terrain heightmaps, moisture, temperature, textures | Ken Perlin developed Perlin noise working on Tron and published it at SIGGRAPH 1985; simplex noise (2001) reduces grid artifacts. Layer several frequencies (octaves) for natural detail |
| Biome from climate | biome per tile from generated temperature and moisture | the same logic as a Whittaker diagram (see physical world) |
| Erosion and hydrology | rivers, valleys, deltas | simulate water flow downhill to fix the "noise mountains" look |
| Wave function collapse | tile layouts that are locally similar to an example | Maxim Gumin's 2016 algorithm; used in Caves of Qud, Bad North and Townscaper |
| Grammars and templates | dungeons, buildings, quests, names | author the pieces; generate the combinations |
| Agent-based history | civilisations, wars, figures, legends | Dwarf Fortress (Bay 12 Games, Tarn and Zach Adams) generates terrain, rivers and erosion, then simulates civilisations spreading, wars and historical figures, browsable in Legends mode |
Procedural oatmeal: Kate Compton's warning that you can generate thousands of bowls of oatmeal that are mathematically different but perceived as the same. Players value perceptual uniqueness, not combinatorial counts. Fixes: fewer, more distinct building blocks; rare hand-made "set pieces"; generated content that has consequences (history, factions) rather than only variation.
Hybrid authoring: hand-author the critical path, landmarks, towns and story beats; generate the connective tissue (terrain, foliage, minor caves), then hand-edit. Seeded generation keeps results reproducible for testing.
Scale and density
| Decision | Consider |
|---|---|
| World size | travel time at the player's movement speed, not square kilometers |
| Content density | how many seconds between points of interest; empty stretches must be deliberate (mood, anticipation) |
| Verticality | climbing, flying, layered cities: a smaller map with more vertical content can feel larger |
| Fast travel | reduces tedium, but also removes the world between nodes; unlock after first visit; tie to in-world features |
| Traversal as play | if travel itself is fun (grappling, gliding, driving), the world can be emptier |
| Scale compression | game worlds compress real scale drastically; a "city" of fifty buildings reads as a city if landmarks and districts are strong |
| Landmark visibility | draw distance and fog decide what the player can navigate by |
Rule of thumb: a smaller, denser world usually beats a larger, emptier one, unless emptiness is the point.
The MDA framework
Robin Hunicke, Marc LeBlanc and Robert Zubek, "MDA: A Formal Approach to Game Design and Game Research" (2004), developed in the Game Design and Tuning Workshop at the Game Developers Conference.
| Layer | Definition (from the paper) | World-design reading |
|---|---|---|
| Mechanics | "the particular components of the game, at the level of data representation and algorithms" | the rules of the world: physics, economy, faction logic, spawn tables |
| Dynamics | "the run-time behavior of the mechanics acting on player inputs and each others outputs over time" | what actually happens: migrations, price swings, ambush patterns, player routes |
| Aesthetics | "the desirable emotional responses evoked in the player, when she interacts with the game system" | wonder, dread, mastery, belonging |
The designer works mechanics → dynamics → aesthetics; the player experiences them the other way round. The paper's eight kinds of fun make a useful target list for a world:
| Aesthetic | Paper's gloss | World features that serve it |
|---|---|---|
| Sensation | game as sense-pleasure | vistas, sound design, weather, tactile movement |
| Fantasy | game as make-believe | a coherent setting you can inhabit; roles |
| Narrative | game as drama | quests, factions, environmental storytelling |
| Challenge | game as obstacle course | hostile terrain, enemies, puzzles |
| Fellowship | game as social framework | shared spaces, co-op, guild halls |
| Discovery | game as uncharted territory | secrets, hidden areas, lore fragments, maps |
| Expression | game as self-discovery | housing, customization, building, playstyle choice |
| Submission | game as pastime | relaxing loops: fishing, farming, wandering |
Level design process
Brief
Purpose of the level: what it teaches or tests, story beat, target duration, mechanics used, emotional aim (MDA aesthetics), where it sits on the interest curve.
Bubble diagram
Spaces as bubbles, connections as lines: start, set pieces, optional areas, gates, keys, the exit. Check flow, loops and critical path before any geometry exists.
Paper map
Top-down sketch with rough scale: landmarks, sightlines, cover, elevation, where the player first sees the goal.
Blockout (greybox)
Build with simple untextured shapes in the engine at true scale. Test movement metrics (jump distance, cover height, door width) and timing. This is where most design happens.
Playtest and iterate
Watch people play without helping. Note where they get lost, bored, stuck or skip content. Iterate the blockout; it is cheap to change now.
Art pass
Dress the level: materials, lighting, props, environmental storytelling. Keep the navigation cues from the blockout intact; art that hides the path is a regression.
Polish and final test
Audio, effects, performance, collision bugs, accessibility settings, a last round of fresh-eyes playtests.
Implementing in Godot
Pointers only; details are on the Godot sheets.
| Need | Godot approach | Sheet |
|---|---|---|
| Levels as units | one scene per level or area, instanced into a world or swapped with a scene change | nodes and scenes |
| 2D tile worlds | the TileMapLayer node (which replaces the deprecated TileMap) with a TileSet holding tiles, collision, navigation and terrains; one node per layer | nodes and scenes |
| Triggers and regions | Area2D / Area3D with body_entered for doors, ambushes, district music | input and physics |
| NPC navigation | navigation regions and agents; TileSet navigation layers | input and physics |
| Lore and item data | custom Resource types for items, codex entries, factions | nodes and scenes |
| World state and reputation | an autoload holding flags and faction standing; save it to disk | resources, saving and export |
| Large worlds | threaded background loading of the next area; streaming chunks | resources, saving and export |
| Guidance cues | lights, emissive materials, animated props, audio players placed as weenies | UI, animation and audio |
| Visual districts | per-area environments, color grading, shader effects (fog, water) | shaders |
A minimal world-state autoload for faction reputation:
# world_state.gd (autoload as WorldState)
extends Node
signal reputation_changed(faction: StringName, value: int)
var flags: Dictionary = {}
var reputation: Dictionary = {
&"wardens": 0,
&"salt_guild": 0,
}
func change_rep(faction: StringName, delta: int) -> void:
var v: int = clampi(reputation.get(faction, 0) + delta,
-100, 100)
reputation[faction] = v
reputation_changed.emit(faction, v)
func set_flag(key: StringName, value := true) -> void:
flags[key] = valuePlaytesting the world
| Method | Reveals |
|---|---|
| Silent observation | where players look, hesitate, backtrack; what they ignore |
| Think-aloud | what players believe the world is telling them (often not what you meant) |
| Position heatmaps | where players actually go; unused areas; bottlenecks |
| Death heatmaps | difficulty spikes, unfair ambushes, confusing hazards |
| Time-to-objective | whether guidance works; outliers show confusion |
| "Where are you?" questions | whether the mental map forms: can players point to the landmark, name the district? |
| Lore recall | whether environmental storytelling lands: ask what happened in the room |
| Fresh testers each round | people who haven't learned your level's tricks |
Signs of a navigation problem: players hugging walls, spinning the camera, opening the map repeatedly, walking into decorative dead ends, or asking "where am I supposed to go?".
Common mistakes
| Mistake | Fix |
|---|---|
| Lore that contradicts mechanics (ludonarrative dissonance) | align verbs with story or make the tension deliberate |
| Huge empty open world | shrink it, increase density, or make traversal itself fun |
| No landmarks; every area looks the same | global landmarks, distinct districts |
| Invisible walls | natural edges: cliffs, water, dense foliage |
| Art pass hides the path | protect blockout sightlines and lighting |
| Codex infodumps as the main story channel | environmental storytelling first; codex for depth |
| Procedural oatmeal | fewer, more distinct pieces; hand-made set pieces |
| Gates shown after the key | show the locked door first |
| Reactive systems nobody notices | surface consequences in dialogue, world state and UI |
| Fast travel from the start | unlock after discovery |
| Designing only at the desk | blockout and playtest early and often |
| Uniform intensity | plot the interest curve; add rest beats |
Templates
Level design document
LEVEL: WORLD POSITION: (hub/zone)
PURPOSE: teach / test / twist:
MECHANICS USED: NEW MECHANIC INTRODUCED:
STORY BEAT:
TARGET AESTHETICS (MDA):
TARGET DURATION: DIFFICULTY:
INTEREST CURVE: hook / peaks / rest / climax
CRITICAL PATH: start -> ... -> exit
OPTIONAL AREAS AND REWARDS:
GATES AND KEYS (gate seen before key? y/n):
LANDMARKS: global: local:
NODES (decisions, NPCs, saves):
EDGES (how bounds are shown):
GUIDANCE: light / color / lines / sound / UI
ENVIRONMENTAL STORY VIGNETTES:
ENEMIES AND ENCOUNTERS:
METRICS: jump, cover height, door width
BUBBLE DIAGRAM: link
BLOCKOUT: link PLAYTEST NOTES: linkArea / biome sheet
AREA: DISTRICT IDENTITY (one line):
CLIMATE AND BIOME (see physical world sheet):
PALETTE: MATERIALS:
MUSIC AND AMBIENT SOUND:
LANDMARKS VISIBLE FROM HERE:
ENTRY / EXIT POINTS:
TRAVERSAL: verbs needed, hazards, shortcuts
FACTION CONTROL: REPUTATION EFFECTS:
ENEMIES / CREATURES (and why they live here):
RESOURCES / LOOT:
LORE: what happened here (hidden truth):
what the player can find out (fragments):
POINTS OF INTEREST (and spacing in seconds):
FAST TRAVEL POINT: y/n, in-world form:Quest template
QUEST: GIVER (faction, bias):
HOOK (why the player cares):
GOAL (stated): REAL SITUATION (hidden):
STEPS:
1.
2.
3.
LOCATIONS (existing areas reused?):
MECHANICS EXERCISED:
CHOICES AND CONSEQUENCES:
option A -> world change: reputation:
option B -> world change: reputation:
FAIL STATE:
REWARDS: items / reputation / lore / access
LORE DELIVERED (channel):
REACTIVITY (who mentions it later):
LUDONARRATIVE CHECK: do mechanics match the story?References
- Ludonarrative dissonance (Wikipedia) (opens in a new tab): Clint Hocking's October 2007 Click Nothing post "Ludonarrative Dissonance in Bioshock" and later examples
- Kevin Lynch, The Image of the City (MIT Press, 1960): paths, edges, districts, nodes, landmarks; imageability
- The Image of the City (Wikipedia) (opens in a new tab): summary of the five elements
- Weenie (design) (Wikipedia) (opens in a new tab): Walt Disney's term, its origin and examples
- Don Carson, "Environmental Storytelling: Creating Immersive 3D Worlds Using Lessons Learned from the Theme Park Industry" (Gamasutra, 2000) (opens in a new tab): cause-and-effect vignettes, contrast, drawing the audience
- Henry Jenkins, "Game Design as Narrative Architecture" (2004) (opens in a new tab): evocative, enacted, embedded and emergent narrative
- Hunicke, LeBlanc and Zubek, "MDA: A Formal Approach to Game Design and Game Research" (2004) (opens in a new tab): mechanics, dynamics, aesthetics and the eight kinds of fun
- Jesse Schell, The Art of Game Design: A Book of Lenses (Morgan Kaufmann, 2008; 3rd ed. 2019): interest curves and design lenses
- Yellow paint in video games (Wikipedia) (opens in a new tab): the debate and its arguments
- Procedural generation (Wikipedia) (opens in a new tab): "procedural oatmeal" and Kate Compton
- Kate Compton, "So you want to build a generator" (opens in a new tab): practical guide to generators, source of the oatmeal image
- Perlin noise (Wikipedia) (opens in a new tab): origin (Tron, SIGGRAPH 1985) and simplex noise
- Maxim Gumin, WaveFunctionCollapse (GitHub) (opens in a new tab): the algorithm and games using it
- Dwarf Fortress (Wikipedia) (opens in a new tab): world generation, history simulation, Legends mode
- Godot docs: TileMapLayer (opens in a new tab): the tile layer node and TileSet features