GAME · 2010
Halo: Reach
- Developer
- Bungie
- Publisher
- Xbox Game Studios
- Platforms
- Microsoft Windows
37 archived facts 4 topics 1 source Last reviewed Sep 2026
29 Facts From the Development of Halo: Reach
- #001
Halo: Reach was announced on June 1, 2009, with a trailer shown during Microsoft's Electronic Entertainment Expo press conference.
- #002
A press release stated that an invitation to Halo: Reach's open multiplayer beta would appear in 2010.
- #003
Halo: Reach was the last game in the Halo series developed by Bungie.
- #004
After Halo: Reach, responsibility for developing future Halo titles passed to Microsoft subsidiary 343 Industries, starting with Halo: Combat Evolved Anniversary in 2011.
- #005
A trailer released on March 3, 2010 showcased the multiplayer of Halo: Reach.
- #006
Bungie revealed parts of Halo: Reach's campaign and Firefight at E3 2010.
- #007
Halo: Reach was developed by a Bungie team led by creative director Marcus Lehto and design lead Christian Allen, while a separate team worked on Halo 3: ODST.
- #008
Bungie weighed many concepts for Halo: Reach, including a rejected sequel to Halo 3, before settling in brainstorming sessions on a prequel to the first Halo game.
- #009
Halo: Reach is set on the planet Reach during a pivotal time in the war, a setting creative director Marcus Lehto described as a rich world with a great fiction surrounding it.
- #011
Lehto recalled that creating a character-driven story for Halo: Reach was a great challenge, since players would learn more about the characters as they advanced through the campaign while the Spartan characters also had to behave intelligently.
- #014
Executive producer Joe Tung said the 'survive' component of Halo: Reach felt great to the team, and that although different versions of how it happened and different cinematic endings were discussed, the final result was a well-paced, significant and emotionally impactful ending.
- #015
Bungie initially planned to port and update existing Halo 3 assets for Halo: Reach, but the team concluded it could rebuild every asset from scratch at much higher quality without a significant increase in time, according to 3D artist Scott Shepherd.
- #016
Because Halo: Reach was a prequel, its art team could redesign key enemies, weapons and other series elements, drawing on the original concept art for Halo: Combat Evolved.
- #017
The redesigned Covenant Grunts in Halo: Reach took their shape from a sketch made ten years earlier by concept artist Shi Kai Wang.
- #018
For Halo: Reach, Bungie redesigned the game engine, the software responsible for rendering and much of the gameplay.
- #019
Bungie brought in a motion capture expert to make Halo: Reach's character animations more realistic.
- #021
To boost Halo: Reach's replay value, Bungie emphasized artificial intelligence and took a more open, sandbox approach to battles instead of scripting enemy encounters.
- #022
Martin O'Donnell composed the score for Halo: Reach, with additional music by Michael Salvatori. O'Donnell wrote the music in a somber, more visceral style because the plot is character-driven and centers on a planet already known in the Halo universe to have fallen.
- #023
The first music Martin O'Donnell wrote for Halo: Reach was played at the game's world premiere, and he used it as a starting point to develop further themes.
- #024
For Halo: Reach, Martin O'Donnell did not assign strictly divided responsibilities to the other composers. He explained that he created themes, tempos, keys, and other basic starting points, shared them with the composers, and asked them to take off if inspired; their works-in-progress were either retouched by O'Donnell or returned to the composer for completion.
- #028
Bungie projected that between two and three million players would take part in the Halo: Reach beta, a larger figure than the 800,000 who joined Halo 3's trial.
- #029
Development schedules led Bungie to release a six-week-old Halo: Reach beta that carried bugs and issues already fixed in newer builds.
- #031
Halo: Reach's beta began with an internal rollout among Bungie and Microsoft employees, numbering in the thousands of players.
- #032
When Halo: Reach's beta opened to the public, over a million people played on the first day, straining back-end servers; bugs in server clusters backed up game uploads and slowed matchmaking until the issues were resolved.
- #033
Jarrard said the beta's 16 million total hours of play time and its large-scale rollout were vital to seeing how Halo: Reach would perform.
- #034
Bungie used the Halo: Reach beta to correct mistakes, glitches and gameplay balance issues, with the studio stating that fan feedback was needed to shape the finished product.
- #035
The Halo: Reach beta automatically gathered statistics including upload and matchmaking speeds and game preferences, while Bungie found it harder to sort the more subjective anecdotal feedback arriving through emails, notes and forums.
- #036
The Halo: Reach beta produced more than 360,000 forum posts on Bungie's community forums, prompting the studio to create official threads for groups of issues to manage the volume of feedback.
- #037
Chris Carney, lead designer for Halo: Reach's multiplayer mode, recalled vocal dissatisfaction with the pistol early in the beta, but by the end of the beta the weapon accounted for most kills from newly included weapons; Bungie also ran special test matches to remove lurking variables and balance gameplay.
Sources & editorial notes
Sources for the entries on this page
- Wikipedia Halo: Reach — Wikipedia
Information from external sources is independently selected, consolidated and edited by Arka Evren. Sources are listed for verification and further reading. Encyclopedia text is used under its licence (CC BY-SA). How we work