There is a moment in Outer Wilds—maybe the tenth time you’ve watched your solar system collapse into itself—when you realize nobody was ever going to sit you down and explain what happened to the Nomai. The ruin was the text. The loop was the structure. And the narrative was something you assembled, piece by piece, from a system of rules designed to make discovery inevitable without making it automatic. That is not a writing achievement. It is a plotting achievement. The distinction matters.
I bring it up because I think we have been misreading how narrative works in games for a long time. The conventional vocabulary treats story in games as either something the writer crafts (cutscenes, dialogue, lore documents) or something the player creates (emergent moments, unexpected interactions, the time your friend shot you off a cliff in a co-op game). Both framings miss a third thing the best indie games are doing: they build systems structurally capable of producing narrative-shaped outcomes, the way a plot structure in fiction produces meaning from the arrangement of events rather than from the prose itself.
This is not a small distinction. It changes what you look at when you evaluate a game’s narrative. It changes what designers should be building. And it suggests that game designers and narrative writers share a craft problem they rarely discuss together: how to construct a system that produces outcomes neither the creator nor the audience can fully predict, but that feel inevitable in retrospect.
The Plot Is the System
In fiction, plot is not the events. Plot is the structure that makes the events meaningful. A character wants something, encounters resistance, and the resistance escalates until the structure resolves. The meaning lives in the relationship between events, in the way the structure makes certain outcomes feel earned. This is why you can spoil a plot but not a structure: knowing that the detective solves the murder does not change the experience of watching the structure produce that solution through constraint and revelation.
The best indie game narratives work the same way, except the structure is not a narrative outline. It is a mechanical system. The rules of the game, the feedback loops, the resource constraints, the information economy—these are the plot structure. The events that emerge from those rules are the story. And the player’s experience of that story is not passive reception but active deduction, the same way a reader of a well-plotted novel is actively constructing meaning from the structural clues the writer has embedded.
Outer Wilds is the clearest example I know. The game’s central system is a 22-minute time loop. Every rule in the game is designed to make that loop produce narrative. The planets change over time, so locations are accessible at some moments and not others. The Nomai ruins are scattered across a solar system that is physically navigable but informationally opaque. The player carries no progression items, no levels, no upgrades—only knowledge. The entire game is a structure that turns curiosity into narrative through constraint. You cannot read all the texts. You cannot visit all the locations in one loop. You cannot be in two places at once. The system forces you to choose what to investigate, and those choices, combined with the time pressure, produce a story that is different for every player but structurally inevitable for all of them. Everyone who finishes Outer Wilds reaches the same understanding of what happened. But the path there—the sequence of revelations, the moments of confusion and clarity—belongs to the player because the system generated it, not because the writer scripted it.
That is plotting. Not writing. Plotting.
Obra Dinn and the Structure of Deduction
Return of the Obra Dinn does something structurally similar but mechanically different. Lucas Pope built a game about an insurance adjuster investigating the deaths of sixty people on a ghost ship. The narrative is not delivered through cutscenes or dialogue trees. It is delivered through a system: you observe frozen moments of death, you identify who is who, and the game’s logic forces you to deduce relationships, causes, and identities from partial information.
The structural brilliance of Obra Dinn is that the story is non-chronological but the deduction is cumulative. You cannot understand chapter four without information from chapter eight. You cannot identify the captain without first understanding the mutiny. The system is designed so that meaning emerges from the arrangement of fragments, not from any single fragment. This is exactly how a well-structured mystery novel works: the clues are not meaningful in isolation. They become meaningful through their structural relationship to one another.
Pope did not write sixty death scenes and hope the player would assemble them into a story. He built a system in which sixty death scenes, arranged according to specific rules of information access and logical dependency, would necessarily produce a coherent narrative if the player engaged with the system’s constraints. The story is in the structure. The writing is in service of the structure. This is the same relationship a good plot has to good prose: the prose fills in the structure, but the structure is what makes the prose matter.
What makes Obra Dinn feel different from a scripted mystery is that the player’s path through the information is not predetermined. You might identify the first mate before you understand what happened to the captain. You might spend an hour stuck on three deaths that click into place only after you revisit an earlier chapter with new eyes. The system produces a unique sequence of understanding for each player, but the understanding itself is structurally guaranteed. That guarantee is the design. That guarantee is the plot.
Citizen Sleeper: Dice as Narrative Engine
Citizen Sleeper takes a different approach to the same problem. Gareth Damian Martin built a tabletop-inspired system where you roll dice each cycle and assign them to actions. The dice are your capacity to act in the world. Low rolls constrain your choices. High rolls open possibilities. The narrative emerges from the intersection of what you want to do, what the dice allow, and what the game’s systems—hunger, energy, the ticking clock of your deteriorating synthetic body—force you to prioritize.
The game’s story is not independent of this system. It is produced by it. When you have to choose between spending a die on earning money for food or spending it on helping a friend, the narrative weight of that choice comes from the system, not from dialogue. The system makes scarcity real, and real scarcity produces decisions that feel like story. You are not reading about a character struggling to survive. You are making the decisions that constitute that struggle, within constraints the designer built to make the struggle unavoidable.
This is the thing scripted game narratives cannot do. A scripted story can show you a character making a hard choice. A systemic story makes you make the hard choice, and the hardness of it is not performed—it is structural. You feel it because the system has made it unavoidable, the way a plot structure in fiction makes the climax unavoidable through the accumulation of constraints the writer has been building since chapter one.
What Writers and Game Designers Share
Here is where I think the conversation between game design and narrative craft gets genuinely interesting, and where the parallel becomes more than metaphor. Writers who use structural tools—beat sheets, story frameworks, plot generators—are doing something mechanically similar to what these game designers are doing. They are building a system of constraints that will produce narrative-shaped outcomes. The system is not the story. The story is what happens when characters with desires encounter the constraints the system imposes. The writer’s job, like the game designer’s job, is to build the system well enough that the outcomes feel inevitable without feeling predetermined.
Reedsy’s Plot Generator is built around this same principle. You define a protagonist, a central conflict, stakes, and a structural framework—3-Act, Save the Cat, the Hero’s Journey—and the tool generates a plot shape from those inputs. What it produces is not the story but the system from which a story becomes possible. The constraints you define (genre, tone, ending type) shape what the structure can produce, the same way a game’s core mechanic shapes what kind of player behavior the game can generate. The tool’s own framing makes this explicit: it notes that stakes are what separate a plot from a mere sequence of events. That is a design principle, not just a writing tip. It is the same principle that makes Outer Wilds’ time loop produce narrative instead of repetition—there are stakes built into the system, and the system forces you to engage with them.
The parallel matters because it clarifies what structural tools actually do. Whether you reach for an AI plot generator or a structural template you found in a craft book, the tool is not writing your story. It is building the constraint system within which your story becomes inevitable. The story is still yours. The meaning is still yours. But the structure—the thing that makes the events cohere into something that feels like it had to happen this way—that is the system’s contribution. Game designers who build systemic narratives understand this intuitively. They do not write the story. They write the rules that make the story happen.
This is also why the conversation about authorship and tools is more complicated than the simple binary of human-versus-machine suggests. The Authors Guild has published AI Best Practices for Authors that grapple with exactly this tension: what does authorship mean when a creator builds a system that produces content rather than writing the content directly? The Guild’s position is that human voice, thinking, and creativity are what make a writer a writer, and that AI outputs are generic mashups rather than authored work. I think this is largely right, and I think it clarifies the game design parallel. When a designer builds the system that produces the narrative, they are the author—not of every moment, but of the conditions that make those moments meaningful. The player is a participant, not a co-author. The system is the medium, not the message. The same distinction applies to writers using structural tools: the tool generates the scaffold, but the writer authors the meaning that fills it. The craft problem is not whether you used a tool. It is whether you built a system capable of producing something worth experiencing.
Why This Matters for How We Read Games
If the best indie game narratives are plotted as systems rather than written as scripts, then the way we critique game narrative needs to change. Most game criticism still treats narrative as a text to be read: the dialogue, the lore, the cutscenes, the character arcs. This is like judging a novel by its prose without considering its plot structure. You can do it. But you will miss the thing that makes the narrative work.
When I evaluate a game’s narrative now, I ask different questions. What system produces the story? What constraints does that system impose? Do those constraints generate narrative-shaped outcomes, or do they just generate activity? Is the player’s path through the narrative structurally guaranteed but experientially unique, or is it scripted to seem unique? Does the system produce consequences that feel inevitable in retrospect, or does it produce arbitrary outcomes the designer tries to narrativize after the fact?
These questions separate the games doing narrative systemically from the games doing narrative cosmetically. A lot of AAA games have narrative systems that are cosmetic—dialogue choices that do not matter, branching paths that converge, moral systems that reduce to a meter. These are systems that look like they produce narrative but actually just produce the appearance of agency. The story was written. The system is decoration. The best indie games do the opposite: the story was not written, the system was built, and the story is what the system produces when a player engages with it honestly.
The Craft Problem We Share
The craft problem game designers and narrative writers share is not how to write good stories. It is how to build systems that produce outcomes neither the creator nor the audience can fully predict, but that feel inevitable in retrospect. That is a harder problem, and a more interesting one. It requires you to trust the system you have built. It requires you to accept that you cannot control every outcome. It requires you to design constraints that are tight enough to produce meaning and loose enough to produce surprise.
Outer Wilds trusts its system enough to give you no guidance. Obra Dinn trusts its system enough to give you incomplete information. Citizen Sleeper trusts its system enough to let dice determine what you can do. These are not games that are well-written. They are games that are well-plotted, in the deepest sense of that word—not in the sense of having a good story, but in the sense of having built a structure that makes good stories inevitable.
The next time you finish a game and feel like the story was something you lived through rather than something you were told, look at the system. Not the dialogue. Not the cutscenes. The rules. The constraints. The feedback loops. The economy of information and action. That is where the narrative was. Not written. Plotted. Built into the bones of the game like structure is built into the bones of a good novel—invisible, load-bearing, and absolutely essential to everything that happens above it.