How to Write a Game Bible: The World-Builder's Template

A Game Bible is the one document that defines your world. It's what the AI Game Master reads before your first session begins, and it's what the GM leans on when a player asks something nobody saw coming, thirty hours into a campaign. A great Game Bible gives you consistent, immersive storytelling. A vague one gives you the Generic Fantasy Experience™, where worlds blur into one another and every scene drifts toward the bland middle of everything the model has ever read. Even the NPCs start to sound alike.

This post is a practical template you can fill in as you go. By the end, you'll either have a complete draft or a clear picture of what's still missing. It works for a brand-new world, and just as well for one you've been quietly incubating for years. I'll also tell you what actually happens to your document when you upload it to EchoQuest, because once you know that, you write differently.

It's short on purpose. A great Bible can be six to ten pages; you don't need a hundred. The AI doesn't read better with more text. It reads better with denser text. There's a hard practical reason too. When you upload a Bible, Claude reads up to 80,000 characters of it (somewhere around 13,000 words), and anything past that gets cut off. It then condenses what it read into a GM briefing of 200 to 400 words, plus tidy lists of the places and people that matter. Every line you write is competing for a spot in that briefing, so make each one earn it.

What Goes in a Game Bible

Think of your Game Bible as the answers to six questions:

1. What kind of world is this?
2. What's wrong with it right now?
3. Who are the major players?
4. What does it feel like to be here?
5. What are the rules?
6. Where does the story start?

If your draft answers all six clearly and specifically, you've got a playable world. If any answer is vague, the AI GM will plug the gap with the most generic version of that thing in fantasy fiction. I can point to the exact reason in my own code. When Claude extracts a world from an uploaded Bible, it's told to take only what the document actually says and not to invent lore, and a missing field falls back to a bland default such as "unknown" for tone. I'd make that choice again, because it's the honest behaviour. Still, it means blanks stay blank. The whole point of a Bible is to crowd out the generic with your specific.

Section 1: World Overview (1–2 paragraphs)

Name your world. Describe its scope: one city, a continent, several realms? Give the feel of its historical period: medieval, Renaissance, post-apocalyptic, a secondary-world modern day, or somewhere in the near or far future. State the dominant tone, too: gritty realism, high fantasy, cosmic horror, political thriller, fairy tale or slice-of-life. Then pin down the geography just enough that the AI knows the shape of the map without needing every contour.

Example: "Valdenmoor is a decaying empire in its third century of slow collapse. Think late Roman Empire crossed with the Venetian Republic: bureaucratic rot and mercenary armies, with gods that are slowly fading. The capital is a port city built on the ruins of three older cities, layered like sediment. Travel between provinces is by river or road, or, for those who can afford it, by airship. The tone is dark and political, with occasional moments of unexpected grace. Magic exists but is rare and slow, and people treat it with suspicion."

Naming real-world analogues matters a lot. "Late Roman Empire" hands the AI a coherent texture to draw on in a way that "ancient kingdom" never will. Don't be shy about citing influences. The AI recognises them and uses them as scaffolding. I leaned on the same idea myself when I gave each of EchoQuest's nine prebuilt worlds a short block of true, researched detail. The pirate world learned how a ship's bell counts out a watch, and the steampunk one learned how glowing rivets were tossed from the heater to the catcher before being hammered home. Real texture beats invented texture nearly every time.

Section 2: The Central Conflict

What's the one tension that defines this moment in your world? It should be specific and active, something happening right now rather than ancient history. The conflict is the engine. Without it, your world is a museum.

Example: "The Emperor has just died without an heir. Three Archduchies are mobilising armies. A fourth is secretly negotiating with a foreign power. The Church has declared it will name the next emperor from among the clergy. Civil war is two weeks away. No major faction is ready, but none can afford to wait."

History got there first, by the way. After Nero's death in AD 68, Rome lived through the Year of the Four Emperors: Galba, Otho, Vitellius and Vespasian all held power within a single year, and rival legions fought a civil war over the throne. If you need a model for a succession crisis, it's hard to beat.

Notice the time pressure in "two weeks away". It gives the world a clock, and the AI will use that clock. Scenes will refer to it without you having to remind anyone, so the pressure stays on with no extra effort from you. In EchoQuest, a conflict like this also belongs in that short GM briefing, which sits at the top of every single turn Claude plays. Spend your sharpest sentences here.

Section 3: Factions (3–5)

For each faction, write two or three sentences on who they are and what they want, and on what they're willing to do to get it. Skip the histories. Write current agendas.

Here's a faction template that works well:

