../

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.

ApproachStarts fromStrengthRisk
Mechanics-firsta verb (jump, grapple, build, sneak) and the spaces that test itthe world fits the gameplay; systems feel nativelore bolted on after the fact; incoherent setting
Narrative-firstsetting, characters, plotstrong identity and motivationmechanics that contradict the story; levels as corridors between cutscenes
World-firsta place and its rules (ecology, factions, physics)systemic, emergent play; explorationaimlessness; the world is interesting but the game isn't
Iterative (most real projects)a core loop plus a setting pitch, refined togethereach informs the otherrequires 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.

SymptomExample patternFixes
Story says one thing, mechanics reward anothera peaceful hero who kills hundreds in gameplaychange the verbs, change the story, or make the contradiction the theme
World ignores player actionsNPCs praise a player who robbed themreactive dialogue, reputation, consequences
Urgency without pressure"the world ends tonight" in an open world with no clocka real timer, or story framing that allows wandering
Rules the world breaks for cutscenesa character killed by a wound the player shrugs offkeep cutscene stakes within game rules, or signal the exception

World structures

StructureShapeExamplesStrengthsTrade-offs
Lineara sequence of spaces, one path forwardHalf-Life 2, The Last of Us, Unchartedauthored pacing, spectacle, tight difficulty curvelow agency; replay value limited
Hub-and-spokea central hub with branches to levelsSuper Mario 64 (the castle), Hades (the house between runs)clear home base; choice of order; natural place for story and upgradesbacktracking through the hub; hub can feel like a menu
Open worlda continuous large map, mostly accessible earlyThe Legend of Zelda: Breath of the Wild, Skyrim, Elden Ringfreedom, discovery, emergent storiespacing hard to control; content density; expensive
Metroidvania / interconnecteda connected map gated by abilities; shortcuts loop backSuper Metroid, Hollow Knight, Dark Soulsmastery of one place over time; satisfying shortcutsplayers get lost; gating must be readable
Proceduralspaces generated by rules each runSpelunky, Minecraft, No Man's Skyreplayability, surprisesameness ("procedural oatmeal"); weak authored moments
Sandboxa space plus tools; player sets goalsMinecraft, Dwarf Fortresscreativity, emergent narrativeonboarding; no inherent pacing
Instanced / mission-basedseparate maps chosen from a menu or map screenmany tactics and action gamestight design per mapthe 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.

district old town: one look, one use, one name district docks: distinct materials and sounds node plaza where paths meet landmark tower seen from across the map path path edge river, wall or cliff: a boundary line sightline
Lynch's five elements on a small invented map
ElementLynch's meaningIn a game worldDesign tips
Pathschannels people move along: streets, walkways, canals, railwaysroads, corridors, rivers, ledges, trailsmake main paths wider, brighter, better lit; vary them so players can tell them apart
Edgeslinear boundaries not used as paths: shores, walls, cliffs, railway cutsmap borders, cliffs, water, walls, fogmake edges feel natural (mountains, sea) rather than invisible walls; edges also help orientation ("the sea is west")
Districtsmedium-to-large areas with a recognizable common characterzones, biomes, neighborhoods, dungeon wingsgive each a distinct palette, materials, music, enemies and name
Nodesstrategic focal points you enter: junctions, squareshubs, crossroads, plazas, save points, camps, townsput decisions, NPCs, shops and save points at nodes; make them readable from paths
Landmarksexternal reference points, usually seen rather than enteredtowers, mountains, giant trees, statues, a volcanoplace 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

TechniqueHow it worksNotes
Lightingplayers move toward light; darkness reads as danger or dead endthe strongest tool in 3D; light the exit
Colora consistent accent color marks interactables or the routesee color theory; keep the code consistent across the game
Leading linesroads, pipes, cables, cliff edges, rows of lamps point the eyecomposition from painting and photography
Affordancesshapes that suggest actions: ledges look climbable, cracks look breakableteach once in a safe place, then reuse
Breadcrumbsa trail of pickups, footprints, blood, coinsreward-driven; don't overuse
Sightlines and framinga doorway or gap frames the goalreveal the next landmark from a high point
Motionmoving things (birds, NPCs, flags, water) attract attentionbirds flying away from danger, NPCs running toward it
Soundaudio sources pull players: music, voices, machineryspatialised audio is a guide in the dark
Gatinglocked doors, broken bridges, ability checksshow the gate before its key (metroidvania rule) so the player remembers it
Pinchingnarrowing a space funnels players to a pointbefore a set piece or boss
Reveal pointsa vista after a climb shows the region aheadlets players plan; a natural save or rest point
Explicit UIwaypoints, compass markers, quest arrowsreliable, 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.

