My AI DM Got Something Wrong. Now What?

My AI DM Got Something Wrong. Now What?

It happens. The DM forgets a spell slot you spent, revives an NPC you buried, or insists you are still poisoned three sessions after the poison ended.

Here is why it happens, what you can sort out yourself, and what should be handled for you.

Why AI DMs Drift

Three different failures get called "the AI forgot", and they need different answers.

• Context loss. A chatbot with no memory system only knows the recent conversation. Session 12 is gone. This is the most common failure and the hardest to fix from your side.
• State drift. The story says one thing and the underlying record says another. Your sheet shows the slot spent, the narration says otherwise.
• Rules error. The mechanic was applied incorrectly. Advantage that did not apply, a condition that never landed, damage resistance ignored.

What You Can Fix Yourself

• Restate the fact plainly. "I spent my second level slot on Misty Step last turn." A DM working from a real record will check it. A DM working from vibes will agree with you regardless, which is worth knowing.
• Ask what it thinks the state is. "What are my remaining spell slots?" If the answer is wrong, you have found state drift rather than a narration slip.
• Ask which rule it applied. A system that enforces rules can name the one it used. A system that improvises will produce a plausible-sounding rule that does not exist.

That last one is the most useful diagnostic in this article. Ask any AI DM to justify a ruling. The answer tells you which kind of tool you are using.

What You Should Not Have To Fix Yourself

Talking a Dungeon Master out of a mistake is not gameplay. It is customer support with elves.

And it does not reliably work. Asking an AI to correct itself in conversation usually produces agreement, not correction. It will say you are right, apologise, and carry on with the same broken underlying state, because the conversation and the record are two different things. You have fixed the narration and not the bug.

What Actually Fixes It

Two things have to be true.

• The game needs a real record, separate from the conversation. Character state, NPC state, quest state, world state, stored and queryable rather than inferred from chat history. We wrote about why this is the hard part in persistent world state.
• Something needs to be able to repair that record. A record you cannot correct is only a more precise way to be wrong.

How We Handle It

The Endlessness keeps the record separately from the story, and ships a repair agent called the Fixer to correct it. There is a wrench beside the send button.

You describe what went wrong. The Fixer reads what actually happened in your campaign, decides whether something is genuinely broken, repairs it, and tells you what it changed.

Three properties matter more than the repair itself:

• It cannot tell you a story. No narrative tools, no dice, no combat. It cannot be talked into giving you a magic sword, because handing out swords is not a thing it can do.
• Every repair is independently reviewed and rolled back if it does not hold up.
• It has its own daily credits, so telling us something broke never costs you play. 10 a day on Free, 40 on Legend.

What This Does Not Solve

An AI Dungeon Master can still write a dull scene, miss the tone you were going for, or hand you an NPC with the personality of a paving slab. The Fixer repairs broken state. It has no opinion about whether the story was good. For that, tell the DM what you want and steer, exactly as you would at a table.

The Endlessness and Getting It Wrong

Our AI Dungeon Master enforces the rules from a real record rather than from memory of the chat, and hands you a repair agent for the times it still slips.

For related reads, our the Fixer, persistent world state, and can AI be a good DM posts cover more.

Final Takeaway

Every AI DM makes mistakes. The question worth asking before you commit a campaign to one is what happens next. The Endlessness gives you a wrench instead of an apology.