• Name (and what people call them informally)
• Public goal (what they say they want)
• Real goal (what they actually want, if it's different)
• Willing to do (what's on the table: bribery, assassination, an alliance with a hated rival, a public scandal)
• Won't do (the line that defines them)
• Internal weakness (the crack that could split them apart)

Three to five factions is the sweet spot. Two feels binary; six feels like homework. Each faction should have at least one other faction it treats as an enemy and one it treats as a complicated ally. Never simple goodwill, and never simple hatred either.

Here's something worth knowing before you write pages about each one. When EchoQuest reads your Bible, every faction boils down to a name, a short description and a disposition toward the player (friendly, hostile, neutral or unknown). That's a small box. So I'd make sure the "won't do" line survives by putting it in plain words near the top, instead of burying it in paragraph four. The same goes for the important NPCs inside each faction. Each one's personality gets trimmed to about 120 characters in the GM's briefing, so lead with the thing that matters most about them.

Section 4: Tone & Sensory Language

Give the GM a list of sensory details specific to your world. What does the capital smell like? What sounds fill a tavern? What does magic look like when someone casts it? How do the rich and poor districts differ in smell and sound, not just in looks? What does the dominant religion's incense smell like, and what's underfoot in the marketplace?

Details like these separate generic narration from immersive storytelling. The AI is excellent at picking up sensory cues from source material and weaving them naturally into descriptions, but only if you supply them. Three sentences of sensory detail per major location go a remarkably long way.

Smell deserves special attention, I'd argue. Harvard neuroscientist Venkatesh Murthy explains that odour signals get to the limbic system very quickly, reaching the amygdala and hippocampus, which deal with emotion and memory. In an audio game, where nobody sees a single pixel of your world, a well-chosen smell does much of the work a picture would.

A good habit: write one sentence that captures each location's "first ten seconds", meaning whatever a visitor notices first. "The Spice Quarter announces itself at fifty paces with the smell of cardamom and dried fish, cut with burning sandalwood; under that, the constant clatter of small handcarts on cobbles." That sentence will shape every scene set there. It also maps neatly onto how EchoQuest stores places. Each location gets a short line of 8 to 12 words that rides along in the GM's snapshot whenever you're there, plus a fuller description you hear when you press L to ask where you are. Claude also tags each place with an ambient mood, which picks the background track, so a line about harbour bells or dripping moss pulls its weight twice.

Section 5: Rules & Constraints

What can't happen in your world? Where are the hard limits? Some examples:

• "Magic is rare and feared: nobody casts spells openly"
• "This world has no elves or dwarves; every character is human"
• "Death is permanent and treated with gravitas: there's no resurrection magic"
• "Technology is roughly that of 1200s Europe: no gunpowder weapons yet"
• "There are no gods, but there are ancient creatures people sometimes mistake for gods"
• "Travel between continents takes weeks; teleportation doesn't exist"

About that gunpowder line: choose your century with care, because history moved faster than people tend to think. Brass cannons were being cast in Florence in 1326, and an English manuscript from that same year already shows one. Write "1400s Europe, no gunpowder" and a well-read GM (or player) would be entitled to raise an eyebrow.

The GM will respect these constraints throughout your campaign. In EchoQuest, Claude is told to capture every mechanical rule from your Bible, and those notes go into the GM's briefing whole instead of being squeezed into the short summary. The GM's own instructions also say the world's Bible is the source of truth for setup and mechanics. If your Bible spells out stat limits, like a maximum per stat or a pool of points to spend, character creation enforces those as well. Constraints clarify. They make the AI's improvisation tighter, because it has fewer easy outs. That's why the World Builder Wizard asks you for exactly one: "Name one hard rule of this world the game master must respect."

The most powerful constraint is usually a "no". A "no resurrection" rule means deaths matter. A "no gunpowder" rule gives battles a particular shape. With "no telepathy", news travels at the speed of horses. And a "no writing" rule turns every oath into a matter of witnesses and memory. Each one ripples outward into interesting consequences in play. What's the "no" at the heart of your world?

Section 6: Opening Scenario

Describe the first scene in two or three sentences. Where is the player character? What's happening right now? What's the first decision they have to make?

Example: "You're a junior aide in the Imperial Chancery on the night the Emperor dies. The chamber is in chaos. A high-ranking official has just handed you a sealed letter and asked you to deliver it to the Archduke of the Northern Reach, without telling anyone. You don't know what's in the letter, but you can see the official is sweating, and a guard captain is pushing through the crowd toward you."

The opening should drop the player into immediate, mid-stakes action with a specific choice. It shouldn't begin with "you wake up in a tavern". Anything-but-a-tavern is a handy rule of thumb. Storytellers have known this for a couple of thousand years: Horace praised the "immediate interest" of starting in medias res, in the middle of things, instead of ab ovo, from the egg. I took the same advice for EchoQuest. The GM opens every new game cold, already mid-moment, and the Wizard asks you to describe your opening scene in just one or two sentences for exactly that reason.

Section 7 (Optional): Pronunciation Notes

If your world has invented names with non-obvious pronunciations, list them with a phonetic guide. "Aeryndel: pronounced AIR-in-del. Tovaryn: TOH-vah-rin. The capital, Khel-im-Karras: KEHL-im-CAR-ras." Notes like these help the GM keep its narration consistent, and they help any human who reads your Bible.

Here's an honest caveat, though, from someone whose game is spoken aloud from start to finish. A speech engine reads the letters it's given. There's a whole W3C standard, the Pronunciation Lexicon Specification, that exists purely to tell speech engines how to say tricky words, which tells you how often they guess wrong. EchoQuest doesn't use pronunciation dictionaries, so the most dependable fix is a spelling that says itself. If "Aeryndel" keeps coming out mangled, ask yourself whether "Airindel" would serve your world just as well. Then listen to your names in play, with the browser voice and, if you have it, a premium voice too.

Uploading Your Bible

EchoQuest accepts Game Bibles as PDF, DOCX, plain text, Markdown or JSON files, up to 10 MB each. Claude reads your document (it takes about fifteen seconds, and the page announces each stage as it goes, which screen reader users will appreciate), pulls out the world data and builds a playable campaign from it. That includes locations and NPCs, factions and campaign hooks, important items, and any classes, backgrounds or stat rules you defined. Plain text or Markdown is the safest bet, since there's no layout to untangle, although a well-formatted PDF works fine too.

Once it's built, you can jump straight in with "Play Your World Now". Then pay attention to the world's synopsis, the short summary Claude writes to introduce it. That's a quick test of what Claude took from your document. If it sounds vague, your Bible probably is too, so tighten the weak section and upload again. On the Storyteller plan you get one private world, so delete the old version from My Worlds before re-uploading. The Creator plan lifts that limit and lets you publish finished worlds to the library, where other players can find them.

Storyteller plan and above includes Bible upload access. See plans →

Related reading: Browse all EchoQuest blog posts.