What a Dungeon Master Actually Does
A Dungeon Master is part referee, part storyteller, part rules encyclopedia. They describe the world, voice every NPC, adjudicate every roll, track every spell slot, and somehow keep the story moving while four players argue about whether you can grapple a dragon mid-flight. It is an enormous cognitive load — which is why finding a willing DM is one of the oldest problems in tabletop gaming.
When a DM is unavailable, campaigns die. Not from lack of interest, but from logistics. The DM moves across the country, burns out, or simply can't commit to a Tuesday night every two weeks indefinitely. The players are still there, dice in hand, with nowhere to go.
What "AI DM" Usually Means in Practice
The last few years have produced a wave of AI Dungeon Master tools. Most of them are, at their core, a large language model with a system prompt that says something like: You are a Dungeon Master running a D&D 5e campaign. The LLM improvises dialogue, describes scenes, and tries to remember what happened last session.
For pure storytelling — atmosphere, NPC personality, reactive narrative — this works surprisingly well. Modern LLMs are genuinely good at collaborative fiction. The trouble starts when rules enter the picture.
The Problem: LLMs Hallucinate Rules
Ask an LLM to adjudicate a grapple check and it might get it right. Ask it to track concentration spells across a five-round combat while managing action economy, bonus actions, and three different players' reaction triggers, and it will eventually invent rulings that don't exist. Not because it's trying to cheat you — because it's a pattern-matching system, not a rules engine.
Concrete examples: an LLM DM might let a Paladin smite after seeing the dice result (the rules require the decision before rolling). It might forget that a character's Bardic Inspiration die was spent two turns ago. It might apply the wrong damage type for a spell, miss that a condition grants advantage on a saving throw, or simply lose track of HP in a long combat. These aren't edge cases — they happen in ordinary play.
TableForge's Approach: Two Systems, One Table
TableForge separates the work that belongs to an LLM from the work that doesn't.
The AI narrator handles what LLMs are genuinely good at: describing environments, voicing NPCs, reacting to player choices, building atmosphere, and keeping the story coherent across sessions. It has persistent memory across your entire campaign — NPCs, locations, player decisions, plot threads, consequences. It follows your lead. There is no script.
The rules engine is programmatic code, not an LLM. Dice rolls, HP tracking, spell slot management, condition application, grapple checks, concentration saves, action economy — all of it is adjudicated by deterministic logic that runs the same way every time. The engine feeds its results to the narrator, which then describes what happened in prose. You never see the machinery, but it's there.
What This Means for Players
In practice, it means the game works. You don't have to fact-check the DM. When the rogue crits and you ask for the damage, the engine calculates it correctly and the narrator describes the result. When your concentration breaks, it breaks because the code says so, not because the LLM happened to remember.
It also means the experience holds together across sessions. The AI doesn't forget that you spared the bandit captain in session two, or that the merchant owes you a favor, or that the cult's ritual is tied to the next new moon. Campaign memory is persistent and comprehensive. You can play tonight and pick up next month and the world will still be waiting exactly as you left it.
The goal has always been a table that feels like a real campaign — not a demo, not a one-shot, not a chatbot pretending to roll dice. Try it free and see for yourself.