The short answer: enough to make the world feel alive, but not so much that you turn continuity into a bookkeeping job. The trick is to decide what gets remembered, who remembers it, and how that memory changes future behavior.
Who it's for: this guide is for DMs, GMs, and game developers who want NPCs and factions to feel persistent across long campaigns or ongoing worlds.
1. Decide what kind of memory matters
Not every event deserves to be remembered forever. Separate memory into a few simple buckets: personal interactions, public actions, faction-level events, and major world-changing choices.
A merchant should probably remember a bargain, a favor, or a theft. A city guard should remember a public insult or arrest. A faction should remember betrayals, alliances, and destroyed assets.
2. Track anchors, not every sentence
Use short notes that capture the important facts: who did what, to whom, when, and what changed because of it.
Good memory notes are usually one line each: "Helped the innkeeper during the flood," "Humiliated by the party in public," or "Lost two scouts to the adventurers."
3. Decide how long the memory lasts
Some memories should fade, some should stay, and some should escalate. A shopkeeper may forget a minor awkward meeting after a few sessions, but a guard captain may remember a jailbreak for the rest of the campaign.
A useful rule is: trivial events fade, personal events linger, faction events persist, and betrayals leave scars.
4. Make memory change behavior, not just dialogue
Remembering something should do more than add a callback line. It should change what an NPC is willing to do, say, offer, or refuse.
Examples: a merchant gives a discount, a guard asks extra questions, a faction sends reinforcements, or an old contact quietly warns the party about a trap.
5. Use faction memory as a pressure system
Treat factions like groups with shared institutional memory, even if individual members come and go. The faction may not know every detail, but it should know the broad shape of what the party has done.
Think in terms of relationship states: neutral, suspicious, cautious, friendly, allied, hostile. Then tie specific actions to movement between those states.
6. Let important memories create delayed consequences
The strongest campaign continuity often comes from consequences that show up later, not immediately. A favor from ten sessions ago might become a secret passage, an informant, or unexpected mercy.
Likewise, a small act of cruelty might return as a closed door, a refused service, or a faction quietly helping the enemy.
7. Keep the system lightweight enough to actually use
If you need a spreadsheet to remember every conversation, the system is too heavy. Use a few tags, a short timeline, or a simple reputation note per important NPC or faction.
Review memory between sessions and prune anything that no longer matters. The goal is continuity, not archival perfection.
Common mistakes
- Remembering everything equally, which makes the world feel noisy instead of meaningful
- Tracking memory but never letting it affect behavior, offers, prices, trust, or future choices
- Forgetting that factions are not individuals and need shared memory at the group level
- Making the continuity system so complex that the DM or dev team stops maintaining it
FAQ
Should every NPC remember the party forever?
No. Save long-term memory for NPCs who matter to the story, the setting, or the players' relationships. Background NPCs can forget minor interactions, while major recurring characters should remember the party's most important actions.
How much should factions remember compared to individual NPCs?
Factions usually remember the pattern, not every detail. They should know whether the party helped them, embarrassed them, threatened them, or hurt their interests. Individual members can remember the personal version of the event.
What is the best way to keep continuity without too much bookkeeping?
Use short memory notes, a few relationship tags, and a simple rule for how each memory changes future behavior. If a memory does not affect a future scene, it probably does not need to be tracked.