How to Build a Living Campaign Wiki for Your TTRPG (Step-by-Step)

A step-by-step guide to building a living campaign wiki for D&D, Pathfinder, or any TTRPG. Use AI extraction, structured canon, and evidence-grounded entries so the wiki updates itself as you play.

How do I build a living campaign wiki?

Build a living campaign wiki by treating canon as a structured ledger of typed entities (NPCs, locations, factions, quests, items) instead of free-form prose. Tabletop Arc analyzes session transcripts, proposes updates, and renders the canon as a wiki that updates itself — every entry is evidence-grounded and links to the moment it was established.

What is a "living" wiki?

A static wiki is one a GM updates by hand. A living wiki updates itself: as you play, the canon ledger grows, and the wiki re-renders to reflect new facts. Tabletop Arc renders the Lore Wall (per-arc wiki) directly from the structured ledger — there is no separate "wiki document" to maintain.

Step 1: Decide the entity vocabulary

A wiki works because every entity has a stable, predictable shape. Tabletop Arc ships with twelve types: character_pc, npc, creature, faction, location, item, quest, event, lore, handout, rule_clarification, and house_rule. Use them as-is unless your setting demands new types — sticking to a small vocabulary makes the wiki coherent.

Step 2: Seed the wiki with starter content

Before session one, run a few archetypes through the town generator, NPC generator, and quest generator. Save the ones that fit. The starting set should be small (5-10 entities) — most of the wiki will come from play.

Step 3: Capture sessions

Record audio (or paste a transcript) and run analysis. Tabletop Arc proposes canon updates: new entities, new facts, modified relationships. Approve them in the Review queue.

Step 4: Set visibility

Each entry has a visibility flag (GM_PRIVATE, PLAYER_SAFE, PUBLIC). Player-safe entries appear in the player wiki; GM-private entries are hidden until you choose to reveal them. Public entries appear in the indexed public arc page if your campaign is published.

Every fact in the ledger ought to link to a transcript segment. Tabletop Arc does this automatically when analysis runs. For manually-entered facts (from GM notes), you can add evidence later if you have the source.

Step 6: Iterate

Run sessions, approve proposals, and let the wiki grow. By session ten, you will have a navigable, searchable, evidence-linked wiki that the players can browse between sessions.

Try it yourself — generate a free NPC right now

No sign-up required. Generate NPCs, quests, locations, and more.

Open NPC Generator

Frequently Asked Questions

Do I need to write entries by hand?
No. Most entries come from analysis of session transcripts. Hand-written entries are still possible (and useful for setting bibles or imported lore).
Can players edit the wiki?
Players can propose changes (new entities or facts). The GM approves what enters canon.
How do I prevent spoilers?
Use visibility flags. GM-private entries (or fields within entries) never appear in the player view. Player-safe and Public entries appear with appropriate scoping.
How is this different from a Notion or Obsidian wiki?
A general-purpose wiki is unstructured prose. The Tabletop Arc wiki is structured: typed entities, evidence segments, confidence levels, and AI-extractable facts. The structure is what makes the wiki "living" — it updates from session data instead of from manual edits.
Does the wiki support media?
Yes. Each entity supports image attachments (portraits, maps, handouts) and rich text in the body. Image generation is available on Pro and Legend plans.
Can I publish the wiki?
Yes. Toggle the campaign to Public; the wiki becomes a shareable, indexed URL with per-entity pages, breadcrumbs, and JSON-LD structured data so AI Overviews and search engines can cite it.

Related Tools

Related Articles

The AI Memory Layer for Tabletop Campaigns

An AI memory layer is the persistent, structured record of every fact in your TTRPG campaign — characters, locations, factions, quests, evidence, and confidence — that AI tools can safely read, update, and reference. Tabletop Arc is that memory layer.

AI Campaign Continuity: How to Run a Campaign That Remembers Everything

AI campaign continuity is the practice of using a structured canon ledger, evidence-grounded recaps, and a living wiki to keep every TTRPG session connected. Tabletop Arc is the AI memory layer for tabletop campaigns: every fact links to the transcript that proves it.

TTRPG Lore Tracking: How to Keep Campaign Canon Coherent for Years

TTRPG lore tracking is the practice of capturing every canonical fact about your tabletop campaign — characters, locations, factions, secrets, and rules — in a structured, evidence-linked record that compounds across sessions. Tabletop Arc is the AI memory layer for tabletop campaigns.

Persistent Campaign Memory: Make Your TTRPG Canon Compound Session Over Session

Persistent campaign memory is the structured, evidence-grounded record that turns isolated TTRPG sessions into a coherent, multi-year campaign. Tabletop Arc is the AI memory layer that lets canon compound instead of decaying.

Automatic D&D Recap Tool: Turn Session Audio into Player-Ready Recaps

An automatic D&D recap tool transcribes your session, extracts scenes and entities, and generates evidence-grounded recaps in player-safe and GM-private formats. Tabletop Arc is built for long-running campaign continuity, not just one-shot summaries.

Keep going