10 Things You DIDN'T Know About Halo: Combat Evolved
10 Things You Didn’t Know About Halo: Combat Evolved
Welcome to MojoPlays and rather than finishing the fight, we’re showing where it all began as we delve into the archives to uncover the truth behind the origins of and behind the scenes secrets of one of the greatest first person shooter series of all time.
Monkey Nuts
Halo didn’t immediately start out as Halo and instead it all began as a tiny side project by Jason Jones and Marcus Lehto during Myth II development. Internally it was “Monkey Nuts”, a placeholder so embarrassing they knew they’d have to ditch it faster than a Grunt drops a plasma pistol when things get spicy. Jones renamed it “Blam!” because no way was he telling his mom he was working on a game called Monkey Nuts. This was Bungie’s first game built primarily on PC instead of Mac, and at first it was literally just Jones, Robert McLees, and Lehto slinging code on the prototype like three Spartans trying to hold a Flood outbreak with spitballs and hope. From a placeholder embarrassment that sounded like a rejected adult film title to the game that launched Xbox. Every legendary franchise starts somewhere ridiculous. Blam! indeed… and thank the Great Journey they didn’t ship it as Monkey Nuts.
Rough Drafts
As far back as 1997–1998, the Flood started as a Covenant-created “living minefield” or disease-like agent designed to crank up aggression and intelligence in its hosts, long before the ringworld or any of the deeper lore even existed. Early drafts featured a human “Empire”, pre-UNSC, whose ship crashes on the ring. Loose Marathon ties lingered with Chief as a Security Officer variant, Covenant scraps from the Pfhor, Forerunners echoing the Jjaro. However, they slowly stripped it all away for the cleaner UNSC tale we got. Just imagine Chief playing survival instructor to retro-future tribes while dodging plasma and parasitic rage-zombies. It would’ve been gloriously messy, but the final version tightened the focus and hit harder. What started as a chaotic crossover fever dream became the definitive sci-fi shooter epic. Sometimes the best horrors are the ones that survive the chopping block.
First Impressions
Steve Jobs strutted out at Macworld to introduce the then-Mac-and-Windows game, back when Halo was still a wild RTS-turned-third person experiment that hadn’t even discovered its first-person soul yet. Marty O’Donnell knocked out the iconic theme in a single day, drawing on Gregorian chant vibes inspired by The Beatles’ “Yesterday.” The demo CD literally shattered en route to the event, but a backup copy saved the day. Jason Jones was visibly nervous during the pitch, probably wondering if the whole project would crash and burn right there on stage. Bungie turned that near disaster into the soundtrack of a generation while Jobs played hype man. It’s the ultimate underdog story: nervous devs, broken plastic, and a melody that carried an empire from those early genre experiments all the way to ring-dominating glory. Without that backup, we might’ve never gotten the ring. Fate loves a dramatic save… preferably with sturdier packaging next time.
John 117
The name “John” came courtesy of Eric Nylund while writing The Fall of Reach. The “117” was Eric Trautmann’s contribution, nodding to Revelation 1:17 in the Bible. Microsoft briefly pushed “The Commando”, but thankfully cooler heads prevailed. They landed on Master Chief Petty Officer for that perfect Navy-inspired gravitas. Cortana drew heavy inspiration from Durandal in Marathon and was originally planned with a sharp British accent and far more contemptuous, rampant personality. Some lines like “sod off!” survived the switch to Jen Taylor’s American voice, partly to dodge similarity with another game she’d worked on. Visually, she was modeled after a Nefertiti statue, with green eyes and facial symbols later removed. The name evolution for both icons mirrors the game itself, it started messy, but ended legendary. Imagine pitching “The Commando” while Cortana tells you to sod off in a posh accent. Thank goodness they stuck with the strong, silent Spartan and his sassy hologram.
Beta Level
Internally known as B30, the Assault on the Control Room level was built, torn down, and rebuilt more times than most marriages. It served as the ultimate proving ground for gameplay, weapons, and that epic ring reveal. Early builds were hilly terrain testbeds packed with buildings, Marines, and gloriously bouncy tank physics. Programmer Charlie Gough casually hooked up controls to a single unit one day out of pure curiosity. Turns out, controlling it felt surprisingly good. Good enough to help shove the whole project away from its RTS roots toward third-person action and then eventually the first-person masterpiece we got. The team planned levels with humble index cards such as A30 for the intro “Halo” section, or A50 for Truth and Reconciliation shenanigans. Every frantic sprint through those corridors carries the ghost of one curious programmer discovering the joy of running and gunning. Some of gaming’s best maps, and genre shifts, came from treating design like chaotic Warthog Jenga.
Glitch Features
Here’s a glorious near-release glitch: look straight down and Chief’s head stays facing forward like he’s perpetually judging your aim. Instead of fixing it last-minute, they left it in. Machinima gods, and especially early Rooster Teeth, embraced the relaxed “talking head” pose for their many hilarious and iconic sketches. It even inspired the official “alert carry” animation in later games. Bungie turned a bug into an accidentally genius feature. Next time you’re watching old Red vs. Blue and Chief looks weirdly chill while chaos erupts, thank that one overlooked animation quirk. It’s the video game equivalent of leaving the typo in because it became iconic. Who needs perfect rigging when you can accidentally birth an entire comedy empire? Pure serendipity wrapped in MJOLNIR armor.
Shrinkflation
Deadlines hit like a Hunter’s shield slam, forcing heavy asset and layout reuse across the campaign. Several full levels were cut late, shoving story beats into quick cutscenes such as the bridge between Silent Cartographer and Assault on the Control Room. The flamethrower worked great in beta and the PC port, with enemies dropping weapons and running in panicked circles before dying, but it got dummied out for Xbox. Other losses included the human machete, an energy sword counterpart, the tri-barrel chaingun from early promos, the late-dropped Covenant “Shadow” vehicle, jetpacks which were originally key to Boarding Action, and numerous vehicles. Wild creatures like rideable thorn beasts, symbiotic blind wolves, Threelegs, Thorax, Vulpards, Sharquoi, and Keelbugs were all axed mostly over AI headaches. Though some later resurfaced in books and Halo Wars. Bungie turned crunch chaos into a living ring, proving you can still slap together a classic with whatever’s left in the fridge at 2 a.m.
LAN Multiplayer Underestimation
Bungie figured Halo multiplayer would be a cozy little college dorm thing, used only by existing LAN parties with freshmen and Mountain Dew. But, surprise! Regular people started hauling massive CRT TVs to friends’ houses, rigging up makeshift networks, and turning living rooms into blood-soaked arenas. The team was floored when folks treated it like a legitimate social event instead of niche nerd ritual. Anyone who grew up during this time can remember explaining to their family why they need to borrow the family TV for four hours of Slayer. What started as a happy accident became the blueprint for console multiplayer domination. Bungie basically invented the “bring your own monitor” meta without realizing it. So next time you’re yelling at your screen in a random match, tip your helmet to those early pioneers who lugged heavy glass just to get owned by a guy named xXEliteSlayerXx. Pure evolution, baby.
Working to the End
By mid-2001, about 80% of the script was still floating in the void. Enter Eric Trautmann and Brannon Boren from the Microsoft side, who rolled up their sleeves and knocked out the bulk of the level dialogue while the team was already running on fumes. Joseph Staten, meanwhile, was out here piloting characters in cutscenes like a deranged puppet master, manually recording every input. The result? Occasional clipping and jitter that they just shrugged and kept because deadlines don’t care about perfect animation. It’s peak Bungie chaos where half the memorable lines came from last-minute heroes while the other half survived because “eh, close enough.” Next time Chief delivers a stoic one-liner or Keyes drops exposition, just picture exhausted writers and a guy frantically keyframing awkward walks. It’s no wonder the Flood feels so invasive, they were probably stress-eating the schedule too.
Microsoft Meddling
You’d think naming the biggest Xbox launch title would be simple, right? Well yes, but also no apparently. Bungie just wanted to call it Halo. Clean, mysterious, perfect. Microsoft and the marketing folks panicked though, worried a single word might scream “religious epic” instead of “religious epic where you shoot aliens in the face.” So, they slapped on Combat Evolved like a safety label on a plasma grenade. We can’t even imagine the pitch meetings: “Guys, we love the ring, but we need people to know this is an action shooter, not some mysterious art piece.” The subtitle stuck, and honestly? It worked and eventually grew on everyone. Classic corporate save that accidentally nailed the vibe since nothing says “evolved combat” like dual-wielding needlers while your Warthog flips into a canyon. The full title ended up working perfectly for what became a defining shooter.
What’s your favorite making of fact about Halo: Combat Evolved and what’s your favorite Halo game ever? Share your knowledge and picks in the comments.