TechniqueExample (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 aftera flooded village map in the inn; the village itself half underwater
Wear and usepaths worn in carpets, polished handrails, a chair turned to face the window
Personal cluttera desk with a half-written letter, a child's drawing pinned above it
Architecture as historynewer brick patched onto old stone; a temple converted into a barracks
Signage and graffitipropaganda posters defaced by the resistance
Ecology as historytrees 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:

KindJenkins's idea (summarized)Design implication
Evocative spacesspaces draw on stories and genres players already knowuse genre expectations (the haunted house, the frontier town)
Enacted storiesnarrative built from the player's movement through space and localized incidentsstructure the level as a journey with micro-narratives
Embedded narrativesa pre-structured story hidden in the space for the player to reconstructplant clues; let players assemble backstory
Emergent narrativesstories arising from systems, not pre-scriptedbuild systems rich enough to produce anecdotes (The Sims, Dwarf Fortress)

Lore delivery

ChannelStrengthsWeaknessesTips
Item descriptionsoptional, dense, rewards curiosityeasy to ignoreone fact per item; hint at links between items
Audio logs, letters, diariescharacter voice; plays while exploringcontrived (why record this?)give each a reason to exist; keep them short
NPC barks and ambient dialogueshows culture and opinion in passingrepetition gets annoyinglarge pools; react to player state and world state
Codex or encyclopediareference for completistsinfodump in a menuunlock entries by discovery; write in an in-world voice
Environmental detailno interruption at allambiguityback it with a clear internal answer
Cutscenesspectacle, emotion, controltake agency awaykeep short; let the player act soon after
Quest textdirectly tied to goalsfunctional tonegive quest-givers personality and bias
Loading-screen tipscaptive audienceforgettablemix 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.

MechanicHow it worksExample
Reputation meter per factionactions raise or lower standingFallout: New Vegas tracks reputation with its factions
Mutually exclusive allegiancesjoining one closes anotherchoose a side in a civil war
Faction territorycontrol of areas shifts with playoutposts change hands
Reactive dialogueNPCs comment on past actionsguards mention the bridge you burned
World-state changesquests alter the map permanentlya rebuilt town, a destroyed bridge
Economy reactionsprices and stock respond to player actionsflooding a market with loot lowers prices
Disguises and identityfactions judge by appearance or insigniawear 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

TechniqueWhat it generatesNotes
Noise (Perlin, simplex)terrain heightmaps, moisture, temperature, texturesKen 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 climatebiome per tile from generated temperature and moisturethe same logic as a Whittaker diagram (see physical world)
Erosion and hydrologyrivers, valleys, deltassimulate water flow downhill to fix the "noise mountains" look
Wave function collapsetile layouts that are locally similar to an exampleMaxim Gumin's 2016 algorithm; used in Caves of Qud, Bad North and Townscaper
Grammars and templatesdungeons, buildings, quests, namesauthor the pieces; generate the combinations
Agent-based historycivilisations, wars, figures, legendsDwarf 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

DecisionConsider
World sizetravel time at the player's movement speed, not square kilometers
Content densityhow many seconds between points of interest; empty stretches must be deliberate (mood, anticipation)
Verticalityclimbing, flying, layered cities: a smaller map with more vertical content can feel larger
Fast travelreduces tedium, but also removes the world between nodes; unlock after first visit; tie to in-world features
Traversal as playif travel itself is fun (grappling, gliding, driving), the world can be emptier
Scale compressiongame worlds compress real scale drastically; a "city" of fifty buildings reads as a city if landmarks and districts are strong
Landmark visibilitydraw 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.

LayerDefinition (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:

AestheticPaper's glossWorld features that serve it
Sensationgame as sense-pleasurevistas, sound design, weather, tactile movement
Fantasygame as make-believea coherent setting you can inhabit; roles
Narrativegame as dramaquests, factions, environmental storytelling
Challengegame as obstacle coursehostile terrain, enemies, puzzles
Fellowshipgame as social frameworkshared spaces, co-op, guild halls
Discoverygame as uncharted territorysecrets, hidden areas, lore fragments, maps
Expressiongame as self-discoveryhousing, customization, building, playstyle choice
Submissiongame as pastimerelaxing loops: fishing, farming, wandering

Level design process

  1. 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.

  2. 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.

  3. Paper map

    Top-down sketch with rough scale: landmarks, sightlines, cover, elevation, where the player first sees the goal.

  4. 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.

  5. 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.

  6. 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.

  7. 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.

NeedGodot approachSheet
Levels as unitsone scene per level or area, instanced into a world or swapped with a scene changenodes and scenes
2D tile worldsthe TileMapLayer node (which replaces the deprecated TileMap) with a TileSet holding tiles, collision, navigation and terrains; one node per layernodes and scenes
Triggers and regionsArea2D / Area3D with body_entered for doors, ambushes, district musicinput and physics
NPC navigationnavigation regions and agents; TileSet navigation layersinput and physics
Lore and item datacustom Resource types for items, codex entries, factionsnodes and scenes
World state and reputationan autoload holding flags and faction standing; save it to diskresources, saving and export
Large worldsthreaded background loading of the next area; streaming chunksresources, saving and export
Guidance cueslights, emissive materials, animated props, audio players placed as weeniesUI, animation and audio
Visual districtsper-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] = value

Playtesting the world

MethodReveals
Silent observationwhere players look, hesitate, backtrack; what they ignore
Think-aloudwhat players believe the world is telling them (often not what you meant)
Position heatmapswhere players actually go; unused areas; bottlenecks
Death heatmapsdifficulty spikes, unfair ambushes, confusing hazards
Time-to-objectivewhether guidance works; outliers show confusion
"Where are you?" questionswhether the mental map forms: can players point to the landmark, name the district?
Lore recallwhether environmental storytelling lands: ask what happened in the room
Fresh testers each roundpeople 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

MistakeFix
Lore that contradicts mechanics (ludonarrative dissonance)align verbs with story or make the tension deliberate
Huge empty open worldshrink it, increase density, or make traversal itself fun
No landmarks; every area looks the sameglobal landmarks, distinct districts
Invisible wallsnatural edges: cliffs, water, dense foliage
Art pass hides the pathprotect blockout sightlines and lighting
Codex infodumps as the main story channelenvironmental storytelling first; codex for depth
Procedural oatmealfewer, more distinct pieces; hand-made set pieces
Gates shown after the keyshow the locked door first
Reactive systems nobody noticessurface consequences in dialogue, world state and UI
Fast travel from the startunlock after discovery
Designing only at the deskblockout and playtest early and often
Uniform intensityplot 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: link

Area / 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