Story, RPG and what a Story Generator is not

Story vs RPG: two kinds of generative play

Story Generators come in two main forms. Both perform an authored canon live, and both put choice in the player's hands. What differs is where the player stands.

A story generator places the player beside the story, closer to an author or director. You shape where the narrative goes, chapter by chapter, and watch the cast play it out. The pleasure is the pleasure of a great serial: what happens next, and knowing you decided it.

An RPG generator places the player inside the story, as a character. The world is narrated around you, and you decide what your character does next. The narration can take many forms: a narrator describing the scene, other characters speaking to you, or both at once. You run down the stairs and find a zombie at the bottom. Jane shouts that there is a gun in the drawer. What do you do? Sometimes the answer is a line of dialogue, more often it is an action, and the model narrates what happens as a result. The pleasure is the pleasure of being there: every decision is yours, and the world answers it.

Story Writers are a different thing

A close neighbour is often confused with Story Generators: the Story Writer. In a Story Writer the user writes. They write a passage and the AI writes the next, the two trading the pen back and forth with a character or a world as the shared material. It is co-authorship, a creative tool in the same family as a notebook or a writing room, and it draws people who would once have written fan fiction or joined a play-by-post forum.

A Story Generator is distinct. The canon is authored for you, the AI performs it, and your part is to choose and to act rather than to write the prose. One is a tool for making stories; the other is a medium for playing them. Both matter, and many people will enjoy both, but keeping the terms apart is what lets each be understood, in the same way that "video game" came to mean something distinct from the computer program that ran it.

Why neither needs a dungeon master's rulebook

Stats, dice rolls, hit points, skill checks, inventories and combat systems are classical mechanics. They came from tabletop role-playing games, where a dungeon master needed rules to decide what happened, and were carried into video games, where code needed numbers to decide it. They belong to the classical pillar, and they work well there.

Story Generators have a different core mechanic: input and output. The player acts, in their own words, and the model generates what happens: the narration, the consequence and the characters' replies. Then the player acts again. Both halves are the mechanic. The player's input is the move; the generated output is the world's answer. Everything else is secondary to that loop, and the whole of it is focused on the player.

That is why carrying the dungeon master's rulebook across is usually a mistake. Complex mechanics compete with the loop. Every turn the model spends tracking numbers and adjudicating rules is a turn it is not spending on what makes the medium worth playing: a scene that lands, a consequence that follows from what you actually did, a reply that could only have been written for you. Heavy systems also get in the way of the player's input. When an action has to be translated into a skill check before the world is allowed to respond, the player is no longer acting, they are filling in a form.

That does not mean anything goes. Structure still matters, but in a Story Generator it lives in the canon: what a character knows, what she wants, what she would never do, what must be earned before a secret is told. A guard who will not let you pass because of who he is makes a better obstacle than one who will not let you pass because you rolled a four. Light tracking, such as relationships, knowledge or what a character remembers about you, can help. The test is whether something makes the input and output better, or just gets between the player and the world.

What a Story Generator is not

The boundary matters because AI is now arriving in every corner of game development, and most of it does not create a new medium. It makes the existing one faster or richer. Three uses in particular are often confused with Story Generators:

1. AI NPCs inside a classical game. Giving a shopkeeper in an open-world game the ability to chat is a welcome improvement, and we have written about designing NPCs that listen. But if the game's story is still scripted, its quests still authored and its ending still fixed, the game remains a classical game with a more talkative cast. The generated dialogue is a layer on top, not the substance.
2. Code generation. Models that write gameplay code, shaders or tools change how games are built. They do not change what the player experiences as a medium. A game written with AI assistance is still a classical game.
3. Asset generation. Textures, 3D models, animation, voices and music made with AI are production techniques. A world full of generated trees is still a world whose story was written in advance.

A useful test: if you removed the model, would the work still exist? Remove the AI from a classical game that uses generated assets and NPC chatter, and you have the same game with fewer assets and quieter characters. Remove the model from a Story Generator and there is nothing left to play, only the canon waiting to be performed.

AI films and AI games are not the new medium

There is a great deal of hype around AI films and AI games. Almost none of it describes a generative experience. An AI film is a film: generated in production, then fixed, and watched the same way by everyone. An AI game is, nearly always, a classical game with AI used to build its code, its art or a few lines of its cast. Both are better described as AI in film and AI in games. They make two existing pillars faster and richer; they do not create a new one.

The clearer picture comes from the last great computing shift. Frontier models are becoming the operating systems of this era: the layer everything else runs on. The flood of productivity apps built as thin wrappers around a model's API are the equivalent of the early BASIC applications written for DOS and the first versions of Windows: useful, quick to make and easy to copy. World models are the game engines. And Story Generators are the games: the entertainment that the whole stack ultimately exists to run, and the reason most people will ever come to know it.