Real World

Zero-bug release

From Halopedia, the Halo wiki

Revision as of 13:41, March 23, 2022 by PorpleBot (talk | contribs) (Text replacement - "{{Ref/Sources}} [[" to "{{Ref/Sources}} [[")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Zero-bug release or ZBR is an old school development vernacular when the development of the software transitions from planning and development to release and support phases. In reality, the term is a misnomer as unimportant bugs are still present in the final product.[1] It is the practice of developing software that is maintained in the highest quality state throughout the entire development process.[1]

It is a target set by Bungie to release Halo: Reach to the public without any noticeable major bugs. To test the game, employees are required to play for numerous hours performing tasks any normal player would perform - such as bumping into other AI. They would then re-perform the test in the same conditions another two times to confirm if it is a bug and not a general error.[notes 1]

Mentioned Bugs[edit]

Porcupine[edit]

The ambient AI for the porcupine model was unable to function in the game, so was removed from the game altogether. It had been decided earlier that only content was to be removed to solve bugs unless specifically necessary due to time constraints.[2]

Squirrel[edit]

Like the porcupine, the squirrel model was also removed from the game after it failed to function.[3]

Bug 15163 - off-centre cross hair[edit]

This bug was featured in a pre-release screenshot and featured the cross hair for the MA37 ICWS being far to the left. Generating speculation ranging from evidence to a Resident Evil 4: Wii Edition style of aiming with "Project NATAL" (the project title of the then-unreleased "Kinect") to Bungie being lazy programmers, it was revealed to be a bug in the January 29 Bungie Weekly Update. This update also discredited the rumours of Halo: Reach being made for Natal.[4]

Bug 14579 - SPARTAN gender[edit]

When a Spartan player under the "Female" gender option would suffer the effects of her shields being down, her AI player model would suddenly be replaced with the "Male" option.[3]

Bug 42748 - Custom vehicle specifications[edit]

Like earlier games, Halo: Reach custom games have the option to select specific vehicles to use. When playing on Sword Base with "Mongooses only" being selected, the map's cameras would turn into Mongooses and hang on the wall. This was due to the cameras being in the "vehicles" folder of the game.[3]

Bug 42844 - Kat[edit]

The AI of Catherine-B320 would respond to constant bumping in an order of phrases that Bungie deemed too "suggestive".[2]

Bug 52719 - Credits[edit]

After the campaign is cleared, selecting the "credits" option on the menu to replay the credits will cause the "results" menu to appear after skipping the video. This could potentially grant players extra points.[2]

Bug 55893 - Elite model[edit]

The player model for Elite players was the location of a bug. ZBR engineers discovered that rotating the player model would not move the legs, which would remain in their original position.[3]

Notes[edit]

  1. ^ "Bug" portions of the Bungie Weekly Updates refer to "Repro rate" when discussing bugs, suggesting that they tried to reproduce the results.

Sources[edit]