User:BaconShelf/Sandbox

Halo Wars Community Site Archive
As of March 30th, 2018, halowars.com will no long exist. F.


 * Game Info
 * Overview
 * Skirmish Maps
 * UNSC
 * Covenant
 * Spirit of Fire (Archived 10/02/2018)
 * Timeline #1 (Archived 10/02/2018)
 * Timeline #2 (Archived 10/02/2018)

Note, the links to all the images/ renders stored in these pages still work so you can still access the lovely concept art.
 * Galleries
 * Screenshots (Archived 10/02/2018)
 * Concept Art (Archived 10/02/2018)
 * Renders (Archived 10/02/2018)

Link dumps
Just a bunch of links to various bits of concept art and whatnot I don't want to lose. https://www.neoseeker.com/halo-2/concept_art/ https://www.neoseeker.com/halo-3/concept_art/
 * http://potentialthings.blogspot.com/2014/11/recent-work-from-halo-master-chief.html (Stonetown concept art)
 * http://potentialthings.blogspot.com/2013/09/halo-4-game-modes-concepts.html (Dominion forge objects)
 * http://potentialthings.blogspot.com/2013/09/decided-to-add-few-concept-images-i-did.html (Longbow concept art) Done!
 * https://www.artstation.com/artwork/P3ogn (Evoltuions concept art)
 * https://www.artstation.com/artwork/k604x
 * https://www.artstation.com/artwork/zLdkw
 * https://www.neoseeker.com/halo-wars/concept_art/
 * http://cargocollective.com/jarradburley/halo-forward-unto-dawn
 * https://www.artstation.com/artwork/ybAXNR
 * https://www.artstation.com/prime/albums/53
 * https://davidheidhoff.com/halo-5-guardians
 * https://www.artstation.com/artwork/8PBW6
 * https://www.artstation.com/artwork/ezxNP
 * http://vfxmagazine.com/portfolio/halo-5-guardians/
 * http://davidsalaiz.blogspot.com/2015/11/h2a-elite-armor-version-1.html
 * http://www.haiweihou.com/sequence
 * https://www.instagram.com/bradwrightart/
 * http://halo.bungie.net/Projects/Halo/default.aspx
 * http://halo.bungie.net/Projects/Halo2/default.aspx
 * http://halo.bungie.net/Projects/Halo3/default.aspx
 * http://halo.bungie.net/projects/halo3/asset_thumb_viewer.aspx?at=52&cc=21
 * http://halo.bungie.net/Projects/odst/default.aspx
 * http://halo.bungie.net/News/content.aspx?type=topnews&cid=25650
 * http://halo.bungie.net/News/content.aspx?type=topnews&link=EngineerEvolved
 * http://halo.bungie.net/News/content.aspx?type=topnews&cid=4305
 * http://halo.bungie.net/News/content.aspx?type=topnews&cid=3908
 * http://halo.bungie.net/News/content.aspx?type=topnews&cid=3491
 * http://nikon.bungie.org/conceptart/
 * http://halo.bungie.net/News/content.aspx?type=topnews&cid=12828
 * https://web.archive.org/web/20170809233902/http://www.spartangames.co.uk/resources/downloads
 * http://halo.bungie.net/Inside/publications.aspx
 * http://halo.bungie.net/News/content.aspx?type=topnews&link=Construct_Postmortem
 * http://halo.bungie.net/News/content.aspx?type=topnews&link=Guardian_Postmortem
 * http://conceptartworld.com/news/halo-4-concept-art-by-dave-bolton/
 * https://www.artstation.com/artwork/O38Dy
 * https://www.artstation.com/artwork/mE06Y
 * http://toroskose.com/halo-wars-2/
 * https://www.artstation.com/artwork/2Ay8K
 * https://www.ajhaworth.com/#/halo-4/
 * https://web.archive.org/web/20190826141643/https://webcache.googleusercontent.com/search?q=cache:5amJaL2Y5W8J:https://belov.artstation.com/projects/1nkl33+&cd=1&hl=en&ct=clnk&gl=uk&client=ms-android-samsung-gs-rev1


 * http://coolhandgraphics.blogspot.com/2013/02/big-spaceships-003-covenant-ccs-battle.html
 * http://coolhandgraphics.blogspot.com/2013/02/big-spaceships-003-covenant-ccs-battle_26.html
 * http://coolhandgraphics.blogspot.com/2013/05/big-spaceships-003-covenant-ccs-battle.html
 * https://www.artstation.com/artwork/xZme1
 * http://www.vis-atk.com/2011/02/22/reach-destroyed-millions-dead-posters-ruined/

