Lore Bible
The canonical reference for a game world's history, factions, and rules — keeps narrative consistent across teams writing dialogue, quests, and lore.
A lore bible is the narrative team’s source of truth. It answers the questions that every piece of writing in a game must be consistent with: What year is it? Who are the factions and what do they want? What are the rules of magic (or technology, or economics) in this world? What events happened before the game begins?
Without a lore bible, consistency failures accumulate. A writer invents a city name, another writer reuses the same name for a different city, and by the time someone notices, two hundred dialogue lines reference the wrong geography. A lore bible with version control stops this class of error before it starts — when a writer adds a fact, the merge request is where the discrepancy gets caught.
Lore bibles grow over the life of a project and often outlive it. A shipped game with a sequel in development has a lore bible that spans both projects, tracking what was established in the first game and what is canonical for the second.
How it works in Gameframe
Gameframe’s branch model is well-suited to lore bibles because lore changes are often speculative — a writer drafts a new character backstory, but it only becomes canonical when the lead narrative designer approves the merge. Until then, it lives on a branch without touching the main document.
Gameframe’s Narrative Designer specialist reviewer reads documents in the context of the studio’s stated tone and world rules, flagging character voice inconsistencies, arc contradictions, and worldbuilding gaps.
Start free and keep your lore bible in version control alongside your GDDs.