Keeping a long story consistent across multiple AI chat sessions is genuinely painful. You start a rich worldbuilding thread in one conversation, switch models or hit a context limit, and suddenly your AI has amnesia about everything that happened before page two. It’s the kind of friction that kills creative momentum fast.
This Reddit contributor built something refreshingly lo-fi to fix it. The project is called WORLDBREAKER1.0, and at its core it’s a structured folder of plain .txt files that acts as a portable memory layer for longform interactive fiction and worldbuilding. Think Dungeons & Dragons campaigns powered by LLMs, but with actual continuity between sessions.
The creator is upfront about it being early-stage and rough around the edges, but the concept is solid. Instead of relying on any single model’s built-in memory (which varies wildly and often just vanishes), you keep your world state in simple text files that any model can read.
How It Actually Works
The system breaks down into a few key components:
- Spine: rules and workflow files that define how the world operates and how the AI should behave within it
- Ledger: an editable snapshot of the current world state, characters, and context that you can update as the story evolves
- Append-only history: a running log that captures what happened, so nothing gets lost or contradicted
- Structured saves: a “camp” flow that lets you pause and resume sessions cleanly without losing the thread
The beauty here is the portability. Because everything lives in .txt files, you’re not locked into ChatGPT, Claude, or any specific client. Swap models mid-campaign if you want. The memory travels with you.
Why This Approach Is Worth Watching
Most people trying to solve the AI memory problem reach for vector databases, RAG pipelines, or complex tooling. This Redditor went the opposite direction: flat files, human-readable, zero dependencies. There’s something genuinely practical about that.
If you’ve experimented with tools like SillyTavern or other AI roleplay frontends, WORLDBREAKER takes a different approach by keeping the memory infrastructure completely model-agnostic and transparent. You can open any file in Notepad and see exactly what your AI “knows” about your world.
The minimal file set also means there’s almost no setup friction. Clone the repo, drop in your world files, and point your preferred model at them.
What to Keep in Mind
The creator is very honest about where this stands. A few things worth noting:
- It’s early. The project describes itself as “pretty basic prompt stuff” at this stage
- The broader memory infrastructure behind it isn’t public yet
- The save/camp flow is functional but still being refined
- With very long campaigns, those append-only history files could grow past context window limits, and there’s no summarization or compression layer mentioned yet
The post’s author is actively asking for feedback on file structure, naming conventions, and whether the save/resume flow feels natural. That kind of openness to critique usually means the project will improve quickly.
🧭 Getting Started
- Grab the repo from GitHub (linked in the original Reddit post)
- Review the Spine files to understand the rules framework
- Set up your Ledger with initial world state
- Point your preferred LLM at the folder and start a session
- Use the camp/save flow when you need to pause or switch models
💡 Pro Tip
If you’re running campaigns across different models, keep your Ledger updates tight and factual. The less ambiguity in your world state files, the less room any model has to hallucinate details that contradict your established canon.
For anyone building interactive fiction with AI or just trying to keep a novel-length project coherent across sessions, this is worth bookmarking. The repo and full discussion are available in the original Reddit thread on r/PromptEngineering: check it out and drop the creator some feedback while the project is still taking shape.
WORLDBREAKER1.0 text game style interaction and story building that can (hopefully someday) be used with any model for a significant memory generation infrastructure.
by u/_klikbait in PromptEngineering