Skip to main content

Understanding the Codex

The Codex is the lore coordinator behind every recap. After transcription and recap generation, Epicly passes that session through the Codex Update System so it can extract plot beats, NPCs, locations, lore threads, and quests, then update your campaign wiki automatically. This guide mirrors the help link on the in-app Codex page so you can follow along without leaving the tool.

Codex update system​

  • Automatic processing. Every new session upload runs the Codex Update System once the recap is ready. The system extracts entities, updates or creates wiki entries, refreshes the plot overview, and writes a change summary for each automatic edit. You can toggle the entire run off for a campaign from the Settings tab or manually trigger/retry it via the session detail menu when you need to backfill older sessions.
  • Plot overview. The system generates a high-level plot overview with every run, then keeps updating it as the story progresses. You can edit the plot text manually, leave it on auto-update, or lock it by turning the Auto-update toggle off in the overview editor so nothing changes until you want it to.
  • Entity extraction. Codex runs look for locations, factions, player characters, NPCs, lore beats, and quests. For each match it either creates a new wiki entry or updates an existing one (matching against names, aliases, and related tags). Alias management is critical—keep the lists current so the Codex can add new information to the right page instead of generating duplicates.
  • Folder intelligence. The automation suggests folders for new entries based on inferred geography and relationships. It never moves existing entries; instead, it learns from the folder structure you build so future suggestions follow the patterns you prefer.
  • Entry controls. Each folder and entry has an Auto-update toggle (on by default) and a Private toggle. Turn off Auto-update to keep a lore item frozen, and enable Private to hide the content from players until you’re ready to reveal it.
  • Aliases, tags, and GM notes. Every entry ships with alias lists and related tags to help the Codex match future references. You can add additional aliases or tags, and the GM notes field lets you store hidden reminders that only creators and GMs can read.

Modes and proposals​

  • Auto mode. The default mode. Approved Auto-update entries apply changes immediately so your wiki stays continuously in sync.
  • Review mode. When you switch a campaign to review mode (via Settings), every Codex run becomes a proposal queue. Each proposed change appears in the wiki tree and in the session’s Change Report; approve or reject it from there. Before approving you can edit the proposed text, and update proposals show existing vs. proposed content side by side.
  • Review queue toggle. The Wiki tab shows a Review Queue button when there are pending proposals. Clicking it opens the queue (temporarily hiding the regular tree) so you can Approve or Reject each change proposal, and clicking it again returns you to the wiki.

Versions, change summaries, and reports​

  • Version history. Every automatic or manual edit saves a version with a generated change summary. Open the “Show versions” control on any entry or on the plot overview to browse past drafts, compare revisions, or restore an earlier text.
  • Codex Change Report. Each session detail page now has a Change Report card that displays the latest Codex run status, lists entities created or updated by that run, and links to those entries. The report auto-refreshes while the run is processing, players only see approved changes, and GMs see pending proposals.

Exploring the Codex page​

  • Home tab. Tracks campaign stats like time since the last session and your longest weekly streak so you can monitor momentum.
  • Overview tab. Displays the campaign description alongside the live plot overview updated by the Codex.
  • Sessions tab. Lists every session (list and timeline views) and shows separate recap and Codex status indicators so you always know what still needs a run.
  • Wiki tab. This is the heart of the feature:
    • Folders and entries live in the left-hand tree; selecting one reveals its contents in the central pane.
    • Use the … menu beside any folder or entry to rename it, delete it, move it, or access special controls like Auto-update and Private toggles.
    • Auto-update toggle: Disable it to keep that entry/folder untouched by future Codex runs.
    • Private toggle: Enable it to hide the entry (or entire folder) from players—the tree displays a lock icon to signal privacy.
    • Entry editor: Rich text controls let you edit the title, body, related tags, aliases, and GM notes.
    • Related tags jump straight to linked entries, and aliases help the Codex match incoming lore to existing pages.
    • GM notes stay hidden from players while letting creators leave behind-the-scenes reminders.
    • Review queue button, visible when review mode has pending proposals, swaps the tree for the queue view so you can work through approvals without losing your place.
  • Settings tab. Only campaign owners and GMs can turn Codex automation on/off, switch between Auto and Review modes, and configure the help link that points back to this guide.

Using the Codex workflow​

  • Status indicators. Every session row now shows both recap and Codex status so you can see at a glance what has finished. Sessions processed before this update will state “Codex not run” until you trigger them manually.
  • Triggering and retrying runs. Use the … menu on any session detail to trigger the Codex run for that session or retry a failed run. It takes a few minutes and Retry only resumes once a failure is resolved.
  • Ordering caution. Running the Codex out of chronological order treats that session as new input, so approve any resulting proposals carefully to avoid mismatched lore.
  • Security guardrails. Only the campaign creator and assigned GMs can see the Codex tabs, review queue, and editing tools.

Backfilling your wiki​

Codex automation is enabled by default. Reprocess your earliest sessions by triggering a Codex run, approve or reject any proposals, then work forward chronologically so your wiki reflects every session, locks in aliases, and is ready for the next play night.

Last updated on