Narrative design is the part of a game that most small teams either skip or overbuild, and both failures look the same from the outside: players finish and remember nothing.
The fix is not more writing. It is deciding which parts of the story your systems carry, and refusing to pay for the parts players never notice.
Story, Narrative, And Lore Are Three Different Jobs
Story is what happens. The hero leaves home, finds a threat, wins or loses.
Narrative is how the player experiences it, through cutscenes, dialogue, environment, and their own actions.
Lore is why the world is the way it is, the ancient war, the founding of the kingdom, the rules of the magic.
The common mistake is overinvesting in lore. A wiki of world history gives a player no reason to care in the present tense. Soulsborne games get away with deep fragmented lore because the moment to moment play already has you, and the lore rewards you afterwards. For a browser game, a clear character with a clear goal facing a clear obstacle beats twenty pages of mythology every time.
What Players Actually Notice About Choice
True branching is exponential. If every choice creates two paths, five choices is 32 unique routes, each needing writing, scripting, testing, and possibly voice. Almost nobody can pay for that, which is why most choice systems converge back to the same beats.
That is fine, because players are not auditing the branch count. They notice three things:
Did the game acknowledge my choice immediately.
Does this character treat me differently now.
Did the choice pay off later, in a way that felt earned or interestingly challenged.
Deliver those three and a mostly linear story feels deeply responsive. Skip any of them and genuinely complex branching still feels hollow and mechanical. The Walking Dead built its reputation on exactly this, with a critical path that barely moved.
Narrative Models And What They Cost
Linear is the cheapest to produce and the easiest to write well, because it is closest to traditional storytelling. The risk is a story that feels bolted onto the gameplay.
Branching buys replayability and investment, and the cost scales with the number of branches. The trap is uneven quality, since one thin branch makes players distrust the whole system.
Emergent narrative comes from systems rather than authored content. It needs the least writing and the most game design, because the systems have to generate events that are varied, consequential, and readable enough for players to turn into stories.
Hub and spoke keeps a linear spine with optional detours, which is usually the sane middle for a small team.
For an indie or web project, the practical shape is narrow branching: mostly linear, two or three real variation points, each visible and consequential inside the scope you can actually finish.
The Takeaway
Write the story engine first, then add lore as decoration. Spend the branching budget on acknowledgement, reaction, and payoff rather than on paths nobody will replay to find.
The full guide, covering agency, environmental storytelling, dialogue, and how AI is changing narrative work, is here: https://www.abratabia.com/game-narrative/
Top comments (0)