How does an AI game master work?
The short answer
An AI game master is not just a chatbot told to "run a fantasy game." A language model writes the prose, but a surrounding system decides what the model gets to see, checks what it claims happened, and keeps the record. The model is the storyteller. The system is the notebook, the rulebook and the editor.
That split matters because language models are good at atmosphere and dialogue and unreliable at bookkeeping. If you ask one to remember your hit points from memory every turn, the number slowly wanders. A well-built AI game master avoids that by never asking the model to be the source of truth.
What happens when you take a turn
Each turn starts with your input, such as "I try the cellar door." Before the model writes anything, the system assembles a prompt. Think of it as a briefing packet for the narrator, built fresh every turn from several sources:
- The stable facts of the world (who rules the town, how magic works, what a faction believes).
- What is true right now (your inventory, an NPC's mood, where you are standing).
- A short rolling summary of the story so far.
- The most recent turns, and any older memories that look relevant to what you just did.
Each of these sections has a limited budget, because sending the entire history every turn would be expensive and would not make the story better. So the system chooses what earns a place in the packet. Your own input is wrapped and labelled separately from everything else, so the model can tell your words apart from the world's instructions.
Why the model only proposes changes
After the narrator writes its reply, the story has to change in the record too. The cellar door opens, you pick up a lantern, the guard grows suspicious. In Fabulator's design the model never writes these changes directly. It proposes them, and the game engine validates them before anything is committed.
Validation is concrete. Changes to numbers are expressed as relative adjustments (lose five health) rather than absolute values, so they cannot drift. Values are clamped to sensible limits. A proposal that references an item you never owned, or tries to revive a character who died, gets rejected. If prose and record disagree, the turn can be regenerated instead of letting the contradiction stand.
This is why a good AI game master can say "you cannot lift that, it is too heavy for you" and mean it. The limit lives in tracked state, not in the model's mood.
How dice and rules fit in
Some groups want a story with no mechanics at all. Others want stats and rolls. Fabulator handles the second case with pluggable rulesets, which are compiled to WebAssembly and run in a sandbox. A ruleset is deliberately starved of power: it cannot query the database or reach the network on its own. It receives the context it needs from the engine, and if it needs a random roll it asks the host to roll for it. The model narrates the outcome, but it does not get to decide whether the sword hit.
How the story keeps moving
Left alone, a narrator tends to wait for you to act. Fabulator separates the local narrator from a Director, which tracks the larger shape of the plot: quest milestones, faction pressure, threats that grow while you are busy elsewhere. When a plot event comes due, it is handed to the narrator as a directive, and the design calls for the system to check that the prose actually uses it. So a courier can burst into the tavern even if you typed "I keep drinking my ale."
Why it sometimes still forgets
Memory in this kind of system is layered. Recent turns are kept close to verbatim. Older material is folded into a summary, and events judged significant are stored individually so they can be recalled later. Small details from long ago may only survive as a line in a summary. That is a trade-off made on purpose, not a sign that the whole thing is broken.
The practical difference between a weak AI game master and a strong one is mostly about which layer is responsible for which fact. Facts that must stay fixed belong in the world record. Numbers belong in tracked state. Only the shape of what happened belongs in decaying memory. When a slip happens, it usually means a fact was living in the wrong layer.
Players also get a way to look at this machinery. In Fabulator you can inspect what the game currently knows about your story and correct it, so a wrong detail is something you can fix rather than argue with.
Where to see it for yourself
If you would rather watch the mechanism work than read about it, Fabulator lets you browse published World Seeds, which are ready-made settings you can start a campaign in. Pick one that sounds interesting, play a few turns, and try something the setting would not expect. How the world responds, and whether it stays consistent when you push on it, will tell you more than any description could. There is no pressure to commit to anything: the Discover page is there when you want to look around.