Part V: Narrative Design
Chapters 20--23
Let me say something that will annoy a lot of writers: games do not tell stories. Not really. Not the way books tell stories or films tell stories. Those are authored experiences --- fixed sequences of events crafted by a storyteller and received by an audience. Games are something else entirely. Games create contexts in which stories happen. The player is not an audience member. The player is an agent. And the story is not what the designer wrote. The story is what the player did.
This distinction matters enormously, and misunderstanding it is responsible for most bad game writing. Every designer who has tried to make a movie with a controller attached --- forcing the player through unskippable cutscenes, locking them in corridors of plot, taking away their agency to deliver a story beat --- has experienced the fundamental tension of narrative design. The player wants to do things. The story requires things to happen. Reconciling those impulses is the core challenge of this discipline, and there is no universal solution. There are only tradeoffs, and this part of the book is about understanding those tradeoffs well enough to make them intentionally.
The good news: when narrative design works --- when story and gameplay are inseparable, when the player's actions are the story, when the game creates meaning that could not exist in any other medium --- the result is more powerful than any book or film. Because the player was there. They did it. It happened to them.
What You Will Learn
Chapter 20: Narrative in Games lays the theoretical groundwork. What makes interactive storytelling different from linear storytelling? What are the structural models --- linear, branching, modular, emergent --- and what does each one sacrifice and gain? We will analyze how Dark Souls tells a story through item descriptions, architecture, and environmental clues that the player may or may not find, creating a narrative that rewards attention without punishing inattention. We will look at how Celeste integrates its story (a young woman climbing a mountain while battling anxiety and self-doubt) into its mechanics (the mountain literally manifests her inner demons as gameplay challenges). And we will examine how Breath of the Wild creates a narrative structure that works regardless of the order in which the player encounters it --- a story told in fragments that the player assembles into their own understanding. You will write a one-page narrative outline for your project: the story arc, the key beats, and how they connect to gameplay.
Chapter 21: Dialogue, Characters, and Writing for Games gets into the craft of writing words that players will actually read. Game dialogue is not screenplay dialogue. It is not novel dialogue. It is dialogue that exists inside a system, that the player may encounter in any order, that competes for attention with gameplay, and that must convey information efficiently while also characterizing speakers and building world. It is brutally hard to write well, and most games do it poorly. This chapter covers dialogue trees, branching conversation design, barks (the short contextual lines that NPCs and companions speak during gameplay), character voice development, and the practical challenge of writing dialogue that works whether the player reads every word or mashes through it. You will implement a branching dialogue system in Godot and write two or three NPC conversations that serve both narrative and gameplay functions --- giving the player story context, quest information, or mechanical hints through character interaction.
Chapter 22: Environmental Storytelling and Worldbuilding Without Words is about the narrative that exists in the spaces between dialogue. A room tells a story. A crumbling wall tells a story. A table set for dinner with the chairs knocked over tells a story. Environmental storytelling is the art of embedding narrative into the game world so that the player discovers story rather than being told it. Dark Souls is the master of this technique: the placement of enemies, the architecture of spaces, the items scattered in specific locations, the corpses pointing toward secrets --- every element of the world is a narrative artifact that rewards careful observation. Breath of the Wild uses ruins, landmarks, and the sheer archaeology of a post-apocalyptic Hyrule to tell a story of civilization lost and remembered. This chapter covers visual narrative (what the environment communicates), prop storytelling (objects that imply events), architectural narrative (spaces that tell stories through their design), and the principle that the most powerful stories in games are the ones the player feels they discovered rather than the ones the game told them. You will add environmental storytelling to Level 1 of your project --- details that imply history, that reward observation, that make the world feel lived-in.
Chapter 23: Cutscenes, Cinematics, and When to Take Control Away from the Player tackles the most controversial tool in the narrative designer's kit. Cutscenes take away the thing that makes games unique: player agency. And yet some of the most memorable moments in gaming history are cutscenes. The death of Aerith. "Would you kindly." The ending of The Last of Us. The trick is knowing when to take control away, for how long, and why. This chapter covers in-engine cinematics versus pre-rendered sequences, camera direction for interactive media, the pacing of non-interactive moments within interactive experiences, and the principle that every cutscene must earn the player's attention by delivering something that gameplay alone could not. You will add one or two brief in-engine cutscenes to your project --- under thirty seconds each --- and design them so they enhance rather than interrupt the player's experience.
The Narrative Design Mindset
Here is the shift I want to create in your thinking: narrative is not a layer you add on top of gameplay. It is not frosting on a mechanics cake. Narrative and mechanics are inseparable in well-designed games. The story is expressed through the systems, and the systems create the conditions for story.
Celeste does not have a story and a platformer. It is a game where the act of struggling through difficult platforming IS the story. Madeline's journey up the mountain is your journey through the levels. Her setbacks are your deaths. Her breakthroughs are your breakthroughs. The mechanics are the narrative.
Dark Souls does not have combat and a story. The loneliness, the dread, the perseverance, the gradual mastery --- those are not themes in a cutscene. They are what the game feels like to play. The narrative emerges from the mechanics. You are alone in a hostile world. You die over and over. You learn. You persist. You prevail. That is the story of the Chosen Undead, and you lived it through the controller.
Breath of the Wild does not have an open world and a narrative. The open world IS the narrative. Link awakens with no memory in a ruined kingdom. The player explores with no knowledge of a ruined world. Link's amnesia and the player's ignorance are the same thing. Every discovery the player makes is a memory Link recovers. The narrative structure mirrors the gameplay structure mirrors the emotional arc. That is not coincidence. That is design.
When you design your game's narrative, do not think "what story do I want to tell?" Think "what story does the player's experience create?" Then find ways to reinforce, deepen, and give meaning to that experience through character, dialogue, environment, and --- sparingly --- cutscenes.
Your Project After Part V
By the end of these chapters, you will have:
- A one-page narrative outline with story arc and key beats
- A branching dialogue system implemented in Godot
- Two or three NPC conversations serving both narrative and gameplay functions
- Environmental storytelling details in Level 1
- One or two brief in-engine cutscenes (under 30 seconds each)
- A narrative woven into your game's mechanics and world
Your game will start to feel like it has meaning. Not meaning in the pretentious, "games are art" sense --- though they are --- but meaning in the sense that the player's actions feel purposeful, the world feels inhabited, and the experience adds up to something more than the sum of its mechanics. That "something more" is what narrative design creates.
A game without narrative design is a toy. There is nothing wrong with toys. Some of the best games ever made are essentially toys --- Tetris, Baba Is You, Super Hexagon. But if you are building a game with a world, with characters, with any sense of place or purpose, you need narrative design. Not a Hollywood script. Not a novel. A design discipline that treats story as a system --- one that interacts with all your other systems to create an experience that could not exist in any other medium.
That is what games can do that nothing else can. Make the player the author of a story they will never forget, because they lived it.