Why AI Game Masters Forget Your Campaign (and How DungeonsDeep.ai Doesn't)
Your party killed the king in session two. He had a coronation room, a personal guard, and a habit of feeding informants to the dogs. By session twenty, your AI Game Master welcomes you to the throne room and the king greets you warmly. Nobody mentions the murder. Nobody remembers it. The campaign you spent forty hours building has quietly forgotten itself.
At a quick glance, that is the AI memory problem. It is the single biggest reason long campaigns fall apart on AI tabletop platforms, and it is the problem we obsessed over more than any other when we built DungeonsDeep.ai. We didn't want a memory system that worked most of the time. We wanted one that did not forget. Period.
Bulletproof memory is non-negotiable for us, and it has to be, because the people building DungeonsDeep are long term tabletop RPG and D&D players ourselves. We have sat at real tables for campaigns that stretched across years. We know how much weight a single throwaway line from session three can carry when it comes back around in session forty. We know what it feels like when a human Game Master remembers the name of the innkeeper's daughter, the favor you owed a thief two cities ago, the scar your fighter took during a botched ambush in act one. That is the bar. Any AI Game Master that forgets those details is not playing the same game we are. So we refused to ship a memory system that couldn't keep up with the kind of campaigns we run at our own tables.
This post is the long version of why memory is so hard for every other AI Game Master in the category, how each major platform tries to solve it, where each one fails, and how we built ours differently. If you've ever lost a campaign to an AI that suddenly stopped knowing who your character was, this is for you.
Last updated June 23, 2026.
Memory Is the Whole Game
Every other feature in an AI tabletop sits on top of memory. Combat doesn't matter if the AI forgets your hit points. Worldbuilding doesn't matter if the AI forgets the world. Quests don't matter if the AI forgets why you're on them. A persistent party, a meaningful choice, a recurring NPC, a long arc, an emotional payoff, all of it depends on the AI remembering what came before. When memory fails, the entire game collapses into a series of scenes that don't talk to each other.
This is why memory is the most cited complaint across every AI tabletop community we've looked at. It shows up on the AI Dungeon subreddit, on AI Realm's forums, in product reviews, in Hacker News threads about LLM tabletops, and on our own subreddit too. Players use different words for it, "object permanence," "Franz forgot," "the AI keeps treating me like a stranger," "the goldfish problem," but they're all describing the same thing. The AI Game Master forgot the campaign.
A good memory system is the foundation everything else stacks on. A bad one, no matter how beautiful the prose or how clever the combat, eats the campaign from underneath.
How the Other AI Game Masters Handle Memory
Every platform in the AI tabletop space has a memory system. They've all read the same forum threads we have. The question is how each one tries to solve the problem, and where each one quietly fails.
AI Dungeon: The Context Window Trim
AI Dungeon uses a context window. The model reads back a fixed number of tokens of your story at every turn, and according to their own documentation, the oldest story text gets trimmed when the context limit is exceeded. To fight back, the platform layers on extra systems. Story Cards are keyword triggered notes. Plot Essentials are persistent instructions. The Memory Bank auto stores important details. All of these are attempts to slow the inevitable.
The inevitable still arrives. The DreamGen review of AI Dungeon, based on over twelve hours of testing, found that even paid models with expanded context missed established plot details when the story grew long enough. AI Dungeon's own memory documentation acknowledges the limitation directly, framing the entire Memory Bank feature as a workaround for the underlying truth that the AI cannot hold the full story in working memory. The longer your campaign, the more aggressive the trimming, the more details slip.
The cost lands on the player. To survive a long campaign, AI Dungeon players curate Story Cards, refine Plot Essentials, and check the Memory Bank between sessions. It is real work, and the AI still forgets.
AI Realm: The Notes File You Maintain
AI Realm goes further in the opposite direction. Instead of asking the AI to remember, they ask the player to do it. Their own Player's Guide states the model in plain language: "if it's not in your Notes, the AI will eventually forget it." The recommended cadence is to spend around ten minutes every five to ten sessions cleaning up Notes, deleting outdated sections, and reorganizing.
The V2 Guide goes on to admit the AI's memory "is not infallible," that it sometimes gets details like Armor Class wrong, and that it can address players by a different character's nickname mid session. The guide recommends keeping a separate character record outside the chat, "because it's more than likely to forget some things about your character during the journey." That's the platform telling you, in writing, to maintain a parallel record because their own system can't be trusted to hold one.
This is a memory system in name only. The actual memory lives in a player maintained text file. The AI consults it when it remembers to. The player consults it when the AI fails. It works for short campaigns, and players have made it work for long ones with enough effort. But the effort is the point. The platform openly admits the AI alone won't hold your campaign.
We cover AI Realm's context limits and Notes workflow in more detail in our honest AI Realm review.Friends and Fables: The Retrieval Gamble
Friends and Fables goes more sophisticated. Their AI Game Master, Franz, runs on a retrieval based memory model. Their context size documentation explains that Franz makes multiple model calls enriched with campaign context including characters, locations, items, and campaign state, with model context windows that "vary but are generally 128k or larger." Their memories help article explains the actual mechanism. Memories are created automatically every five turns and searched into a working context, with this caveat in their own words: "not all memories are always included because of cost, speed, and performance tradeoffs."
That's the failure mode in plain English. The system has the memory. The system might not hand it to the AI this turn. Whether the memory shows up depends on retrieval, on cost budgets, on speed budgets, and on what tier the player is on, because higher subscription tiers get more mention slots per message and larger custom block character limits per their pricing page. You pay more to retrieve more.
The DreamGen review of Friends and Fables documents users reporting Franz memory issues in extended campaigns, especially on lower tiers. This isn't a knock on Franz. It's the math of retrieval. When the system has a thousand memories and can only surface twenty into context, the right one is sometimes missing. That's the gamble baked into the architecture.
ChatGPT, Claude, Grok, and Gemini: The Permanent Goldfish
Then there's the player running a campaign through ChatGPT, Claude, Grok, or Gemini with no purpose built platform underneath. This is the rawest form of the memory problem. ChatGPT, Claude, Grok, and Gemini are general purpose chat tools, not tabletop platforms. Each one has a context window, and that's it. No retrieval, no campaign state, no auto generated notes, just the conversation so far. When the conversation hits the context limit, the beginning rolls off.
A popular Reddit thread on r/Solo_Roleplaying captures the failure mode. Players report continuity breaking down after a few thousand words. The same pattern shows up on D&D Beyond's ChatGPT thread: useful for one off scenes and prep, but quickly forgets a long campaign without aggressive human curation. There's no magic here. The model is doing its job. The architecture underneath just can't hold a tabletop session.
Memory as Recall vs Memory as Record
Here's the framing that unlocks the difference between every system above and what we built.
Every other AI Game Master treats memory as recall. The campaign happened. The system is trying to remember what happened. Recall systems search, summarize, and retrieve. They guess what's relevant this turn and hand a slice of the past to the AI. They all carry the same hidden failure mode: the right detail has to be remembered correctly, located in time, and surfaced into context, every turn, forever. Miss any of those three and the memory is gone, even if the data is technically still in the system.
We built DungeonsDeep.ai around memory as record. The campaign isn't a story the AI is trying to recall. The campaign is the system. The state of the world is the source of truth. NPC relationships, party choices, item inventories, plot threads, the consequences of every decision, all of it lives in the campaign system as the world itself, not as transcript the AI has to flip through. The AI Game Master doesn't recall the state. The state hands itself to the AI.
The shift sounds small. In practice it changes everything. Recall systems can lose the memory. Record systems don't have a memory to lose, because the campaign is the memory. The king who died in session two is dead in session forty because the world is recording him as dead, not because the AI happened to remember he died. The goblin head you mounted above the tavern fireplace is still there when you walk back in, because the tavern remembers what's on the wall.
"Great job remembering the nuances of things we've done in past campaigns. We mounted the head of a goblin lieutenant above the fireplace, and when we returned to the game in a new session and made our way back to the tavern, the AI Game Master specifically called out the head mounted above the mantle. Loved the personal touch. NPCs seem to have a memory of who we are and have the correct tone of conversation that starts back up with them later in the campaign."
DungeonsDeep.ai beta tester
How DungeonsDeep.ai Built Bulletproof Memory
The record approach takes more work to build than a recall approach. You have to design the world as a structured place that can be updated, queried, and persisted across sessions. Three principles guided how we made that practical.
1. The Campaign Is the System, Not the Conversation
On every other platform, the conversation is the primary artifact. Memory is whatever the conversation can carry. On DungeonsDeep.ai, the campaign is the primary artifact. The conversation is one window into it. Character state, relationships, world events, party decisions, and consequences live in the campaign system itself. The AI Game Master sees the campaign state when it narrates, and the narration updates the campaign state in return. Nothing important lives only in transcript text.
2. The Player Doesn't Maintain Anything
No Notes file. No Story Cards. No Memory Bank to curate. No mention budget per tier. The player plays. The platform tracks the world. If you mounted the goblin head above the fireplace, the platform knows. If you killed the king, the platform knows. If the merchant you helped in session four remembers your face in session forty, that's because the merchant remembers, not because you reminded the AI to remember.
This matters because every player maintained memory system is a memory system that fails when the player gets tired. We didn't want the longevity of your campaign to depend on whether you felt like cleaning up Notes this week.
3. Memory Survives Session Boundaries
Memory on DungeonsDeep.ai persists across sessions, across model swaps, across pauses, across platform updates. Session 1 to session 50, the same campaign state. Take a month off, come back, the world is exactly where you left it. The state isn't reconstructed from chat history when you log back in. It was never lost.
This is the part recall systems can't match. A retrieval based system rebuilds context every turn. A context window system holds context only as long as the window does. Both are vulnerable to anything that disrupts continuity. A record system isn't, because the record is the source of truth and the conversation is a view of it.
Tested Against the Bar of a Real Table
The memory system on DungeonsDeep.ai has been hammered on by our own development team before any beta tester ever saw it. Many people on our team have spent years sitting at real tabletop and D&D tables, including campaigns that stretched well past their first anniversary and a few that are still going. We have lost characters across multi year arcs. We have watched a side joke from session two turn into a major plot beat in session sixty. We know exactly how much a real Game Master holds in their head from week to week, and we know what shape the disappointment takes when that thread gets dropped.
So when we built the campaign system, we tested it against that bar, not against the bar of an AI demo. We ran long running campaigns internally. We pushed past the point where context windows fail. We rolled back, paused for weeks, resumed, swapped characters, brought old NPCs back into play, and watched for any moment where the world stopped remembering itself. We knew that for any AI Game Master to serve the tabletop community well, the memory had to be as accurate as a real gameplay table. Anything less is a tech demo with a fantasy skin on it.
What This Feels Like at the Table
The architecture is the why. The play experience is what actually matters, and the play experience is what beta testers keep flagging. Memory shows up at the table as the small details that make a campaign feel like a place rather than a series of scenes.
"The DM on your game has shockingly good memory."
DungeonsDeep.ai beta tester
"This game is delightful. The little things it remembers, the way it characterizes the dudes you make, it's all very charming."
DungeonsDeep.ai beta tester
"So I have tried Dungeons Deep, Friends and Fables, and MacerAI. DD is the one that impressed me the most. The other options just made me realize DD spoiled me."
DungeonsDeep.ai beta tester
That last one is the pattern we hear most often from players who came over from another platform. Other systems train you to lower your expectations. You start curating Notes. You start re minding the AI who your character is. You start accepting that the AI will lose the thread because that's what AI Game Masters do. Then you play a campaign where the AI doesn't lose the thread and the bar resets.
The Honest Tradeoffs
Building memory as record instead of memory as recall isn't free. We made a set of choices to get here, and a few of them show up as tradeoffs on the product roadmap right now.
- We're in closed beta. A record system takes longer to build than a retrieval one, and we're still in the controlled release window. Sign up is free and we're bringing players in regularly.
- Image generation is on the roadmap. We built the campaign system and the rules engine first because those are the foundation memory sits on. In game image generation is coming, not shipped.
- Multiplayer is coming soon. Friends and Fables ladders up to six players today and that's a real lead. Multiplayer on DungeonsDeep.ai is on the roadmap and we're building it on top of the same memory foundation, which means multiplayer sessions will inherit the same persistent state.
These are real and worth knowing about. They are also why the memory system works the way it does. We prioritized the foundation. The rest gets built on a platform that already holds the campaign.
How AI Memory Architectures Compare
The at a glance breakdown:
| Platform | Memory model | Player burden | Failure mode |
|---|---|---|---|
| AI Dungeon | Context window plus Memory Bank | Curate Story Cards, Plot Essentials | Oldest text trimmed |
| AI Realm | Player maintained Notes | 10 min every 5 to 10 sessions | "If it's not in Notes, AI forgets" |
| Friends and Fables | Retrieval based memory | Tier dependent mention budgets | "Not all memories always included" |
| ChatGPT, Claude, Grok, Gemini as GM | Pure context window | Manual everything | Catastrophic forgetting |
| DungeonsDeep.ai | Platform managed campaign state | None | The world remembers itself |
Frequently Asked Questions
Why does my AI GM or DM keep forgetting things?
Because most AI Game Masters store the campaign as transcript and read it back into a context window every turn. As the campaign grows, the transcript outgrows the window, the oldest material gets trimmed, and retrieval systems start surfacing the wrong details. Forgetting is not a bug your AI Game Master will eventually patch. On most platforms, it is how the architecture works.
What is an AI Game Master with good memory?
One where you do not have to maintain a notes file, prune a memory bank, or remind the narrator who your party is. A good AI Game Master memory system tracks character state, NPCs, locations, inventories, and plot threads on the platform itself, persists those across sessions, and surfaces them automatically when they become relevant. DungeonsDeep.ai was built around exactly this requirement.
Which AI Game Master has the best memory?
Among purpose built AI Game Master platforms, DungeonsDeep.ai is the strongest fit for players who want a campaign memory that holds up across long sessions without manual curation. Friends and Fables and AI Dungeon both have sophisticated memory layers, but their own documentation acknowledges retrieval and context window limitations. AI Realm explicitly relies on a player maintained Notes file. ChatGPT, Claude, Grok, and Gemini have no campaign memory beyond the context window.
Why does ChatGPT forget my D&D or tabletop RPG campaign?
ChatGPT runs on a context window. Every turn, it reads back as much of the conversation as fits, then truncates the rest. When your campaign grows past that limit, ChatGPT starts losing the oldest material first. ChatGPT also does not know it is running a campaign, so it does not separately track NPCs, inventory, or plot threads outside of what is in the conversation. The same applies to Claude, Grok, and Gemini.
Can ChatGPT remember a long D&D campaign?
Short ones, yes. Long ones, no. ChatGPT, Claude, Grok, and Gemini all share the same underlying constraint: a context window that fills up. Without a campaign system tracking state on the side, the player ends up summarizing, re uploading notes, and reminding the AI of established details. Most long campaigns on a general chatbot eventually fall apart around the context limit.
How do I stop my AI Dungeon Master from forgetting?
On most platforms, you can't fully stop it, you can only delay it. The available tactics are the ones the platforms recommend themselves: keep Story Cards updated on AI Dungeon, maintain a Notes file on AI Realm, watch your mention budget on Friends and Fables. The only way to actually stop forgetting is to switch to a platform where memory is managed at the campaign layer instead of in the chat transcript. DungeonsDeep.ai was designed around that approach so the player isn't doing memory maintenance between sessions.
Does the AI remember between sessions?
On DungeonsDeep.ai, yes. The campaign state persists across sessions, pauses, and model updates. You can log out, come back a month later, and the world is in the exact state you left it: same NPC relationships, same inventory, same plot threads in motion. On context window based platforms like ChatGPT, the AI's recall between sessions depends on what fits in the new conversation, which means a fresh session often loses the earlier details.
How long can an AI remember a tabletop RPG campaign?
On a context window system, until the window fills, typically somewhere between a few thousand and a few hundred thousand words depending on the model. On a retrieval system, in theory forever, but in practice limited by which memories get surfaced into context on any given turn. On a record based system like DungeonsDeep.ai, the campaign state is the source of truth and doesn't decay with length. We've tested long running campaigns specifically to validate that.
Does DungeonsDeep.ai remember NPCs across the campaign?
Yes. NPCs live in the campaign system, not in chat transcript. The merchant you helped in session four still remembers your face in session forty. The villain you let escape in act one is still loose and still has their grudge. NPC relationships, dispositions, and history are tracked on the platform, so the AI Game Master narrates them consistently every time they return to the table.
Does the AI Game Master remember my character?
Yes. Your character's class, race, backstory, choices, relationships, and inventory live in the campaign system rather than in transcript. The AI Game Master sees them every turn, which means you don't have to re explain who your character is, what they're carrying, or what they've done. This is the issue that beta testers coming from other platforms tend to flag first, since they're used to reminding the AI of basic character details.
What is the best AI for long D&D campaigns?
For long running tabletop RPG campaigns with real continuity, DungeonsDeep.ai is built specifically for the use case. It was designed by long term tabletop and D&D players to hold up to multi session play without the player maintaining notes, retrieval budgets, or memory banks. Other purpose built platforms work for shorter or more curated campaigns. A general chatbot like ChatGPT, Claude, Grok, or Gemini is fine for one shots and prep but struggles past a few sessions.
What is platform managed campaign memory?
Platform managed memory means the campaign state lives in the platform's systems rather than in the player's notes or in a context window. Character details, NPC relationships, party choices, and world events are tracked by the platform automatically. The player doesn't configure Story Cards, doesn't maintain a Notes file, doesn't worry about retrieval, and doesn't restart the campaign because the AI forgot.
How does DungeonsDeep.ai's memory work?
DungeonsDeep.ai uses memory as record. Character state, NPC relationships, item inventories, plot threads, and world events live in the campaign system itself rather than in chat transcript. The AI Game Master sees the campaign state when it narrates and updates that state in return. Memory persists across sessions and doesn't depend on retrieval or player maintained notes.
Does AI memory matter for long campaigns?
It is the single most important factor for whether a long campaign holds together. Combat, worldbuilding, dialogue, and quest design all collapse if the AI forgets what came before. A short scenario can survive on any AI Game Master. A campaign that lasts months only survives if the memory system is built to last that long.
Start Adventuring
If you've ever lost a campaign to an AI that suddenly stopped knowing who your character was, that was the recall problem. The campaign was still there, the AI just couldn't reach it. We built DungeonsDeep.ai to solve that problem at the foundation, so the campaign you spend forty hours building is the campaign that's still there at hour two hundred. Sign up for the closed beta and see what a campaign feels like when nothing gets forgotten.
If you'd rather hang out with the community first, find us on Discord or the DungeonsDeepAI subreddit. We're real players too, and we're always happy to talk shop.
This work includes material from the System Reference Document 5.2 (“SRD 5.2”) by Wizards of the Coast LLC, available at https://www.dndbeyond.com/srd. The SRD 5.2 is licensed under the Creative Commons Attribution 4.0 International License, available at https://creativecommons.org/licenses/by/4.0/legalcode.