World Bible & Environmental Storytelling
Standards (4)
GD.18.4Worldbuilding
Construct and document immersive game worlds using spatial logic, environmental storytelling, visual themes, and narrative alignment to support exploration, gameplay, and storytelling.15.1Narrative Storytelling
Evaluate and demonstrate how narrative structure, point of view, character, conflict, theme, and setting impact story development.15.3Authentic Representation
Create content with authentic representation of diverse people, communities, perspectives, and stories.GD.17.3Narrative Design
Design branching narratives that use player choice, interactive dialogue, and worldbuilding to shape outcomes and give players influence over the story progression.
The task
Author the official, living World Bible for the game your studio greenlit in Unit 1. This document serves as the master narrative and environmental guide for your entire team, defining world history, faction identities, environmental visual clues, decay rules, and diegetic storytelling specs.
In modern game development, a World Bible is not an unread hundred-page novel. It is an actionable production manual built specifically to give level designers, 3D prop artists, concept artists, and audio designers clear rules for building believable, immersive spaces without relying on cutscenes or exposition dumps.
This is a collaborative studio deliverable: the team writes and publishes the shared document together, and each student publishes an individual process and contribution breakdown to their personal portfolio.
Deliverable: Published studio World Bible document (6 to 12 pages in a shared workspace like Google Docs, Notion, or Git wiki) + individual portfolio reflection entries on Google Sites under GAD2 U2.
Before you start
Read both prerequisite modules:
- Worldbuilding and Environmental Storytelling (
GAME-205) — visual lore, architectural styles, the palimpsest principle, and the 70/30 rule - Narrative in Games (
GAME-107) — embedded vs. emergent storytelling, punchy diegetic audio logs, branch-and-bottleneck agency, and authentic representation - Review your studio’s greenlit Team Game Design Document (
team-gdd) to ensure narrative alignment with your core gameplay loop and design pillars.
Steps
Step 1 — Convene department roles and assign document ownership
Every member of your indie studio has a paired role (established in your Studio Roles & Team Charter). While the Narrative Lead or Producer owns the master document file and keeps edits organized, every department contributes their dedicated sections:
- Narrative Lead: Owns the world timeline, faction philosophies, and audio log scripts.
- Art Lead: Owns the architectural vernaculars, faction visual motifs, and material wear states.
- Level Designer: Owns the vertical slice location breakdown, spatial sightlines, and micro-story tableaux.
- Audio / Systems Designer: Owns diegetic delivery methods, radio transmission specs, and player agency hooks.
Step 2 — Establish the core world premise and three-era timeline (GD.18.4)
Define the macro foundation of your game world. Ground the narrative in Hemingway’s Iceberg Principle: give the world immense historical depth, but keep the documentation lean and relevant to what will appear in your 5-minute slice.
Author a Three-Era Chronology:
- The Origin Era: The foundational state of the world before the conflict (the golden age, industrial expansion, or original civilization).
- The Rupture / Turning Point: The specific cataclysm, corporate collapse, technological breakthrough, or war that broke the old order.
- The Present Era: The current state of the world when the player presses start. What is the immediate survival reality? Why does this space look and feel the way it does today?
Step 3 — Author competing factions with authentic representation (15.1, 15.3)
Detail the 2 or 3 primary groups, factions, or societal strata that inhabit or contest your world.
In alignment with California AED CTE Standard 15.3, ensure each faction reflects authentic, multidimensional design rather than lazy stereotypes or monolithic tropes:
- Beliefs and Motivations: What do they value? What are their legitimate, grounded grievances or survival needs? (Avoid “evil for evil’s sake”).
- Internal Complexity: What disagreements exist within the faction? (e.g., radicals vs. moderates, generational divides).
- Visual Motif and Insignia: What is their recognized symbol, logo, or color accent?
- Architectural & Material Vernacular: What materials do they build with (e.g., monolithic brutalist concrete vs. kitbashed corrugated salvage)?
Step 4 — Deep-dive the vertical slice location using the Palimpsest Principle (GD.18.4)
Focus directly on the specific physical setting where your team’s 5-minute vertical slice takes place (e.g., Sub-Level 4 Hydro-Filtration Facility, The Sunken Neon Bazaar, or Outpost Echo Perimeter).
Apply the Palimpsest Principle by detailing the stratified physical layers the level artists will build:
- Layer 1 (Original Purpose): What was this structure originally engineered to do fifty years ago?
- Layer 2 (Modifications): What makeshift additions, security checkpoints, or conduits were bolted onto it over time?
- Layer 3 (The Event): What violent or structural event happened here? Where are the impact craters, breach points, or emergency seals?
- Layer 4 (Current State): What natural decay (water leaks, rust, mold, sand drifts) and human remnants (sleeping mats, spent flares, graffiti) exist right now?
Step 5 — Establish environmental storytelling rules and 3 micro-stories (GD.18.4)
Give your 3D modelers and level dressers clear, enforceable guidelines so all assets placed in the engine tell a unified story:
- Asset Wear States: Define clear criteria for when props should be Pristine, Serviceable, Weathered, or Ruined.
- The 70/30 Rule Application: Specify which surfaces in the slice must remain clean rest spaces for traversal, and where dense visual storytelling should concentrate.
- Three Concrete Tableaux (Micro-Stories): Design exactly three narrative prop clusters to be placed along the level’s path:
- Tableau A (The Departure): A scene showing how the previous occupants evacuated or perished (e.g., packed luggage abandoned by a locked airlock with spent security cartridges).
- Tableau B (The Struggle): A scene showing tactical combat or resistance (e.g., an overturned industrial loader forming a barricade with scorch marks and field dressings).
- Tableau C (The Clue / Secret): A hidden micro-story rewarding players who explore off the critical path (e.g., an unauthorized radio tapping into a corporate surveillance line in an elevator shaft).
Step 6 — Script diegetic narrative delivery and player agency (GD.17.3, 15.1)
Itemize every direct narrative delivery element for your vertical slice:
- Two Diegetic Audio Logs or Radio Transmissions:
- Write the full dialogue script for each log.
- Enforce the 15-to-25 Second Rule: Keep them brief, emotionally urgent, and contextually grounded.
- Specify the in-world playback device (e.g., dispatch radio, helmet recorder, surveillance terminal) and confirm that playback does not freeze player movement.
- Four Environmental Text Elements:
- Write the exact text, font style, and physical condition for at least four signs, stencils, or graffiti pieces (e.g., 2 official corporate/military warnings and 2 spray-painted resistance messages).
- Branch-and-Bottleneck Player Agency Hook (
GD.17.3):- Detail one meaningful gameplay or narrative choice the player can make during the slice (e.g., restoring auxiliary power to the transit lift vs. venting toxic gas through the maintenance ducts).
- Explain the immediate gameplay consequence and how the story branches locally before funneling into the next bottleneck.
Step 7 — Build the cross-department handoff matrix
A World Bible must bridge directly into your upcoming production sprints. Create a summary matrix linking each narrative element to its downstream assignment:
| Narrative Element / Faction Motif | Target Level Zone (for greybox-slice) | Required Props / Decals (for asset-list-pipeline) | Visual & Material Rules (for art-style-guide) |
|---|---|---|---|
| e.g., Faction A Security Checkpoint | Sector 1 Entrance Airlock | Stanchions, biometric scanner, warning decal | Cold steel, yellow hazard stripes, pristine wear |
| e.g., Scavenger Nest Tableau B | Sector 2 Broken Catwalk Alcove | Burn barrel, sleeping mat, ration tins | Corrugated rust, warm orange lighting, ruined wear |
Step 8 — Document and publish on your individual portfolio
Once the studio World Bible is published and reviewed, every individual student must publish a professional case study entry on their Google Sites portfolio under the GAD2 U2 section:
- Live Link: Link to the studio’s shared World Bible document.
- Personal Contribution: State explicitly which sections of the World Bible you personally authored or researched.
- Lore-to-Level-Art Visual Breakdown: Include an annotated visual (a concept thumbnail, mood board snippet, or top-down level sketch) demonstrating how one specific narrative rule or tableau you designed translates into 3D level geometry.
- Professional Reflection: Write a 200–300 word reflection answering:
- How does your environmental storytelling design provide narrative depth without relying on unskippable exposition or text dumps?
- How does your faction and world design fulfill Standard 15.3 (authentic representation) while avoiding monolithic tropes?
Submit
Team Submission: The producer or narrative lead submits the live link to the studio’s shared living World Bible document once in Google Classroom on behalf of the team.
Individual Submission: Each team member submits the direct link to their published Google Sites portfolio Coursework page under the GAD2 U2 section featuring their personal contribution breakdown, annotated lore-to-art visual, and written reflection.
Rubric
| Criteria | Approaching | Proficient | Advanced |
|---|---|---|---|
World Premise & Chronology (GD.18.4) | World history is vague or an unedited text dump; timeline lacks clear eras; disconnected from gameplay slice | Cohesive three-era chronology (Origin, Rupture, Present); setting applies the iceberg principle; directly frames the 5-minute slice | Exceptional historical depth and thematic clarity; setting feels grounded, lived-in, and rigorously calibrated to game mechanics |
Factions & Representation (15.1, 15.3) | Factions are one-dimensional stereotypes or monolithic tropes; motivations are purely generic “evil” | 2–3 distinct factions with grounded survival motivations, internal complexity, authentic cultural care, and defined visual motifs | Nuanced sociological depth; factions possess conflicting internal ideologies, legitimate historical grievances, and striking visual identities |
Palimpsest & Environmental Decay (GD.18.4) | Location described generically without historical layers; random prop scattering; uniform wear states | Vertical slice location clearly stratified into 4 historical layers; 4 defined wear states; 70/30 visual balance rule established | Masterful environmental logic; rich archaeological stratification where every structural alteration, scorch mark, and decay layer tells a coherent story |
Micro-Stories & Tableaux (GD.18.4) | Tableaux are missing, generic, or create overwhelming visual clutter that hinders gameplay traversal | 3 distinct, readable micro-story tableaux specified with prop inventories, wear states, and intentional spatial placement | Evocative, cinema-grade environmental tableaux that guide player line-of-sight, reward exploration, and communicate poignant human moments |
Diegetic Delivery & Agency (GD.17.3, 15.1) | Audio logs are long rambling monologues (>30s) that freeze gameplay; environmental text lacks personality; linear only | 2 punchy audio logs adhering to the 15–25s rule with in-world context; 4 graphic text pieces; branch-and-bottleneck agency hook | Flawless diegetic integration; high-urgency audio scripts with actor direction; sharp environmental signage; elegant branch-and-bottleneck choice |
Cross-Department Pipeline Utility (GD.18.4) | Document functions as isolated creative writing with no practical instructions for 3D artists or level designers | Clear handoff matrix linking lore to the upcoming Art Style Guide, Greybox Slice, and master Asset Pipeline doc | Seamless cross-disciplinary pipeline tool; immediately actionable for modelers, level designers, and audio engineers with zero ambiguity |
Portfolio Artifact & Process (3.8) | Incomplete portfolio post; missing personal ownership details, visual breakdown, or authentic reflection | Complete GAD2 U2 portfolio post with clear personal contributions, annotated lore-to-art visual, and thoughtful 200–300 word reflection | Industry-caliber portfolio presentation; professional graphic breakdown connecting narrative lore to spatial geometry, with mature creative analysis |
Notes
- A World Bible is for your teammates, not yourself: If an environment artist has to ask you “What kind of light fixtures go in this hallway?” or a level designer asks “Why would there be a door here?”, the World Bible hasn’t done its job yet. Write concrete visual and material answers.
- Audio logs must never hold the player hostage: If you write an audio log that requires the player to stop moving for forty seconds in an empty hallway, players will hate your story no matter how good the writing is. Let them run, jump, and explore while listening.
- Micro-stories are punctuation, not wallpaper: You do not need a dramatic tableau in every corner. If every room has an overturned gurney and a tragic skeleton, the emotional impact drops to zero and the player gets visual exhaustion. Use the 70/30 rule: give them quiet, readable space so the narrative moments hit hard.
- The World Bible feeds the Art Guide and Greybox directly: Everything you write here will be tested in 3D over the next three weeks. Don’t write about sprawling cityscapes of ten million people if your vertical slice is scoped to an abandoned geothermal relay station. Keep the world vast, but the slice tight.