Project Warthog
Because I'm really creative with names. Project Warthog is my own personal project to revamp and redo the current set of Warthog pages on the wiki, to make the information within more easily digestible and less bloated. For full details of my proposal, see this thread on the forums.

Stats for REQ vehicle health can be found here (backup of the pastebin incase the tweet goes down here).

Steps

 * 1) Create a page for the M12B Warthog. The idea of this page is to split Warthog information roughly in half, allowing the M12 Warthog page to focus primarily on the Warthog version found in Halo CE through Reach (and also CEA by extent but you get the idea) while the M12B page focuses on the version found in Halo 4 onwards.. DONE!
 * 2) Create the following page(s) DONE!
 * Armored Warthog
 * Trooper Warthog
 * John Forge's Warthog maybe?
 * M914 Recovery Vehicle - Information on this vehicle design and the development process/ cut content aspect
 * M868 Tropic Warthog - Information on this vehicle design and the development process/ cut content aspect
 * M862 Arctic Warthog - Information on this vehicle design and the development process/ cut content aspect
 * M864 Arctic Warthog - Information on this vehicle design, and its use on the map Avalanche
 * Tundra Warthog - General summary page for the Tundra Warthog and what it does differently (link it to the M864 and M862 variants too. I'd imagine that the Halo 5 REQ variants likethe ones I list below would be on a similar "tier" to the Tropic/ Arctic warthogs)
 * Woodland Warthog - As per above
 * ONI Warthog - As per above
 * Urban Warthog - As per above
 * Sword Warthog
 * 1) Create an overall Warthog page as part of the wiki's wider "hub pages" project (see: Wraith, Lich, Spirit for examples). A disambiguation page will be needed too.
 * 2) Rework the Warthog navbox to better reflect the nature of Warthog variants. Likely divide M12 and M12B warthogs into different rows. DONE!


 * 1) Perhaps the trickiest, figure out a way to better divide the Warthog pages for the LRV, Gauss and Rocket designs (ongoing).
 * 2) Listed at the end but really something to do as the project goes along, use this rework as an opportunity to bring Warthog information over from Halo Nation as part of the two wikis' ongoing merger project. Links left below for future reference.
 * https://halo.fandom.com/wiki/M12B_Force_Application_Vehicle
 * https://spina.halopedia.org/index.php/M12B_Force_Application_Vehicle

Project ODST armour
Because my naming creativeness knows no bounds. Project to revamp the ODST armours part of the site to resemble the MJOLNIR armor pages more, because why do Spartans deserve cool pages alone?

