Solo RPG Campaign Journal: NPCs, Factions and Quests

Every solo campaign reaches the night when you sit down to play and cannot remember the innkeeper’s name. A solo RPG campaign journal is the cure: not a diary of everything that happened, but a small set of records that tell you who matters, what they want, what is coming and what you have promised. This guide sets out what to keep, how to keep it short, and how to pick a story back up after weeks away.

Why solo campaigns drift

At a group table, memory is shared: someone recalls the fence’s name, someone else the promise you made her. Alone, you are the whole table, and you invented the fence on the spot three sessions ago. Solo campaigns drift for a handful of reasons:

Improvised people. You create NPCs in the moment and forget them as quickly.
Threads multiply. Every oracle answer can open a new question, and few close.
Breaks. A month away, and the details blur.
Contradictions. Without a record the world quietly rewrites itself: a dead man walks, a friendly village turns cold for no reason.

What should a solo RPG campaign journal include?

Six things, each kept short:

A codex of people, and how they connect.
Factions, and your standing with each.
A quest log broken into steps.
A timeline of what is coming, with deadlines.
Three lists: threats, promises and facts.
Summaries of the story so far.

Paper, a text file or a notebook app will all do. Solo campaign tracking fails less often for want of tools than for want of habits.

How do you keep a solo campaign consistent?

Write things down when they become true, read them before you play, and trust the record over your memory. When a scene would contradict the journal, either the scene changes or the journal does, on purpose. The rest of this guide is what to write.

A codex of people: NPCs and how they connect

How do you keep track of NPCs in a solo RPG?

Give each person one entry of a few lines:

Name and role: who they are to the story.
Where they were last seen, and when.
Status: alive, missing, dead or unknown.
What they want, as far as your hero knows.
What lies between you: a debt, a grudge, a favour.
One detail that makes them themselves.

Then record the ties between them, not only their ties to you: who serves, fears or owes whom. Drawn as a web, the ties show how news travels; insult one person and you know who else will hear of it.

The sample adventure’s codex shows the shape. Father Cern, the village priest, is missing, last seen entering the crypt by moonlight. Brenna Tallowick keeps the Black Pear and knows everyone in Valdrath. Morath of the Hollow holds a favour you owe her and has not yet named it. The pale boy appears at the crypt’s edge at twilight and casts no shadow. Four entries, and each one is a reason to act.

Solo players will know the idea from the Mythic Game Master Emulator by Word Mill Games, whose threads and characters lists hold the campaign’s open questions and its people, and give its random events something to draw on. A codex is the characters list with room for each entry to grow.

Factions and your standing with them

How do you track factions and reputation?

A faction tracker needs only four columns:

Who they are, and what they want.
What they know about you.
Your standing, on a short scale: hated, hostile, wary, neutral, friendly, honoured, revered (or simply −3 to +3).
Why: the deed that set it there.

The last column matters most. “Hostile” is a mood; “hostile because you took their seal” is a story. Change your standing only for deeds the faction would hear of, and write down what they were.

Give each faction a move between sessions, too: one sentence of what it did while you were not looking. In Valdrath, the village honours you because you came to bring its priest home, while the Order of the Broken Sun is hostile and already knows your name. The two pull in different directions, which is what factions are for.

Solo FRP keeps the campaign’s factions and your reputation with each, beside the codex of people and an NPC web of how they are bound to one another.

Quests as steps, not paragraphs

A quest written as a paragraph is hard to act on. A quest written as steps tells you what to do tonight. Keep each entry in your quest log to:

a title, and who gave it;
the goal, in one sentence;
steps, each an action your hero can take, ticked off as it is done;
the next step, plain at a glance.

The sample adventure’s first quest, The Missing Priest, reads: speak with Brenna at the Black Pear (done); search Father Cern’s quarters (done); enter the Valdrath crypt; recover Father Cern or his remains. Anyone could sit down and play the next step.

Keep finished and failed quests in the log as well: the people in them remember how they ended.

Solo FRP’s quest log keeps each quest the same way, as steps.

