Time sure does fly when you’re having fun. Conversely, I’ve found that it tends to drag a bit when you do nothing but stare at the Xbox One’s marketplace screen for hours on end, salivating in anticipation of that glorious moment when the Halo 5: Guardians game tile finally appears in the new releases section. As the old adage goes, a watched kettle never boils, and the same idea is true for digital games. Well, not literally I suppose, what with kettles and boiling water and how not checking the download never…okay fine, it’s a bad analogy. The point is, with only a few hours left to go before the release of Halo 5: Guardians, hype levels for the new game are through the roof. Well, through my roof anyway, and let me tell you, these roofing bills are fucking expensive.
To pass the time between roof repairs and eye watering sessions of endless screen staring, I’ve been gradually getting my Halo fix via alternative means. Namely, I’ve been catching up on a variety of exciting goings-on in the Halo universe by reading a bunch of the latest books and comics that have hit digital and physical store shelves. You see, being a bookworm bastardo, one of the things I particularly love about the Halo franchise is how it has gradually spawned a detailed and rich expanded fictional universe that massively enriches the basic narrative told within the confines of the games. While the main plot of the series is usually experienced from behind the familiar golden visor of the Master Chief, in my opinion the best stories of the Halo universe are instead explored from the eyes, cameras and tentacles (seriously) of the far more interesting characters (sorry Chief) encountered in the books.
While it’s understandable that the cerebral storylines of the novels wouldn’t really work at the breakneck pacing the games require, I sometimes feel that it’s a bit of a shame that the more unique character-driven stories of the Halo universe are relegated to the comics and books, a place where the majority of fans won’t experience them. That’s not to knock those mediums at all (hell, I’ve been lapping them up like a thirsty Unggoy for years since they first started), but for a series that’s first and foremost a video game franchise, it’s hardly surprising that a large part of the game’s fanbase just simply aren’t going to want to go and trawl through all this extra narrative material to get clued up on the Covenant, Crawlers and carbines. Oh, those sweet, sweet carbines.
Hell, it’s certainly not what you might consider a bit of light reading; alongside the six core Halo games, there are currently twenty novels, eight comic series, a podcast radio play, a collection of anime shorts, two live action TV series and a plethora of online ARG sites. Bearing this sheer quantity of material in mind, perhaps the most impressive thing about all of these expanded extras is that they’re all officially canon. With the exception of one delightfully daft Dragonball Z-esque episode of Halo Legends, everything in the expanded universe is written and designed specifically to be officially canon with respect to the story and events told in the games. Pretty impressive for a series that’s been going strong for the last fourteen years and counting huh?
So just why exactly am I prattling on about the Halo expanded universe here? Well, since 343 Industries inherited the Halo mantle from original creators Bungie, they’ve notably tried to cross over more of the giant lore library of the expanded universe into the realm of the games. While this is a very cool thing for a total square like me who’s thumbed their way through years of supplementary lore materials, it’s not always clear to the average Halo fan who’s not even read this wealth of extra materials just what exactly is going on at times.
This was a common complaint voiced by fans after the release of 2012’s Halo 4. That game’s inclusion of a significant chunk of supplementary plot material from outside the core games rankled with a number of players, and looking back at the game now, it’s easy to see why. At times, it can feel like the game expects players to be well read up on the developments that have taken place in the intervening years between the events of Halo 3 and 4, and doesn’t ever really pause long enough to bring those who are unfamiliar with said events up to speed. While this approach certainly made for a thrilling and streamlined gameplay experience, narratively speaking it meant that a lot of important but nerdy details were left out, and many players were left in the dark.
So, to butcher some time before the arrival of Halo 5, I thought I’d momentarily tear my bloodshot eyes away from the TV screen and repeatedly thump my head against this keyboard a bit to put together five daft pointers about the expanded Halo universe. Who knows, a few of them may even to be slightly useful as background context for the new game…maybe.
Specifically, I’m going to be looking at tidbits of info that aren’t covered in particular detail in the games themselves, or are otherwise just plain skipped over in the interest of time; small nuggets of knowledge that might just suggestively tickle away at your swollen curiosity glands in-between bouts of gunfire, grenades and ground pounds. It goes without saying then that I’m going to be discussing a fair few spoilers (a pretty major one right from the off in fact) so consider this your official klaxon-sounding SPOILER WARNING!
Still with me? Okay, with that disclaimer out of the way, it’s time to put down those BR85 Heavy Barrel Service Rifles and let me lore you to death. Speaking of which…
- The Didact is Dead…Probably
Look, I did warn you that the first one was going to be a biggie, so don’t give me that look. Remember that big bad Forerunner overlord dude from Halo 4? The nasty six-fingered fellow with telekinetic abilities who commands a synthesised robotic army and is packing some mean-looking incisors to boot? Well, he’s as dead as a digitalised dodo. At least, I think he is anyway – allow me to explain.
Although we see the alien antagonist plummet into the ominous orange eddies of The Composer in the finale of Halo 4, his ‘death’ actually occurs in the comic Halo: Escalation Volume 2. As the title suggests, ‘The Next 72 Hours’ is a three-part story arc that takes place immediately after the climactic events of Halo 4’s campaign. Master Chief and his fellow Blue Team compatriots – Fred-104, Kelly-087 and Linda-058 – are deployed to Installation 03 to investigate the sudden loss of communication from a science team working under the supervision of Black Team (the same specialist ONI Spartan team encountered in Halo: Blood Line as a matter of fact).
The Blue Team buddies arrive on the scene to find that things have gone just a tad pear-shaped at the unresponsive science camp. The scientists are dead, Black Team are dead, and the place is crawling with enough Promethean pests to warrant a prolonged visit from Rentokil. What a cracking start eh? Shortly after defeating their attackers, Blue Team then discovers a structure known as The Composer’s Abyss, which houses a slipspace portal to The Composer’s Forge, the original resting site of the deadly weapon the Didact used to try and digitise the Earth’s population.
Going through the Portal to the Forge, John comes face to face with the dastardly Didact once again. You see, it turns out that after falling through The Composer’s portal, the Didact was warped to Installation 03, where he’s eventually encountered by the rather puzzled Spartan Black Team. Being the cheerful chappie he is, the Didact proceeds to tear apart the Spartans and scientists, and is currently in the process of repairing Installation 03 to use it against humankind, the slimy bugger.
Being purveyors of righteousness and whatnot, Blue Team leap into action and try to stop him. However, they are easily overpowered by the Didact’s Jedi-like mind powers and reactive armour, which gradually becomes immune to their basic ballistic weapons. Despite putting up a valiant fight, the mighty Blue Team are thrashed.
Just when things are looking pretty grim for Johnny and the blues though, the monitor of The Composer’s Abyss, 859 Static Carillon, joins the fray. This little orb is downright appalled at the Didact’s procurement of Prometheans (apparently vaporising humans to twist them into monstrous robotic killing machines is a bit of a Forerunner no-no – who’d have thought?) and in a moment of rage, teleports the Didact away before he can deliver the killing blows. However, being a bit of a dingbat, Static has only gone and sent the Didact to Installation 03’s control room – exactly where he needs to be to fire the ring. D’oh!
While the rest of Blue Team return to their Longsword fighter, Chief gets Static to teleport him up to the ring to try to stop the Didact. Mocking the now unarmed Spartan, the Didact asks how Chief has any hope of stopping him in combat, to which Chief states he can’t; he lets gravity do the job for him instead. Ejecting the ring’s control platform, Chief and the Didact hurtle back down towards The Composer’s Forge. While Chief is safely teleported to Blue Team’s Longsword at the last second, the Didact isn’t so lucky; the final shot we see of the fearsome Forerunner is of him bellowing out a final Darth Vader-like “Noooooooooooooooooooo!” as he digitally dissolves into the Forge. Ouch.
While this certainly looks like quite a painful way to go, it’s not exactly a confirmation that the Didact is 100% dead and gone. In a debriefing to Admiral Hood back on Earth, Chief considers the Didact a ‘contained’ rather than eliminated threat, so it’s not clear whether he’s actually dead, or just trapped somewhere in the matrices of the Forerunner Domain. Only time will tell I suppose. Whether or not the Didact makes another comeback in Halo 5 or future titles is yet to be seen. But if he does, one thing’s for certain – he’s going to need a heck of a lot of after sun lotion to cool off after his digital dunking.
2. The Spirit of Fire is Still Lost in Space
The massively underrated Halo Wars by Ensemble Studios was not only one of the few examples of a real-time strategy game done well on a home console, but also a really good Halo story in its own right. Instead of shooting your way through alien hordes from the first-person perspective of a MJOLNIR armour suit, Halo Wars zooms the camera way back to a third-person overview and lets you call the shots from above as a UNSC commander. You’re still shooting your way through Covenant and Flood, just mixing things up a bit.
With regard to the game’s story, there’s some very intriguing plot threads that are suggestively left dangling by the time the credits roll – ones that may have much bigger repercussions in Halo 5. Here’s the condensed record of events. Taking place twenty years before Halo: Combat Evolved, Halo Wars‘ story follows Captain James Cutter and the crew of the Spirit of Fire, who are sent to investigate a Covenant excavation operation on Harvest, the first human planet to be attacked in the human-Covenant war (as detailed in Halo: Contact Harvest). Touching down on the glassed planet’s north pole, the UNSC discovers that a Covenant fleet (under the command of the brutal Arbiter Ripa ‘Moramee) are sticking their jaws, beaks and tentacles into places where they shouldn’t – namely into a fancy schmancy Forerunner relic site.
Clearing out the Covenant forces at the structure, the human ground forces move in and discover a giant interstellar map. Fearing the worst – that the Covenant have acquired the location of Forerunner weapon cache – the Spirit of Fire goes in hot pursuit of the alien fleet, tracking them first to Arcadia, before eventually intercepting them inside a hidden Forerunner shield world (similar to the Requiem planet in Halo 4). Within this giant safe-like planet, things quickly go from bad to worse; it turns out that the Covenant are in the process of reactivating a massive fleet of ancient Forerunner warships. To put it lightly, if they succeed in getting them operational, it’s pretty much game over for the human race.
Realising their only hope is to play the dog in the manger card – if we can’t have the Forerunner ships, no one can – The Spirit of Fire sacrifices its FTL drive as a rudimentary bomb to destroy the entire planet and its deadly cargo. The Spirit of Fire escapes the exploding planet using some clever gravitational slingshot manoeuvres…but without her FTL drive, the ship is stranded way out in the vast darkness of uncharted space. With no means of returning home, the crew solemnly enter cryosleep one last time, and prepares for a potentially very long nap.
Hang on a second – what the hell has this got to do with the books and comics you might ask? Well, as it turns out, quite a bit actually. In Halo: Escalation Volume 1, we learn that James Cutter’s son, Daniel Clayton, isn’t all too happy about the fact that Admiral Hood and the UNSC have basically declared the Spirit of Fire as lost with all hands. Not too happy at all.
Joining up with the New Colonial Alliance, an insurrectionist anti-UNSC militia, Clayton tries to strike back at Hood in 2558 by attacking a post-war peace summit between the Sangheili and Jiralhanae on Ealen IV. Thanks to the efforts of Commander Palmer and her Spartan IVs, the NCA are unsuccessful at taking out Hood and further souring relations between the Brutes and the Elites, but Clayton is quick to push a counter-offensive by sending the UNSC Infinity a Trojan space horse of sorts. Intercepting a distress signal from the Pilgrim’s Pride, a damaged freighter with faint life signs and a rapidly venting atmosphere, the UNSC pick it up only to find the core is rigged to blow with explosives. Just brilliant right? Fireteam Majestic board the Pride, and eject the core to prevent the Infinity being blitzed. Afterwards, it’s established that the assault ships deployed from the wounded freighter during the attack came from a certain vessel called the Spirit of Fire – which leads Hood to realise who’s behind the attack, and why.
Cue obligatory flashback scene. In command of the Roman Blue during the events of Halo Wars, Hood (at this point in time just a Navy Captain) is tasked with retrieving the Spirit of Fire’s log buoy after the battle of Arcadia. Encountering a Covenant fleet enroute to the buoy, Hood disobeys orders to not engage the enemy and attacks them out of wounded pride. Though he emerges victorious from the battle, it’s at a great cost. Having sustained heavy damage, The Roman Blue has to abandon its search for the Spirit of Fire, effectively dooming the ship and her crew to the inky blackness of space. Whoops.
Tracking the assault ships back to a Covenant space station hidden in the asteroid belt of Oth Lodon, the UNSC Infinity engages Clayton’s forces, but takes an absolute battering from the station’s plasma cannon. Just when it looks like lights out for Hood and the Infinity, Clayton’s plans are foiled once again by Commander Palmer and her Spartan IVs, who lead a booster frame assault on the station to do what they do best – kick ass and take many, many names. Though he’s ultimately captured and detained in the Midnight Facility (the Halo universe’s equivalent of Guantanamo bay), Clayton swears revenge on Hood, boasting that he’ll meet again when the UNSC finally crumbles. Oh Danny boy, the cells, the cells are calling…
For all we know, the UNSC Spirit of Fire is still out there drifting away in the cold black void of space – and if the final few panels of the comic are to be trusted, there might be a few unwanted stowaways lurking on-board as well. Whether it turns up during the events of Halo 5, Halo Wars 2 or beyond, who knows, but whoever eventually finds it may be in for a very unpleasant surprise.
- Master Chief is Potentially a Reborn Version of the Iso-Didact
Greg Bear’s Forerunner Trilogy is an excellent read if you want to learn more about the mysterious Forerunner race that is at the heart of Halo‘s many mysteries. Set millennia before the events of the first game, the books chart the fall of the mighty Forerunner civilisation to the greasy, corrupting tentacles of The Flood. Over the course of the trilogy, some very provocative questions are raised in the reader’s mind, ones that are likely to have far-reaching implications for the Master Chief in particular.
There’s an awful lot of info to cover on this topic, but I’ll try to give you the whistle-stop tour. The Forerunner Trilogy is told primarily through the eyes of Bornstellar-Makes-Eternal-Lasting, a young Forerunner Builder (think an alien Luke Skywalker, only one who designs fancy buildings as opposed to working on a moisture farm) who is reluctant to go into the family business so to speak, and instead yearns for adventure and to learn more about the Precursors (the Forerunner’s fabled forebears…still following me?)
Sneaking aboard supply transport headed for Erde-Tyrene (AKA Planet Earth) under the direction of his ancilla (a Forerunner AI), Bornstellar eventually meets the Didact (popular guy huh?) who after awakening him from his Cryptum (the same big orange and black ball thing we see in Halo 4) imprints his consciousness, memories and genetic markers on the young Manipular. I’m glossing over a lot of details for simplicity’s sake here, but this basically turns Bornstellar into a second copy or clone of the original Didact if you will.
To cut a very long story short, from this point onwards two versions of the Didact exist in the Halo universe – the Ur-Didact and the Iso-Didact. The Ur-Didact is the big human-hating bastardo who players encounter in Halo 4 and the one digitised in Escalation Volume 2, whilst the Iso-Didact is the pro-human version responsible for activating the Halo array and whose last communications to The Librarian you can read in the hidden terminals of Halo 3.
So how does this all tie back to the Master Chief? Because it’s strongly hinted at throughout the Forerunner trilogy and other sources that John-117 is actually a reincarnated version of the Iso-Didact. Cool right? Here’s why.
One of the key pieces of evidence for this theory is linked to how 343 Guilty Spark, monitor of Installation of 04, interacts with Master Chief after he almost fires the ring in the ‘Two Betrayals’ level of Halo: Combat Evolved. When Chief asks whether 343 already knew the ring’s true purpose – to wipe out all life in the galaxy – Guilty Spark is absolutely baffled:
“…You already knew that. I mean, how couldn’t you? We have followed outbreak procedure to the letter. You were with me each step of the way as we managed this crisis. Why would you hesitate to do what you have already done? Last time you asked me: “If it were my choice, would I do it?” Having had considerable time to ponder your query, my answer has not changed: There is no choice. We must activate the ring.”
Out of context, this all sounds like nonsensical gibberish. However, there are answers to be found in the musty pages of the books. It’s revealed in the Forerunner Saga that 343 Guilty Spark used to be the proto-human Chakas, who befriended Bornstellar back on Erde-Tyrene all those millennia ago. Midway through their galactic gallivanting, Chakas becomes mortally wounded, so Bornstellar (the Iso-Didact at this point) transfers Chakas’ consciousness over to a monitor unit to save him. Eventually, the duo find themselves in the unenviable position of having to fire the Halo rings in a last ditch effort to stop The Flood. Moments prior to firing the Halo array, the Iso-Didact asks 343 this:
“Were it your choice, could you fire the Halo array?”
Why is this line important? Because it gives vital new context to 343’s confusing utterances on ‘Two Betrayals’. In other words, 343 Guilty Spark recognises Master Chief as Bornstellar/Iso-Didact, and is utterly confused why his friend has no apparent knowledge of the weapon system he has already fired years and years ago.
Need more evidence? You got it. In Halo 4, the theory that Chief is the Iso-Didact is further supported when Chief encounters a vision of The Librarian, the Didact’s wife and the main Forerunner Lifeworker responsible for curating and studying all life in the galaxy. Shortly before catalysing the mysterious geas (the Forerunner word for a latent genetic command) hidden in Chief’s genetic makeup, The Librarian reveals some rather interesting secrets indeed:
“Reclaimer, when I indexed mankind for repopulation, I hid seeds from the Didact. Seeds which would lead to an eventuality. Your physical evolution. Your combat skin. Even your ancilla, Cortana. You are the culmination of a thousand lifetimes of planning.”
This revelation, taken with 343’s recognition of Master Chief as Bornstellar in Halo: Combat Evolved strongly suggests that Chief is indeed a human reincarnation of the ancient Forerunner Warrior-servant known as the Iso-Didact. Fascinating stuff huh? Although all this is just unconfirmed conjecture at this point, my personal assumption is that whatever latent genetic properties that the Librarian activates in John will undoubtedly have some major bearing on his journey. Whether we’ll get more information on the Chief’s genealogy in Halo 5 or a future game remains to be seen, and while I don’t think we’ll ever get a look under that olive-green helmet of elusiveness, here’s to hoping we get further info on his mysterious heritage sometime soon.
- Halsey now has both halves of the Janus Key
Though Halo 4‘s Spartan Ops was a tedious and uninspired attempt at bringing new post-launch story content to the game, one aspect of the package that couldn’t be faulted was the fantastic quality of the pre-mission cutscenes by Axis Animation.
These weekly cutscenes from the Glaswegian studio were easily the best thing about Spartan Ops, and while the missions that followed them were often just the same hackneyed shooting galleries ripped straight from the singleplayer campaign, the pre-episode shorts told an interesting brand new and exciting story, taking place six months after the events of the main campaign.
The second batch of Spartan Ops cutscenes were where the story got particularly interesting though, with the final episodes of the season depicting an exciting clash between Commander Palmer’s Fireteam Majestic and Jul ‘Mdama’s Covenant splinter faction – the fallout of which could have a big influence on Halo 5‘s narrative.
To recap, Spartan Ops ends on the ominous note that Halsey has defected to ‘Mdama’s legion and wants revenge on the UNSC. After she’s nearly assassinated by Palmer, and loses her arm to the stray bullet, it’s kind of hard to argue with her logic. Halo: Escalation Volume 3 picks up shortly after Spartan Ops’ story, and shows how Halsey is actually going about the process of enacting her revenge by reuniting both halves of the Janus Key.
What is the Janus Key, and why is it important? Well, the Janus Key provides the real time location of every piece of Forerunner technology in the galaxy, and was gifted to Halsey on Requiem by The Librarian. She instructed Halsey to take the key to a place called the Absolute Record, and use what she finds there to elevate humanity. That’s before she was shot by a fellow human however, so now it looks like she’s going to use whatever might be there for the purposes of crippling humanity rather than progressing them. Bummer.
Now working alongside ‘Mdama as his brainy second in command, Halsey lures the UNSC Infinity to the Planet Oban, where she remotely tampers with the UNSC Infinity’s engines (using some fancy-schamncy Forerunner tech, natch) to prevent them making a slipspace jump away. Descending to the planet’s surface to determine the cause of the interference, the idiotic Dr. Henry Glassman discovers what he thinks might be the Forerunner artefact messing up the Infinity’s engines, and requests to have his half of the Janus Key brought down to him. What he doesn’t know is that the artefact is actually a fake planted by Halsey to dupe Glassman into bringing his half of the Janus Key out into the open, so it’s ripe for the taking. Needless to say, it’s not long before Glassman’s half inevitably falls into the paws/claws of ‘Mdama, and no thanks to Palmer cocking up her Halsey assassination attempt number two, the two conspirators escape.
The story arc ends with Halsey and ‘Mdama reuniting the two halves of the key, and finally acquiring the location of The Absolute Record, a suppository of Forerunner tech and goodies that really shouldn’t belong in the hands of a mad scientist with a thirst for revenge. Shitting crikey, that really can’t be good – perhaps Master Chief will have something to say about her change of heart in the very, very near future.
5. Master Chief has a Bit of a Crush on Linda-058
Okay, so this is a bit of a daft one to finish on, but what the heck. It’s subtly hinted at several times in Halo: First Strike that John is romantically interested in his fellow bootcamp buddy, Spartan Linda-058. As Linda is part of Chief’s Blue Team unit in Halo 5: Guardians, this should give them plenty of time to get to know each other way better.
Considered to be the galaxy’s best shot with a sniper rifle, Chief reckons Linda is by far the strongest and most independent of all the Spartan IIs. Praise indeed from one of the most efficient killers in the UNSC.
First Strike only has a few subtle clues about these two – a tender embrace here, a lingering glance there – but there’s enough references throughout the novel to suggest that John and Linda have a bond that’s perhaps just a teeny bit more intimate than the typical Spartan camaraderie.
As these are sexually repressed supersoldiers bred for war we’re talking about here, I doubt we’ll see a blossoming Rule 34 fan-fic romance play out between the two characters on our consoles, whether we like it or not. So while the Halo equivalent of Nathan Drake and Elena Fisher coupling probably isn’t on the cards any time soon, it’ll be interesting to see if this tantalising narrative thread will be picked up in the Halo 5 script.
Anyway, that’s enough background noise from me – enjoy Halo 5, and I’ll see you on the other side Spartans. Kick a Guardian in the face for me yeah?