Steps
Creation of the following pages;
 * ODST/UA personal protective equipment (AKA Mickey's armour)
 * ODST Sharpshooter Battle Dress Uniform (AKA Romeo's armour. Needs a better name plus a source for said name)
 * ODST/Bullfrog Battle Dress Uniform (AKA the Bullfrogs' armour. Needs a better name plus source for said name)
 * S-1 ONI Recon Battle Dress Uniform (AKA Dare's armour)
 * MJOLNIR GEN2/ ODST (needs a better pagename - possibly ODST-class mjolnir to cover the MKV and MKVI stuff too)
 * Mark 117 chest plate
 * M/LBE hard case
 * Mark IV/LBE-AA field case (not technically ODST, Jorge's backpack but including anyway)
 * UA Collar/ Pauldron

Early development
In 1997, Bungie had just finished Myth: The Fallen Lords and was beginning the development of Myth II. During this time, Bungie only had 12-15 employees in a small office in South Halsted, Chicago, when Marcus Lehto was brought on board to work with Jason Jones on a small "side project" then-known as "Armor". This project was at least in progress by the time the "Armor" trademark was filed on September 24, 1997. This side project was the origins of Halo: Combat Evolved, originating as an RTS due to thinking Myth would be better if it were science-fiction and Starcraft would be better without resource management. Due to Bungie's interest in physics to provide gameplay, they wanted the vehicles to feel like vehicles and move on 3D terrain. This integration would be based in the Myth engine, and was later referred to as "basically Myth in a sci-fi universe." This prototype would change name from "Armor" due to the need to avoid the game actually shipping with that title, and would be referred to internally as "Monkey Nuts" as to ensure the game would not actually ship with that title. "Monkey Nuts" was quickly changed to "Blam!" as Jones didn't want to tell his mother he was working on a game called "Monkey Nuts". The trademarks for "Blam.net" and "Blam.org" were filed in March 1998.

The initial RTS prototype was built with an isometric camera view, though experimentation with certain features allowed a third-person camera to be attached to units for control including the soon-to-be Warthog and Marines. The fun of using the Warthog vehicle led to the camera getting closer and closer. The initial revisions of what would become the Master Chief at this time were simple ~400-polygon models nicknamed something along the lines of the "future soldier", designed to be a supersoldier much like the final Master Chief, but deployable en-masse on the battlefield. These RTS versions of the game had no story and were purely designed for multiplayer, though by late 1998/ early 1999, the game had fully morphed into a third person shooter. Jaime Griesemer was hired in mid-1998 at which point the Halo team was 8-9 people mostly working on the game engine. By this point, the game had one assault rifle that could fire grenades and a small boat called a "Doozy", though Griesemer soon began creation of the shotgun and sniper rifle. The multiplayer mode had a 4v4 deathmatch mode, and the staff would often stop development at 4pm every day and play for the evening. As development progressed, Bungie would eventually move offices to the north side of Chicago to be in a nicer area and nearer to Marty O'Donnel's studio.

Macworld and official unveiling
On July 21, 1999, during the Macworld Conference & Expo, Steve Jobs announced that Halo would be released for Mac OS and Windows simultaneously. Before this public announcement, game industry journalists under a non-disclosure agreement had previewed the game in a private showing during E3 1999 - mid-May of that year - and were reportedly amazed. However, the game was still nameless and thus Bungie hired a branding company to help them name the game. The company and Bungie generated hundreds of names including "The Santa Machine", "The Crystal Palace", "Solipsis", "Hard Vacuum", "Starshield", "Star Maker", "Age of Aquarius" and "Red Shift". However, the name the team ultimately settled on was "Covenant", and this name was given several logo treatments. However, one artist - Paul Russel - thought the name was "stupid" and came up with five or six other names, including "Project: Halo". Few people at the studio liked the name at first, as some thought it was too-religious and that it didn't particularly sound like an action game. However, when Russel wrote down the name on the whiteboard in the studio, the name "clicked" in a way that was simple, and described the intent of the universe while maintaining a sense of mystery. Bungie also teased fans with a Blam! mention on their webcam, and on May 20th a Myth II fan site was suddenly updated with what would become the Blam! project's final name - Halo. The trademark for Halo was filed in February 1999.

Prior to the 1999 Macworld conference, however, then-executive vice president of Bungie Peter Tamte joined the company due to a wish to help an entreprenueurial company grow following Bungie's setbacks in 1998 and the disastrous release of Myth II. Tamte was a former-Apple employee, and one of his first actions was calling his old boss - Steve Jobs - to ask him to introduce Halo to the world. Joseph Staten, Jason Jones and Tamte went to the Apple HQ to pitch the demo to Jobs - with Jones presenting and Staten there in case the demo didn't work. The OpenGL technology used on the soon-to-be Mac didn't work yet, and the demo was shown to Jobs on a PC just twelve days before the game was set to be announced for a Mac release at Macworld conference. By the Friday before the Macworld showing, it became clear that the studio wouldn't be able to get sound working on the Mac, and thus Martin O'Donnell was tasked with creating a soundtrack that could be played from a CD. The instructions given to him by Staten on the Saturday before the conference were the words "Ancient. Epic. Mysterious.", and Marty began brainstorming melodies, settling on the now-famous gregorian chant. The piece was recorded on the following Monday and burned onto a CD for presentation in New York the following day, before someone promptly stepped on and broke the CD in New York. Luckily, Marty had a backup.

The Macworld demo was still being created on the hour-and-a-half flight from Chicago to New York, completely in-engine. On Tuesday, July 21, Jason Jones went on stage with Steve Jobs to show off the long-awaited Halo demo to the world, visibly nervous due to a fatal bug that could appear and crash the game on startup. Luckily, the demo went off as planned and Halo was unveiled to the world as intended. The creation of this trailer would ultimately sow the seeds of what would become the Halo universe, bringing the Master Chief character to life and giving the Covenant a reason for existing. The same day, Bungie officially announced the game with the following synopsis;

Despite this, the primary issue remained that the gameplay footage seen at the Macworld conference was almost everything the studio had working at the time. At the time, the game promised a seamless world without levels or loading screens, open terrain, fauna, flora, weather, celestial events and more. Ultimately, many of these features would be cut for various reasons, but the large expansive levels and seamless transitions from indoor to outdoor environments - considered revolutionary at the time - would remain in the final release.

Microsoft acquisition
Despite the hype surrounding Halo and Bungie's success in announcing it, the company was undergoing financial struggles due to the less-than-successful launch of Myth II - the game had an installer bug that forced Bungie to recall copies of the game so it could be fixed. A month following the Macworld unveiling of Halo, on August 13, Bungie announced they were entering into a publishing partnership with Take Two Interactive, and would begin to see their games published on consoles - where before Bungie had primarily been a PC game developer. Bungie would handle publishing in North America through Take Two's framework, while the two would co-publish games in Europe and Asia. Around this time, Microsoft had begun work on the Xbox, and then-Microsoft Game Studios head Ed Fries was tasked with building up a portfolio of games for the console's launch in fall 2001. When he received a call from Peter Tamte about Bungie's financial situation, he was extremely interested. Take Two invited two of their leading studios - Bungie and Rockstar Games - to meet with Microsoft in January 2000. Alex Seropian and Tamte later agreed that joining Microsoft would be good, particularly as Seropian believed that if Bungie was going to lose their independence - as was the case with Take Two - they may as well fully merge so they can try and have as much a say as possible.

However, Bungie was still in a deal with Take Two, and thus Microsoft and Bungie negotiated that Take Two would retain the rights to Bungie's previous properties and the other game being developed by Bungie, Oni, while Microsoft would keep Bungie itself and Halo. Microsoft announced their Xbox console at the Game Developer's Conference (GDC) in March 2000, to which Bungie later stated their interest in working on the platform. At this time, the Microsoft acquisition was still not complete, and speculation remained that Halo would be ported to other consoles such as the Playstation 2. , though Bungie later said "We never got it running on PS2 anyway". The buyout was announced on June 19, 2000; Microsoft had acquired Bungie for around $30 million and Halo would become an exclusive for the upcoming Xbox console - much to the dismay of PC and Mac fans. Bungie began a restructuring, moving their officers to Redmond and designer Joseph Staten joining the cinematics team.

Continued development
Even amidst the negotiations to move to Xbox, Bungie once more showed off Halo at E3 in May 2000, showing off a new trailer showcasing a deployment of Marines on the titular ringworld. Like the Macworld conference, the demo was finished at the 11th hour, with Marty o'Donnel finishing the music and burning the DVD just two hours before departing for the conference. This trailer would mark the appearance of several new vehicles and equipment; the Elites, Pelican dropship, a sniper rifle, the energy sword and the first appearance of the Master Chief. Previous builds of the game had featured multiple SPARTAN supersoldiers as merely one type of infantry, but now the Master Chief was a singular character. The Master Chief shown in the E3 2000 build would also bear armour much closer to resembling the MJOLNIR Mark V found in the final game, albeit with a small antenna and other slight differences. The trailer would also mark the first appearances of the Covenant Wraith tank and the "Spectre", the latter of which would later be cut from the final game. The Warthog additionally featured a mounted rocket launcher later reminiscent in design of the Gauss Warthog featured in Halo 2 and the Rocket Warthog later featured in the Halo: Combat Evolved PC port. A press kit handed out at E3 2000 estimated the game was "60% complete", while a later article claimed that the only components now missing were mission design and AI.

The game organically evolved to become about the man behind the gun, though the team didn't know precisely who that was yet. As the game currently stood, the third-person camera felt too removed from the player, and thus the decision was made to bring the game into first-person. Jaime Greisemer began properly delving into how to build a first-person control set for console controllers, and ultimately implemented aim assist and the ability to only carry two weapons but switch between them with one button - features standard in shooters now but revolutionary in 2000. This was easier on both the controller, due to having fewer buttons, and on the console, as not as many models and textures would need to be loaded in. By May 26, 2000, the team was investigating first-person though hadn't committed to it yet. Jason Jones had previously opposed the switch to first-person when engineer Charlie Gough attached a camera to the tank's turret in the RTS days of the game's development, after his experience with creating first person games six years prior. Luckily, graphics technology had advanced enough that he was sold on the idea, and Halo's format switched once again from third to first person shooter.

Over the month following the Microsoft acquisition, Bungie moved campus to Redmond. To make sure they left Chicago with a bang, Seropian and Jones went back to the first Bungie office, an old basement apartment, and offered the now-current tenant $1000 to let them have a farewell party there. With the switch to working on Xbox, Bungie now had an arduous task of bringing the game they'd developed so far for PC and Mac to work on the Xbox. This was a blessing and a curse, as it meant the team only had one hardware platform to worry about making the game for, but the Xbox devkits had not been given to Bungie yet and the timescale for the game's development had been rushed, with a little under a year to make the game. The switch to first-person and the Xbox platform would force a radical crunch period on the studio, with "90% of the game" being made in just nine months prior to ship. By September of 2000, Bungie still hadn't started work on the campaign of Halo.

Combat Evolved
Over the summer following E3, little info was released about Halo, though some tidbits of information emerged such as a screenshot of the Hunter enemy, the then-unnamed (and later cut) Engineer and repeated assurance by Microsoft and Bungie that Halo would come to Mac and PC. Eventually, Matt Soell began posting weekly community updates to keep track of progress on the game. revealing that campaign brainstorming began in December. The Redmond studio in which Bungie was now located was designed by Microsoft to be programmer-centric, with closed offices and such that the Bungie team hated, preferring a more open and collaborative working environment, leading to the Redmond studio having the walls and dividers ripped out. This led to tensions between Bungie and some of the other Microsoft teams working there. Eventually, Bungie mandated that regular Microsoft keycards in the building wouldn't grant access to the studio to ensure the development could move smoothly.

During this time, Microsoft hired a marketing company to talk to the senior Bungie staff, with a trailer cut together featuring fast cuts, action and heavy metal. The takeaway the company and Microsoft executives wanted was for Bungie to change the name "Halo", listing a variety of reasons why that Bungie heavily disagreed with. This back-and-forth lasted for several months until eventually the Microsoft team told Bungie they were giving the game a subtitle - "Combat Evolved". Bungie didn't like the name, but were able to ignore it, leading to the final shipping name of Halo - Halo: Combat Evolved.

Early story and setting drafts
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. 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. 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. This planet was to have been named "Solipsis", one of the names suggested as the game's title during development. 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.

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.

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.

One campaign level would involve volcanoes

saving link for later - https://medium.com/@Oozer3993/the-making-of-halo-how-combat-evolved-from-blam-part-2-6bfeabde0f90

Multiplayer
The studio played a lot of multiplayer in development, but for a long time the terrain seen in the Macworld demo was the multiplayer map.

Transparent images
As part of the concept art revamp I'm restoring the original artist-uploaded images to the wiki rather than cropped pngs. The crops are stored here for archival purposes should they be needed then.