47,396
edits
User:BaconShelf/Sandbox: Difference between revisions
→Halo CE development
BaconShelf (talk | contribs) |
BaconShelf (talk | contribs) |
||
| Line 148: | Line 148: | ||
===Early story and setting drafts=== | ===Early story and setting drafts=== | ||
Halo was | [[File:HCE EarliestFlood Concept.jpg|thumb|right|The earliest known concept art of the Flood, by Robert McLees. The full resolution was lost during the shuffle of years at Bungie, and the colour resmebles human skin more due to McLees' colour-blindness.<ref name="feast"/>]] | ||
When developing games prior to ''Halo'', Bungie's method of development was to develop their engine, then make their multiplayer gameplay feel good. This was only followed then by campaign as the final element to take place.<ref>[http://halo.bungie.org/pressscans/display.html?scan=cgw1199 '''halo.bungie.org:''' ''Computer Gaming World 1999 scan'']</ref> The development of ''Halo'' was no exception, as the rough story for the game didn't even begin to take shape until mid-199, following the Macworld trailer premiere. The first seeds of the franchise were sown following [[Robert McLees]]' creation of the then-"future soldier" (the predecessor to the Master Chief) and the Warthog vehicle, at which point he began to place himself in the year 2500, with the player at war with alien factions.<ref name="untold"/> In the early stages of the game's development, the game was to be set on a hollowed-out planet, though this soon evolved into a [[dyson sphere]] and later the titular ringworld.<ref name="AOH73"/> This planet was to have been named "Solipsis", one of the names suggested as the game's title during development.<ref name="IGNhistory"/> The evolution of the setting to the ringworld, however, inspired Paul Russel to come up with the name ''Halo'', which was then applied to the ring itself.{{Citation needed}} | |||
One campaign level would involve volcanoes<ref name=" | By 1997/1998, the [[Flood]] were already being concepted, and story ideas circulating about their role alongside the Covenant. The Flood had been designed by Jason Jones purely for gameplay, and McLees was the first to truly think about what the Flood was in the fiction. His first idea was to have the Flood be a bioweapon engineered by the Covenant, designed as a "living minefield" with which the Covenant would seed planets on their borders, in case anyone tried to make landfall. At the time the game was to be set on a planet, the concept of the [[UNSC]] did not exist yet, simply named the "Empire", later reflected in some of the earliest marketing materials published about the game's story. The story beats of what would become ''Halo: Combat Evolved'' were in place, though still undefined. In this early draft, the player and their ship would crash on a planet populated by humans not part of the Empire, with the player's technology from 2552 and the native technology from the 1950s. The player's goal would be to train the indigenous population for when the Covenant arrived. They would ocmbat the natives in the early levels, and the Covenant later on.<ref name="feast">[http://halo.bungie.net/news/content.aspx?type=topnews&link=Feast_of_Bones '''Bungie.net:''' ''Feast of Bones'']</ref> | ||
Another Flood origin, written by Griesemer, would have the Flood as a meningitis-like disease that made a life form more aggressive and more intelligent. The natives would use the Flood as a rite of passage, throwing males of-age into a mass grave in which they'd climb back out smarter and looking for a fight.<ref name="feast"/><ref group="Note">This origin is remarkably similar to the origins of the Flood and its effects on [[Pheru]] later described in ''[[Halo: Cryptum]]'' and its sequels.</ref> | |||
One campaign level would involve volcanoes<ref name="campaigndecember"/> | |||