A timeline of what is coming, with deadlines

The world should move whether or not your hero is watching. A campaign timeline lists what will happen, and when, if no one intervenes:

the day, or “in three days”;
what happens;
who is involved;
how sure you are: a certainty, or only a rumour.

Deadlines turn a quest into a choice. In the sample adventure, Morath expects the seventh name within two days. With a date on it, every hex you walk and every night you rest costs something, and the timeline keeps the count.

Read the timeline at the start of each session. Anything that came due while you were away happens now.

Solo FRP keeps a timeline of looming events, some with deadlines that will not wait.

Your solo RPG campaign journal: threats, promises and facts

The journal is where the campaign’s loose truths live. Keep three lists:

Threats: what is coming for you. The Order of the Broken Sun knows your name. Something below the abbey is waking.
Promises: what you swore, and what is owed to you. You swore to find the priest. Brenna owes you a favour.
Facts: what is settled. You carry the Vessari seal. The vespers bell has not rung for three days.

Two habits keep the lists honest. Write facts as short sentences you could check, not impressions. And keep rumours out of the facts until play confirms them: the oracle’s yes to does Brenna know more than she says? is a fact, while the tavern’s gossip about the crypt is not, yet.

Session notes, a few lines on each sitting, can live at the back of the journal. Those solo RPG notes are for reading back; the three lists are for playing from.

In Solo FRP the journal is headed the Loremaster remembers, and it holds the threats, the promises and the facts.

A worked example

You write: I lay the broken seal on the bar and ask Brenna if she knows the crest.

The journal says: a fact, you carry the Vessari seal; a threat, the Order of the Broken Sun knows your name; a promise, Brenna owes you a favour.

You ask the oracle: Does Brenna recognise it? You judge it likely. Yes.

What happens: She covers the seal with her cloth before anyone else can see it. “Vessari,” she says. “Put that away, and don’t show it in my common room again.”

You record: in the codex, that Brenna knows the name Vessari and fears who might be listening; in the journal, a new thread: who at the Black Pear is watching?

Three lines of record made that scene possible, and two more came out of it. That is the whole rhythm.

Summaries that let you pick up after a month away

How do you restart a solo campaign after a break?

Write a summary every few sessions, and at the end of any session you suspect will be the last for a while. Five sentences are enough: where the hero is, what they want, what threatens them, what they owe, and what they meant to do next.

When you return:

Read the latest summary, then the timeline.
Advance anything that came due.
Skim the open threads, and choose one.
Play a short, low-stakes scene first, a meal or a stretch of road, to find the hero’s voice again.

Writing a summary also catches drift: the thread you dropped, the name you never recorded.

Solo FRP writes periodic summaries of the story as you play, so a long campaign’s record does not rest on its last few scenes alone.

When an AI keeps the record for you

Why do AI dungeon masters forget things?

A chatbot used as an AI dungeon master reads only a limited amount of text at a time. In a long campaign the early scenes fall outside what it can see, and without a separate record it fills the gaps by guessing. That is how a priest who vanished in the crypt turns up pouring ale. The problem of AI dungeon master memory is a simple one: the story lives in a scrolling chat, and the chat grows longer than the model can hold.

How can an AI game master remember a long campaign?

The same way a careful human does: by keeping the records in this guide apart from the conversation, and consulting them as it plays. People, factions, quests, deadlines and facts belong in records the AI can read again, with summaries for the rest.

That is how Solo FRP keeps a campaign. It holds a codex of the people you meet and an NPC web of how they are bound together, factions and your reputation with each, a timeline of looming events with deadlines, a quest log with steps, a journal of threats, promises and facts, and periodic story summaries, so the story stays consistent from session to session. And should a turn go somewhere you did not mean, undo takes it back.

For more on what an AI Game Master does at the table, read What Is an AI Game Master?; for the map the codex points to, read the solo hexcrawl guide. New to playing alone? Your first solo session starts at the beginning, and what the Loremaster remembers shows these records in their place in the game.