Halo Story Bible
From Halopedia, the Halo wiki
- "It is the ponderous collection of lies, damned lies, and half-truths from which the entire Halo Universe is constructed."
- — Robert McLees[1]
The Halo Story Bible, often shortened as the Story Bible, is a reference document created by Bungie to record information about the Halo universe for easy reference. As a developer's text, the Story Bible contains information to ensure consistency throughout the development of the Halo franchise.[1]
The story bible originated as a document that could be printed as a series of ringbound folders, though over time has since expanded into an internal wiki for use by developers at Halo Studios following Bungie's departure from the franchise.[2][3] This internal wiki is named the Halo Library, after the eponymous locations in the Halo games.[2][4]
Overview[edit]
Bungie Story Bible and Halo Movie Companion[edit]
- " You have read the official Halo Bible, haven’t you? Sadly, neither have I nor most of the millions of fellow Halo fans. As you may know, reading the Halo Bible is a privilege reserved for an extreme few who have an explicit and authorized “need to know”. The rest of the world is left to think, theorize, question, ponder, speculate and generally “float and sputter”."
- — Recon Number 59 on Bungie.net.[5]
The Story Bible (also known as the "Bungie Story Bible")[1] originated during the production of Halo: Combat Evolved as part of supplementary material produced to support the game and other media like the novels. After Bungie's acquisition by Microsoft in 2000, Microsoft brought in the Microsoft Franchise Development Group (MSFDG) to help develop the world of the game. Eric Trautmann, Brannon Boren, Doug Zartman, and Halo: The Fall of Reach author Eric Nylund were responsible for creating the original Story Bible document alongside Bungie.[6][7][8] Eric Nylund used the Story Bible extensively while writing The Fall of Reach.[9] The strained relationship between Microsoft and Bungie in this period meant that Bungie almost cancelled The Fall of Reach, escalating into a confrontation in which Trautmann threatened to delete his documentation, something only resolved by the intervention of senior Microsoft executive Ed Fries. Ultimately Trautmann and Boren continued to work on the Story Bible in exchange for writing and editing dialogue for Combat Evolved, though this tension remained and Trautmann eventually ended his involvement with Halo after the release of The Art of Halo: Creating a Virtual World.[10][11] While writing Halo: First Strike, Nylund credited the work done by Trautmann and Boren for making his job much easier.[8]
After Trautmann's departure from the series, stewardship of the story bible became the domain of Robert McLees (one of the artists who had been instrumental to Combat Evolved and Halo 2)[1] alongside Frank O'Connor.[12] McLees noted that in the studio's early days everyone "wore multiple hats", so he had always been involved in writing to some degree, but fell into the role more as production continued.[1][13] During the production of the Halo film around 2005, a section of the story bible titled the Halo Movie Companion was produced by Bungie for Peter Jackson, WingNut Interactive, and WETA Workshop to use as reference detailing the various aliens and technology of the Halo universe.[14] The Halo Movie Companion was produced by Bungie's community team (including Lorraine McLees) in collaboration with an external studio, Kick Design. McLees later noted that much of the material in the early years of the franchise had been produced without much oversight from Bungie due to the rapid pace of production, so the Halo Movie Companion was the first time that the studio had ever properly sifted through their archives and publications to create a cohesive internal document.[15]
When writing entries for the bible McLees would often consult other staff members at Bungie for their expertise, particularly if they had been instrumental in the creation of certain elements of the fiction, or other times make up content himself based on the needs of production and the questions asked by artists. McLees also noted that aesthetic satisfaction and "feeling good" was a priority for him over being specifically accurate to science, economics, or history. Similarly, he also noted that he had no qualms with overwriting elements of the fiction that he considered "crazy bad" such as the "110mm rotary cannons" described in First Strike. On the other hand, information that could be sourced from game assets (such as sizes, speeds, and so forth) was generally kept.[1] Joseph Staten also consulted with McLees and O'Connor, the "keepers of the story bible", while writing the 2007 novel Halo: Contact Harvest.[12]
Starlight Runner story bible (2008-2010)[edit]
In 2007 Bungie split off from Microsoft and became an independent studio again after seven years. Part of this agreement stipulated that Microsoft were to keep the Halo intellectual property, which would remain under development by a new dedicated studio 343 Industries. Around 2008 Microsoft contacted a veteran transmedia specialist company Starlight Runner for the task of assembling a new and updated Halo Story Bible. According to Starlight Runner's CEO Jeff Gomez, assembling the new Halo Story Bible was one of the biggest challenges of their career, accounting for everything seen in the Halo universe up until that point and one of the largest such story bibles they had ever created.[16] The Starlight Runner story bible was around 2,000 pages in length, with Gomez citing the task of linking the Forerunners to the modern Halo story in a satisfying manner the most difficult aspect of production.[17] Christopher Schlerf worked on the Starlight Runner story bible around this time, and later joined 343 Industries as the lead writer on Halo 4.[18] Overall the writing process for Starlight Runner's story bible took around a year and a half.[19]
During a panel at PAX for Halo 3: ODST's production in 2009, Joseph Staten stated that, if printed and stacked, the Halo bible would be around 12-13" (30-33cm) in height.[20] Staten also noted that during the later years of Bungie's work on Halo they collaborated with 343 Industries to create, update, and maintain a joint story bible with them, through which projects like ODST (and presumably Halo: Reach) could be included.[21]
Under 343 Industries, custodianship of the Story Bible remained the duty of Frank O'Connor, who had moved from Bungie to the new studio and now held the title of Franchise Manager. Around 2010 the bible was still a physical document which was printed and bound across four black-and-silver looseleaf binders which were kept locked inside a metal cabinet in the studio. These could only be accessed by O'Connor, and specific sections were sent to external authors when working on Halo material as-relevant to their projects. The Forerunner Saga author Greg Bear was sent a section of the Story Bible that weighed 10 pounds (4.5 kg) and was watermarked with unique codes so that any leaks could be traced back to their origin.[22] Starlight Runner's story bible, alongside Bungie's Halo Companion for the Halo film project, were provided to the studios involved in the production of Halo Legends for use in creating those animated shorts.[23][24] According to O'Connor, the release of the Halo Encyclopedia (2009 edition) was not a release of the story bible,[25] though the book's editor Tobias Buckell was provided portions of it for use in his contributions to both it and his other stories Halo: The Cole Protocol and Dirt.[26] In a 2013 keynote speech, O'Connor estimated that around "85%" of the Story Bible's contents were public knowledge.[27]
Halo Library[edit]
- "You have Halopedia and Halo Nation, those are the public wikis, we actually have an internal one for us. We have the Library and the Index, which is a repository of information - everything from images and concept art to just full encyclopedic articles, and in those encyclopedic articles we have information on stuff that is not public you know, holes that are filled in, information that maybe is for a future telling or is fodder for a different time."
- — Jeff Easterling discussing the internal wiki at 343 Industries in 2018.[28]
343 eventually formed the Franchise Team within the studio, bringing on writers Jeremy Patenaude, Jeff Easterling, and Kenneth Peters to oversee the Halo canon. In 2023 Patenaude left 343 Industries and