Codex

The Codex is a story-owned lore book that collects information Dreamers discover while playing. Each Codex Entry can describe a person, place, object, faction, historical event, concept, rule, mystery or clue.

Use it when your story has more context than should fit naturally into dialogue or narration. A Codex can work like a lore book, glossary, encyclopedia, compendium, journal or collection of lore entries, while still keeping discovery tied to the player's progress.

Unlike a normal glossary that is fully visible from the start, a Talescape Codex grows over time. Entries are unlocked through story actions and stay part of the Dreamer's permanent story progress, similar to achievements.

A Codex is most useful when the story should reveal information gradually and let Dreamers revisit it later. The main path should still be understandable without studying every entry, but the Codex can reward attentive players with richer meaning, optional context and a clearer sense of progression.

Common uses include:

• Lore book: Background information about the world, history, culture, magic, technology or factions.
• Glossary: Short explanations for recurring terms, invented words, rituals, systems or setting-specific language.
• Encyclopedia: Structured reference pages for people, places, items, creatures, organizations and events.
• Investigation journal: Clues, case notes, witness details, discovered locations or mystery fragments.
• Memory archive: Personal memories, recovered records, dreams, echoes or revelations that should persist beyond one scene.

Bards manage Codex Entries inside the story editor. Each entry is a content record owned by one story and can be prepared, reviewed, published, archived and connected to story logic.

Each Codex Entry contains:

• Title: The visible name of the entry. Titles must be unique within the same story.
• Category: A required free-text grouping such as People, Places, Objects, History, Factions, Clues or Concepts.
• Teaser: An optional short preview shown before or beside the full entry.
• Image: An optional visual asset used to make the entry easier to recognize.
• Description: The main body text of the entry.
• Status: Draft, Published or Archived.

Descriptions can use simple formatting such as headings, bold text, paragraphs and separators. Use formatting to make longer entries easier to scan, but keep the writing focused on the story.

Only Published entries are available to story logic and Dreamers. Draft entries can be used while writing and reviewing content. Archived entries can be kept for reference without exposing them to players.

Categories should be short and consistent. They are not managed as separate models, so decide on a small set of category names early and reuse them.

A mystery story might use People, Locations, Evidence and Events. A fantasy story might use Factions, Places, Magic and Relics. A slice-of-life story might use People, Places, Memories and Objects.

Recommended category rules:

• Use plural nouns where possible, such as People, Places, Objects and Events.
• Avoid near-duplicates such as Location and Locations.
• Keep the number of categories small enough that Dreamers can scan them.
• Use category names that match the story's mental model, not internal editor structure.

Codex Entries are unlocked through actions. A Bard can attach a Codex unlock action to events, choices, scene starts, investigations, item interactions or any other moment where the story reveals new information.

Good unlock moments include:

• The first time a character is introduced.
• When the Dreamer discovers a location.
• After inspecting an important object.
• When a hidden route reveals new context.
• After a major choice changes how earlier information should be understood.

Unlocks are permanent for the Dreamer within that story. Once an entry is unlocked, it remains available in their story progress even if they start a later playthrough.

Conditions can check whether a Codex Entry has already been unlocked. This allows Bards to react to player knowledge.

Use Codex conditions to:

• Show a shorter explanation if the Dreamer already unlocked the relevant entry.
• Offer a special dialogue option when the Dreamer has discovered a clue.
• Avoid unlocking the same lore beat twice in a noticeable way.
• Gate optional recap text behind whether the Dreamer has already found the background information.

This works especially well with dialogues, investigations and optional scene interactions.

For Dreamers, the Codex acts as a growing reference collection. It should feel like a natural part of exploration rather than a separate database that must be studied before the story makes sense.

The Codex can help Dreamers:

• Review characters, places and events after a break.
• Understand invented terms without interrupting dialogue.
• Track clues or discoveries in mystery-heavy stories.
• Notice that a hidden route revealed something meaningful.
• Revisit worldbuilding without replaying a scene.

The Codex can show discovered entries clearly while keeping undiscovered entries hidden behind placeholder cards. This lets Dreamers see that there is still more to find without revealing hidden titles, images or descriptions too early.

Use the Codex for information that is valuable, reusable or easy to forget. Do not use it for every sentence of exposition. The best entries give Dreamers something worth returning to.

Recommended patterns:

• Introduce, then expand: Unlock a focused entry when something first appears, then unlock related entries as the Dreamer learns more.
• Reward optional exploration: Use entries for secrets, side routes, environmental details and alternate perspectives.
• Support long stories: Help Dreamers remember names, relationships and prior discoveries across chapters.
• Keep entries focused: One entry should explain one subject. Split long encyclopedia pages into multiple entries if they cover different ideas.
• Pair entries with images: Portraits, symbols, maps, evidence photos or object art make entries easier to recognize.
• Use categories as navigation: Categories should help Dreamers find information quickly.
• Connect lore to action: Unlock entries at the moment the Dreamer learns the information, not long before or long after.

Avoid unlocking many entries at once without narrative context, requiring Codex reading for basic comprehension of the main path, using categories as hidden technical labels or publishing entries that are not reachable through actions.

Test unlocks in Story Preview before release, especially when Codex entries are tied to optional paths, clues or persistent discoveries.