How to Keep NPCs and Past Choices Straight in an AI-Run RPG Campaign
When an AI-run role-playing campaign stretches across multiple scenes, the hardest continuity problem is often remembering what the group already established: who an NPC is, what they know, and how earlier choices changed the situation. Use a small campaign ledger with one entry per important character, a dated record of consequential events, and a short recap you can give the AI at the start of a session. Treat that ledger as the reference, and correct contradictions as soon as they appear.
Why AI campaign continuity needs a written record
An AI can produce a fluent scene while still misremembering or inventing a detail from an earlier one. A name, promise, or motive that seems minor in the moment may matter several sessions later. The practical fix is to move continuity out of conversational memory and into notes you control. This is a play procedure, not a guarantee that every AI tool will retain or correctly apply the notes.
A useful record answers three questions: What was established? What changed? What remains unresolved? Keep those separate. For example, “Mara is the ferrymaster” is an established fact; “the party gave her the brass token” is a change; “she has not said why she recognizes it” is an open question. That distinction makes it easier to give the AI accurate context without turning every recap into a full transcript.
Start with a compact campaign ledger
Create a campaign overview with the current in-fiction location, the party’s immediate aim, the most consequential recent events, and unresolved threads. Keep it brief enough to scan before play. A practical target is a handful of bullets, not a scene-by-scene retelling.
Then create a separate entry for each NPC who has returned, affected a meaningful decision, or holds information the party may need later. Include a stable identifier, such as “Mara Venn, ferrymaster at Greybridge,” so the AI and players do not confuse her with another Mara. Add only useful continuity fields: role, first meeting, what the party knows, what the NPC knows, relationship changes, promises or debts, and current status.
A tabletop game can give you a model for tracking goals: Ironsworn is designed for solo, co-op, and guided play, and its official description highlights quests, vows, bonds, and story prompts as parts of play. You can borrow the general idea of recording active goals and bonds without adopting Ironsworn’s rules in a different campaign. Ironsworn RPG – Tomkin Press
Log choices as events and consequences
After a session, record only choices that could affect a later scene. Write each as a compact event with a clear cause and consequence: “Session 4: The party returned the map to Mara; she agreed to guide them through the marsh, but kept the map’s torn corner.” This preserves what happened without requiring the AI to infer it from a long transcript.
Use concrete verbs and avoid interpreting a character’s inner life as fact unless the story established it. “Mara handed over the key” is observable. “Mara now trusts the party completely” may be an unsupported conclusion. If the meaning is uncertain, mark it as a question: “Her willingness to help may indicate growing trust; not confirmed.” This gives the next scene room to develop while keeping the established facts intact.
For decisions with continuing consequences, make an open-thread list: a short name, what the group wants or needs to resolve, the last known state, and any next clue or decision. Close an item when the story resolves it, but keep the event in the history. That way a finished thread does not appear active in the next recap, while the reason it mattered remains findable.
Give the AI a focused continuity brief
At the start of a session, provide the campaign overview, relevant NPC entries, and only the recent events that matter to the opening scene. State which notes are established canon and which are unresolved or uncertain. If an NPC is appearing, include the details relevant to this meeting rather than pasting every note in the campaign.
A reusable prompt can be simple: “Use the following notes as established campaign facts. Do not change them without a new in-story event. If a detail is missing, ask me or leave it unspecified instead of inventing a past event. Current scene: [location and situation]. Relevant NPCs: [entries]. Recent choices: [events]. Open threads: [list].” This is a practical instruction, not a feature guarantee; AI systems vary, so check important details in the response.
If the AI introduces a contradiction, pause before building on it. Point to the note and state the correction plainly: “Mara kept the map’s torn corner; the party has never seen it again. Continue from that fact.” Then update your record if the new scene establishes a change. Correcting the ledger prevents the same error from reappearing in later sessions.
Use links and structured fields when the campaign grows
A notebook or plain text file is enough for a short campaign. If the cast expands, separate NPCs and sessions into linked notes so you can follow a character’s history without searching a large log manually. In Obsidian, for example, notes can link to one another, and its Backlinks feature shows notes that refer to the active note. This can help locate session entries mentioning a recurring NPC. Link notes – Obsidian Help Backlinks – Obsidian Help
Structured properties can make recurring fields consistent. Obsidian’s documentation describes properties for data such as text, links, dates, checkboxes, and numbers. For an NPC note, you might use fields such as role, first_seen, status, and last_seen; keep free-form motives and scene history in the body of the note. The fields are an example organizational choice, not a required format. Properties – Obsidian Help
Paper cards, a shared document, or a spreadsheet can work just as well. The best tool is the one your group will update after play. More fields create more upkeep, so start with the minimum that prevents confusion and add a field only when a real continuity problem recurs.
A worked example: the missing map corner
Suppose the party meets Mara at Greybridge and trades a brass token for passage. During the scene, she recognizes the token, agrees to help, and secretly keeps a torn corner of the party’s map. A compact record could read:
NPC — Mara Venn: Ferrymaster at Greybridge. First met in Session 2. Recognized the brass token; reason unknown. Agreed to guide the party through the marsh. Kept a torn corner of the map. Current status: at Greybridge, unless later events change this. Open thread — Token’s origin: Mara recognized it; party has not asked why. Session 2 event: Party traded the token for passage; Mara kept the map corner.
Before the next session, include Mara’s entry, the token thread, and the map event in the brief if the party is returning to Greybridge. If the AI says Mara never saw the token, correct the record before continuing. If the party later asks about the map, add her answer as a new event and update the open thread. This sequence keeps the established detail, the unanswered question, and the new development distinct.
Keep the record small enough to maintain
Do not try to preserve every line of dialogue. Record names, relationships, promises, discovered facts, changed circumstances, and decisions likely to matter again. Leave out decorative details unless the group has chosen to make them significant. When a note grows long, retain a short current-state summary and link or refer to the dated session entries for the full history.
After each session, spend a few minutes on a fixed closeout: update NPC status, add consequential events, revise open threads, and prepare the next starting brief. If you play with friends, agree on who records the notes and let everyone correct factual errors. A shared ledger works best when it reflects what the group established, rather than one player’s unmarked speculation.
Continuity comes from giving the story a dependable record: identify recurring NPCs, write down consequential choices and their outcomes, label uncertainties, and bring the relevant facts back into the next session. That small routine gives an AI-run campaign a clearer past for its next scene to build on.