Casting Series Bible characters and locations into a book

Knowledge Base / Series, Characters & Continuity /Casting Series Bible characters and locations into a book

Your Series Bible stores the master definitions for recurring characters, locations, and lore entities across an entire universe. Casting is how you bring those canonical assets into a specific book, comic, or sequel without risking accidental edits to earlier volumes.

How casting works (copy-with-lineage)

When you cast a character, setting, or lore item from a Series Bible into a project:

  1. BookZeta creates a local project copy of that asset—carrying over its physical description, reference portrait, and named outfits.
  2. Behind the scenes, the project asset keeps a lineage link back to its parent entry in the Series Bible.
  3. Any edits you make inside the current book apply only to this book, leaving your previous books and the master Series Bible untouched until you decide to save a new canonical version.

That separation solves one of the biggest headaches in multi-book series: if your detective loses an arm at the end of Book 2, updating her appearance in Book 3 will never retroactively alter regenerations or exports of Book 1.

Picking the right asset version for prequels vs sequels

Because characters and locations change over time, the Series Bible supports versioned assets. When casting an asset into a new project, the Version Picker lets you choose which era of that character or location to import:

  • Writing a sequel (Book 4): Cast the latest version of your protagonist—complete with the title, scars, alliances, and wardrobe earned in Book 3.
  • Writing a prequel: Cast the Book 1 (or "Origin") version of the same character and the unruined version of a city before the war happened, while keeping the exact same core facial identity for illustrations.
  • Writing a spin-off: Pull two side characters and one shared tavern location into a standalone story without dragging twenty unrelated main-series characters into the AI context window.

Tracking character status across books

Every character asset includes a Status field (such as active/alive, deceased, missing, or retired). Keeping status current before generating a continuation prevents one of the classic long-series continuity errors: a character who died in Volume 2 casually walking into a tavern scene in Volume 3.

Before kicking off an automated sequel or chapter batch, review your cast list alongside What to put in a character profile so every character's current status, outfit, and motivation reflect where the new book begins.

Was this article helpful, or still stuck? Contact support

Related articles