The third time I started the same campaign, I knew the problem was not discipline. I had interest and time, and notes that were actually pretty good. What I did not have was a way to pick up where I had actually left off quickly and easily.

This is the experience a lot of solo players share and almost nobody names excplicitly, either in rules or marketing. They call it motivation, or burnout, or the wrong gaming or rules system. None of those can really explain it though. The real problem is structural in how solo play handles the weight of campaign history and what systems exist (or don't) that can solve for it.

The context rebuild tax

Every session in a solo campaign begins with a sort of investment tax. You sit down, open your notes, and spend ten to twenty minutes trying to reconstruct where you were. Who was this character? What was she working toward? What did that NPC say the last time they met? Why does this location matter?

Good notes help and matter. That's why a lot of people are taking to Google Docs, Obsidian, Notion, Evernote... the list goes on. I have tried long-form notes, structured character sheets pasted at the top of every page/mission, and templates I made myself fill out before I was allowed to start playing. Each one reduced the rebuild time a little but none of them completely eliminated it.

The problem is that usually the parts that mattered most are not the parts that get written down. Like the specific context of a decision, the realization of a consequence's real impact, or the particular way a relationship evolved as opposed to its current state. These things live in your head while the campaign is active and drain away as time goes on. The notes capture the facts but they don't always capture the context behind them.

Why session four can be the wall

Sessions one through three are usually easy since the world is new, the character is fresh, and every choice is the first of its kind. The context rebuild is small because there is not much history yet.

But by session four and beyond the campaign and the story have history. That history is supposed to be what makes decisions meaningful. The choice in session four has weight because of what happened in sessions one through three. The stakes are higher and the consequences feel more real.

That is also when the world history and context rebuild is heaviest. The session where the past should matter most is the one where it is hardest to quickly summarize and access. You sit down, you rebuild for twenty minutes, you get forty minutes of play, and you stop mid-scene with nothing resolved. The next session starts at a half-resolved point. Then the rebuild takes a little longer, and the motivation drops a little. By session six you are thinking about a fresh start.

The DIY stack and its risks

The common solution is to assemble a stack: a chat tool for narrative, Mythic GME or another ruleset for oracle, a notebook/tool for state. Each piece is good at its job individually, but the problem is that none of them know what the others are doing.

The chat tool has no idea what Mythic rolled last week and the notebook does not update itself when the story moves forward. And when Mythic generates the next complication, it has no memory of your character's history at all. You are the integration layer, and maintaining that integration is a lot of work on top of what you are trying to do - actually play the game!

That job is not creative, but rather administrative, and it is the job that ends up hurting the campaign. At some point the overhead outweighs the creative return and it becomes more attractive to start over with a clean slate.

The clean slate feels like relief. And truth be told, it oftentimes is. But three sessions later the history starts to accumulate again, and the same problem returns.

It is structural, not personal

I spent a long time believing I just needed better notes and tools, a better template, a better system, more discipline about filling it out consistently.

None of that was ever going to fix it. A workaround for missing state is still a workaround. What the campaign actually needs is a system that holds its own history, one that knows what happened in session one when you sit down for session ten, without asking you to reconstruct it from a document.

That is a structural requirement. You can paper over it with better notes and you are just compensating for an absent foundation. Get the notes complex enough to actually hold the campaign's history, and they get too complex to reference quickly, so the rebuild problem comes back in a different shape.

---

This is one of the many problems Wanderhold was built to solve. Not just 'use AI' to solve it all. Not the AI narrative or the dice mechanics. What a good engine and data storage mechanism can do is solve the state problem. The engine holds your campaign history so the session can start from where you actually left off.

If you want to see what that looks like in practice, you can start a free campaign at playwanderhold.com/create and pick it back up a week later without rebuilding anything yourself.