Narrative and worldbuilding

Why it matters

Story and world give players reasons to care: about a character, a place, a choice. But games are not films. Players act, and the story has to survive their choices, their skipping of dialogue and their wandering off to collect mushrooms. Narrative design is the craft of telling stories through play, and worldbuilding is creating a setting consistent enough that players can believe in it and act within it.

Narrative designer vs writer

In studios these roles often overlap but are different:

• A writer writes the words: dialogue, item descriptions, barks.
• A narrative designer decides how story is delivered through systems, levels and choices, and makes sure story and mechanics support each other.

Small teams often combine both, and game designers on any team benefit from narrative thinking.

The core idea: story through play

Games tell stories in several layers:

Strong games use several layers, so players who skip dialogue still understand the world through what they see and do.

Ludonarrative harmony

When mechanics and story agree, they reinforce each other. When they clash, players feel it. A character described as gentle who mows down hundreds of enemies is a classic example of ludonarrative dissonance. You do not have to solve this perfectly, but asking "what does this mechanic say about the character and world?" makes designs more coherent.

Worldbuilding that serves play

A believable world is consistent, not exhaustive. Focus on:

• The core difference: the one thing that makes this world unlike ours (magic is fuelled by memory; the sun never sets).
• Rules and consequences: if magic costs memories, characters who use it a lot should forget things.
• Factions and conflict: groups that want different things create quests and choices.
• Visible history: ruins, signs and changes in architecture show the past without a lecture.

Every element should eventually touch play: a place to explore, a choice to make, a mechanic it explains.

Worked example: a narrative brief

For the dungeon game from the paper prototype lesson:

• Logline: A lamplighter's apprentice must descend into the flooded mines to relight the beacon before the village's last oil runs out.
• World: a mining village where the darkness below is alive and drinks light; oil is the most valuable thing anyone owns.
• Character: Mara, 15, wants to prove she is not a child; fears the dark that took her mentor.
• Beats: she enters the mines; she finds her mentor's lamp still burning deep below (turning point); she must choose to carry it home or use its oil to relight the beacon.
• Mechanics fit: light is health because the darkness drinks it; treasure is needed for the exit because the miners' tokens open the lift.
• Environmental story: abandoned lamps placed further and further apart; scratched tally marks on walls.

That one page gives artists, writers and level designers a shared direction.

Common mistakes

• Lore dumps. Long text at the start before players care. Reveal the world as they explore it.
• Story that ignores play. If cutscenes say one thing and mechanics another, players believe the mechanics.
• Too much worldbuilding, too little game. A 50-page history no one sees does not help the player.
• Forcing a single path in a game about freedom. Match narrative structure (linear, branching, emergent) to the game.

Quick recap

• Narrative design tells story through play; worldbuilding creates a consistent setting to act in.
• Use embedded, environmental, emergent and lore layers together.
• Aim for mechanics and story that agree (ludonarrative harmony).
• A one-page narrative brief aligns the team: logline, world, character, beats and how mechanics fit.

Try it

Open the Do tab and write a one-page narrative brief for your game.