Tag Archives: Xbox One

Halo Fest 2020 – Reach

Even more than with Halo 3: ODST, I was hyped-up for the release of Halo: Reach. By this time we knew that Reach was going to be Bungie’s last Halo game and between previews and Bungie’s own PR, it sounded like they had every intention of sending the series off with a bang. While I was a bit disappointed that early rumors of Reach being a more squad tactics oriented game were never realized, the game we ended up with was still my favorite entry in the series up to that point (at least, when I’m not nostalgically giving that credit to Halo: CE.) As with ODST, I only really played through Reach’s campaign once, just after its release, and I was looking forward to playing through it again. I wasn’t disappointed.

Everyone to the cave for a team meeting!
“Everyone to the cave for a team meeting!”

Despite my praise, Halo: Reach ended up being controversial to much of the hardcore fanbase for various reasons, from its lore departures from most people’s introduction to Halo fiction, The Fall of Reach by Eric Nylund, to a plethora of mechanical adjustments that, while seemingly small on the surface, drastically changed the landscape of multiplayer – from overpowered and gimmicky armor abilities such as armor lock, jetpacks, and sprint, to reticle bloom and the overreliance on Forge-built maps, just to mention the highlights. Even today Reach is blamed for killing the Halo competitive scene, beginning a downward spiral as Halo headed into the 343 Industries years. Thankfully, being relatively casual multiplayer players, me and my friends didn’t have too many complaints on this front. The game felt a little different, sure, but each iteration does, and hey, fucking jetpacks!

Halo: Reach was added as part of the Master Chief Collection almost 10 years after its original release, and of course, that’s how I played it on my Xbox Series X for this playthrough. Like MCC’s Halo 3 and Halo 3: ODST, Reach didn’t receive a remaster as much as a straight port with requisite improvements to its resolution, textures, and framerate. That’s okay, as Reach was certainly a major technical leap from Halo 3 if not one of the Xbox 360’s best looking games, period. It’s just an amazingly beautiful game all around, and it still holds up rather well today thanks to the abundance of care and polish Bungie put into it. Save for some occasionally stiff looking character animations and some odd looking facial and hair texture and lightning issues, it even manages to look fairly modern.

MY gravity hammer!
“MY gravity hammer!”

Iterative technical improvements aren’t anything new for the series, of course, but one major departure from the rest of the Halo games is the story. While still conjuring the typical themes of heroism against overwhelming odds, sacrifice, like, real loss of life sacrifice, is a huge theme in Reach. As such, the game has a much darker, more mature story than any other Halo game. Characters die, the heroes of the story aren’t conventionally victorious, and as such, Reach is utterly lost to the Covenant. Hopefully none of that was too spoilery. In fact, since this is a side story taking place out of chronological order from the main series anyway, I’ll recap the plot now. While I’m fairly vague in these plot summaries they absolutely do still contain spoilers, so skip the next two paragraphs if you want to avoid them.

The Story: NOBLE Team, a SPARTAN special operations fireteam assigned to the colony world Reach, is dispatched to investigate a blackout at a major communication hub. NOBLE quickly discovers a Covenant advanced team in the area, triggering a planet-wide emergency declaration. A short time later NOBLE participates in a reconnaissance mission that leads to the discovery of a large invasion force gathering on the planet’s surface. In response, the UNSC launches a massive preemptive strike, taking down a number of Covenant teleportation spires and anti-air batteries before progress comes to a devastating halt when the Covenant supercarrier Long Night of Solace appears. Lacking sufficient weapons to take down the supercarrier, NOBLE is dispatched on a mission to commandeer the slipspace drive from a UNSC frigate, infiltrate a Covenant corvette, and then detonate the drive close enough to the supercarrier to cripple it. Manually detonating the drive, NOBLE-5 successfully destroys the ship, though sacrificing himself in the effort. Victory is extremely short lived as an enormous Covenant fleet jumps into orbit only a short time later. NOBLE team is assigned to assist evacuation efforts in the city of New Alexandria during which NOBLE-2 is killed in action and the city is completely annihilated. With a full withdrawal now underway, NOBLE is dispatched to ONI Sword Base on a demolition mission. Fighting their way into the base, the team is led into a secret research facility built around a large underground Forerunner ruin where they meet Dr. Halsey, the head scientist behind the Spartan program. Halsey tasks the team with carrying new information that she believes will be vital to the war effort safely off world. NOBLE-3 accompanies Halsey while the remainder of the team head to the shipyard where the UNSC cruiser Pillar of Autumn is waiting to depart. NOBLE-1 sacrifices himself clearing the way for NOBLE-4 and NOBLE-6, who manage to clear the shipyard, repelling multiple waves of Covenant attackers before NOBLE-4 is killed. NOBLE-6 delivers the package to Captain Keyes but elects to stay behind to man an anti-air battery, helping the Pillar of Autumn to escape. NOBLE-6 is eventually overcome while the Pillar of Autumn jumps to safety where it is revealed that Dr. Halsey’s information is contained in the AI Cortana and that the Pillar of Autumn has just jumped to Halo Installation 04.

There are so many beautifully framed cutscenes but this one was especially poignant.
“There are so many beautifully framed cutscenes but this one was especially poignant.”

The focus on Master Chief as the hero of the series has mythologized the idea that Spartans are practically demi-gods so actually seeing them dying left and right in a Bungie developed Halo game was, hopefully, a bit of a wake up call, even if most of them being SPARTAN-IIIs provides something of an out for diehard fanboys. The events of Reach also send home how overwhelmed humanity was by the Covenant. They had the technical and numerical superiority and a fanatical cause driving them, and humanity was being systematically wiped out. Finally, I love how the end of the game brings the series full circle, with the last moments of the campaign being precisely where Halo: Combat Evolved starts. Knowing that NOBLE’s sacrifice directly led to and enabled the events of the main trilogy made it all the more effective, putting a positive spin on an otherwise somber story. It also managed to conjure up some unexpected but powerful nostalgic emotion in me, even the second time through.

Appropriately, Bungie seemed to go back to the original game for a lot of inspiration. Based on original designs, the Covenant species feel more alien and more menacing. Even those adorable little grunts are less overtly silly and are all-around tougher than they’ve ever been before. In fact, playing through Reach on “Heroic” felt a lot more like the difficulty of Halo: CE or even Halo 2 than Halo 3 or ODST. While I don’t remember being utterly stuck at any point, I definitely feel like I had a lot more back to back deaths this time around. Part of that was due to Reach’s reliance on Firefight arena style map sections where you’d need to defeat wave after wave of enemies before moving on. I know ODST is the game with the reputation for overusing this mechanic, but I honestly felt it more with Reach.

Kat and I taking our new Revenant out for a spin.
“Kat and I taking our new Revenant out for a spin.”

There were plenty of departures too. The aforementioned “armor abilities” were probably the biggest single change to the Halo formula. Replacing Halo 3’s equipment system, armor abilities allow the player to activate a single on-demand power, most governed by a recharging energy pool. These abilities are all over the place, from classics like active camouflage and the bubble shield, to seemingly simple ones like the ability to sprint or dodge roll. The biggest two additions are the jetpack, which is a little controversial but I’m personally a fan of hopping around all over the place like an idiot, and armor lock. Armor lock essentially makes the player totally invulnerable while on, while an EMP pulse charges and is unleashed once the lock is over. The player’s health and shields will also recharge as normal during the lock. In the campaign this could be useful for preventing big damage or doing an emergency recharge (although the enemy AI tends to simply stop and wait around for the armor lock to end, with feels a little stupid) but in multiplayer the ability to be invulnerable on-demand combined with the situationally usefulness of the EMP pulse altered the flow of fights in a way that many people thought was devastatingly overpowered.

Halo Reach only includes one new enemy, the barely noteworthy Skirmishers which come in several varieties, although all of the classic Covenant enemies have been re-tuned and come in several varieties themselves. Weapons wise, we have a lovely new battle rifle stand-in called the designated marksman rifle (DMR) and its Covenant equivalent, the needler rifle. There’s also a new grenade launcher and its rough match, the Covenant concussion rifle. There’s a few other new items, like Covenant focus rifle, plasma repeater, and plasma launcher, but as usual, nearly every weapon in the game has been adjusted. Reach’s additions to the vehicle inventory are even more conservative, with the new Covenant Revenant which is something like a mix between a Wraith and a Ghost, a fun new UNSC aircraft similar to the Hornet called the Falcon, and the new UNSC Sabre and Covenant Seraph fighters.

Now do a barrel roll!
“Now do a barrel roll!”

Those new fighters are specific to what is probably the biggest new feature of the game, the space sections of the mission “Long Night of Solace”. In these sections you pilot the new Sabre fighter in what feels a little like the Star Wars: Rogue Squadron games or the more freeform Star Fox levels. While I thought those sections were an interesting addition to the already good amount of gameplay variety available in Halo campaigns, some people absolutely hated it. As a personal anecdote, every time Reach comes up in conversation with my brother, he always complains about this particular mission, claiming to have been stuck on this part of the campaign since 2010. Ha! The new Falcon also gets some dedicated time in “New Alexandria”. Beyond these sections, Reach features the typical selection of levels from on-foot corridor-running CQB sections, more open on-foot areas, sections reliant on running Warthogs and Scorpion tanks, and of course, most missions mix up all of these. There’s a lot of variety in the environmental aesthetics of these sections too. It all feels appropriately very Halo and about the only thing Halo: Reach is missing is another “Warthog Run” section.

There’s a lot more I could go into about Reach: the weird AI-centered sidestory found on the datapad pickups in the campaign, the numerous changes to multiplayer including an overhauled progression system and the new epic Invasion mode, bringing back Firefight for more co-op shenanigans, greatly expanded Forge and Theater modes, etc. It’s overall one a hell of a package, and a wonderful way for Bungie to wave goodbye to the series. Most importantly, the love Bungie put into it is obvious, and while it might not have the staying power as the mainline Master Chief installments of the series, it’s story was at least uniquely impactful.

Kat is having a bad day.
“Kat is having a bad day.”

As with my last few entries, I’ll end by touching a bit on the awesome live action promotional content developed around Halo: Reach. There’s “Birth of a Spartan” which is a short that shows Carter-A259 being transformed from a young trainee into a SPARTAN-III and “Remember Reach” which depicts numerous citizens of Reach as they go about their normal lives, oblivious to the impending Covenant invasion. Neat but not essential. “Deliver Hope” on the other hand is absolutely essential! This live-action trailer shows NOBLE team in a battle to defend the colony Fumirole as they attempt to get a fusion bomb onto a Covenant battlecruiser to destroy it. Go watch it if you haven’t seen it!

I got so many amazing screenshots this time around, it really was quite an effort to not just replace all of this rambling with a huge image galley and drop the mic!

Halo Fest 2020 – ODST

When Halo 3: ODST was shown at E3 2009 I wasted no time preordering it, though I did have some minor reservations. I mean, the game was essentially a standalone expansion pack for Halo 3, a game which reasonably wrapped up the trilogy, and this game wouldn’t even feature the iconic Master Chief! Halo 3 was also 2 years old at this point, despite the undeniable staying power of its excellent multiplayer. Still, the reviews ended up being absolutely glowing, with the biggest criticism being the sticker price. Today ODST is still as celebrated for the interesting deviations it made from the core series as it was at release. On top of everything I’ll go into below, I also fondly look back on it for first introducing the “Firefight” gamemode, a “Horde mode” like cooperative wave survival mode that my brother became particularly enamored with.

Over 10 years later, I was able to easily play Halo 3: ODST again as part of the Master Chief Collection on my Xbox Series X. As with Halo 3’s MCC port, ODST didn’t receive the ridiculously thorough remaster treatment of the Halo: CE and Halo 2 anniversary editions, but the fact that it still looks so stunning today with little more than some upscaling speaks volumes about Bungie’s expertise. They were clearly at the top of their game with Halo 3: ODST, and it ages even better than Halo 3 as a result.

The boys!
“The boys!”

Since so many of ODST’s gameplay elements are related to its story, and this is a side story taking place out of chronological order from the main series anyway, I’ll start by recapping the plot. Unlike Halo Wars, which took place before the events depicted in the main Halo games and has little direct relation to their plots, Halo 3: ODST actually takes place during events depicted in Halo 2. Aside from that, it is still very much its own story, however, and while I’m fairly vague in these plot summaries they absolutely do still contain spoilers, so skip the next paragraph if you want to avoid spoilage.

The Story: Breaching Earth’s defenses, the Prophet of Regret’s carrier has taken up position over New Mombasa while Covenant forces terrorize the city streets below. In a desperate move that could help turn the tide of the war, multiple squads of the UNSC’s elite Orbital Drop Shock Troopers (ODSTs) are ordered to drop onto the ship and capture the Covenant leader. ODST fireteam Alpha-9, led by Gunnery Sergeant Edward Buck, is attached to Office of Naval Intelligence officer Captain Veronica Dare for the assault. As the fireteam prepares to drop, Capt. Dare unexpectedly orders them to adjust their drop locations to land in the city instead. As they drop, Regret’s ship performs a surprise low orbit slipspace jump, resulting in a destructive shockwave that sends the fireteam’s drop pods wildly off course. The members of Alpha-9, now completely scattered, individually make their ways through the wreckage of the Covenant occupied mega-city to regroup. One of the members of the fireteam, picking up Dare’s radio signal and subtly guided by Vergil, the city’s Superintendent AI, locates Capt. Dare as she attempts to infiltrate the city’s underground data center. Upon reaching the data center’s core, Dare reveals the true purpose of her mission: to secure the Superintendent AI. The pair quickly discover that the Superintendent AI has been taken over by a Covenant defector. This Huragok, a rarely encountered species of alien dubbed “Engineers” which the Covenant use as biological supercomputers, could be extremely valuable in learning the purpose of Regret’s attack. Escorting this renegade Engineer back up to the surface and fending off multiple Covenant attacks along the way, they eventually meet up with Buck and the rest of his fireteam and make a hasty escape from the city.

Holding out against a ton of Covenant air with nothing but a huge pile of heavy weapons.
“Holding out against a ton of Covenant air with nothing but a huge pile of heavy weapons.”

Structurally, ODST plays unlike any other Halo game. You initially assume the role of the new member of the fireteam referred to as “the Rookie”. By the time the Rookie wakes up after his violent landing quite a few hours have passed and you’re tasked with wandering the dark, deserted streets of New Mombasa searching for signs of what happened to the rest of Alpha-9. Each of the clues you find results in a flashback mission switching you from your silent protagonist to one of his much more developed (and talkative) squadmates. These missions are structured more like your typical Halo mission and, taking place in different areas and at different times, allow Bungie to really mix up the scenery and the action. Once a mission is complete, you’re sent back to rejoin the Rookie in New Mombasa, with these sections ultimately functioning as something of an abstracted hub area. Very cool.

The Rookie surveying the New Mombasa streets.
“The Rookie surveying the New Mombasa streets.”

The New Mombasa streets area has a couple of other interesting tricks up its sleeve. First, the expansive map is more or less wide open. While you’re guided to the location of each subsequent clue, it’s only by a waypoint, and there will be multiple ways to reach it. You’ll probably end up taking different routes whether you want to or not, as navigating the maze-like city streets isn’t easy, often requiring the use of the in-game map. Along the way you can choose whether to engage the Covenant patrols you encounter or attempt to sneak around them entirely. You can even find the aforementioned clues and play their associated missions totally out of order if you want to.

More importantly, these New Mombasa sections have an absolutely unique tone. As the Rookie, you’re all alone in the dark, rainy city streets. Remnants of the day’s earlier conflict surround you: ruined buildings, destroyed vehicles, and dead UNSC and Covenant soldiers alike. It conjures a lonely, bleak feeling. The Superintendent AI’s poltergeist-like attempts to guide you only add a further creepy layer to this. There’s also something of a light survival feel to these sections, as ammo is scarce; your UNSC weapons will probably be depleted after your first few encounters, forcing you to scrounge for Covenant weapons and ammo. The pacing is altered by all of this too. In the proceeding Halo games you’re shuffled from mission to mission with an urgency that is, I suppose, appropriate to the epic task at hand. You know, saving the planet and whatnot. In the New Mombasa streets, however, there is no such urgency. You’re just one person, completely isolated. It all feels very grounded and very personal.

A squadron of Banshees fly by the remains of the space elevator.
“A squadron of Banshees fly by the remains of the space elevator.”

The graphics and sound are a large component of why this all works. The lighting and shading certainly conjure a particular mood, but with ODST’s soundtrack they’ve incorporated a greatly expanded variety of different musical influences, from the more traditional Halo sounding orchestral tracks and electronic ambiance to smoky jazz-inspired, piano and saxophone laden pieces that sell the game’s intentionally film noir vibe. Halo has always had extremely strong soundwork, but ODST is really something else entirely. Anyone who thinks Marty O’Donnell is a one trick pony really needs to stop what they’re doing and go give the ODST soundtrack a listen. Right now!

Gameplay wise, Halo 3: ODST is built directly on top of Halo 3 and plays more or less the same, but it’s hard to mark the game down for that. I mean, that is one damn fine foundation. Some of the few differences between the two games relate to the fact that you’re not playing a literal supersoldier like Master Chief. I recall Bungie making statements before ODST’s release that perhaps oversold that just a little; that as a normal human, you’d be weaker and less capable and that suddenly even the previously laughable grunts would be fearsome opponents. That sort of thing. Instead, there is another new health system, this one feeling similar to Halo: CE’s with a shield-like recharging “stamina” layer and a core health pool that is only refilled with health packs. Unlike Halo: CE, however, these health packs are relatively plentiful. There’s also no hijacking vehicles, no dual wielding, no use of Halo 3’s special equipment, and no radar.

New Mombasa Streets: VISR off.
“New Mombasa Streets: VISR off.”

New Mombasa Streets: VISR on.
“New Mombasa Streets: VISR on.”

Bungie giveth as well. As an ODST your standard armaments are a new silenced version of the submachine gun and, something of a throwback to Halo: CE, a lovely new silenced magnum pistol. There’s also the VISR mode which serves as both a sort of night vision and also highlights friendlies, enemies, and certain objects with a thin colored outline on your HUD. The only negative to VSIR mode is that there’s no real reason to ever turn it off, and leaving it on means seeing only one, lesser version of the game’s lighting.

The VISR mode’s ability to highlight objects is key to ODST’s single collectible system: audio logs. Similar to the terminals of previous games, these logs are hidden throughout the New Mombasa streets. Interestingly, rather than typical voice memo type recordings, these are audio and still images recorded from security systems scattered around the city and tell the story of a single character, Sadie, and her attempt to meet up with her father as the fighting erupts. This story links directly into ODST’s overall plot, giving some insight into the Vergil AI and its fate. While I remember liking these audio logs, I could barely stand them this time around. The script feels unnatural and the voice acting and sound effects come across like a old time radio play. Sadie’s main nemesis in the story, the city’s police commissioner, is a particularly ridiculous mustache twirling villain stereotype that I just couldn’t take seriously.

At least that’s not an issue the campaign has! The voice cast is excellent, with notable TV actors including several of the core cast of Firefly with Nathan Fillion, who Buck is both voiced by and modeled after, and Battlestar Galactica’s Number Six, Tricia Helfer, voicing Veronica Dare. Say what you will about Buck’s sarcastic attitude or he and Dare’s relationship issues, but in the brief time we spend with these characters they express a lot more personality than we ever got from Master Chief, and the strong cast only helps that.

Dutch's level is a total throwback to previous games.
“Dutch’s level is a total throwback to previous games.”

I beat the game on “Heroic” difficulty, and even with the aforementioned lack of ammo and other constraints I found it to be one of the easiest campaigns so far. That’s not to say there weren’t some intense moments. The first time I ran into a Hunter I struggled like hell to take him down, depleting all of my grenades and most of my ammo in the process, only to have his buddy saunter into the room just as I was catching my breath. Sheer panic. There was also a lot more variety in the action than I’d remembered, with missions featuring a tank section, a wide open Warthog-centric level, some Banshee flying including a unique Scarab fight, and even yet another Warthog run-like level towards the end of the game. Even with its relatively short length, there’s definitely enough to make it feel like a full Halo game. While a part of me does have to wonder if you had to have played the previous games in the franchise to really appreciate it to its full extent, I personally think Halo 3: ODST is something of a masterpiece and is easily one of the strongest games in the series.

We are ODST!
“We are ODST!”

Just a quick footnote, but similar to Halo 3’s “Landfall”, ODST’s considerable promotion efforts included the absolutely awesome The Life. This live-action short shows the journey of an ODST from a young recruit to a battle hardened veteran. Compelling and absolutely worth a quick watch if you’re a Halo fan and haven’t seen it!

Halo Fest 2020 – Halo Wars

Now for a complete change of pace from the original Halo trilogy, we have Halo Wars. Despite the fact that Halo actually started life as an real time strategy game, it still strikes me as incredibly unlikely that Microsoft would have ever greenlit this. I guess they figured a console RTS had more of a chance of success with the Halo brand behind it than without, and they were probably right. Still, I didn’t know many Halo fans who were all that excited about the prospect at the time, and console FPS fans and RTS fans were mostly two different breeds. Regardless, this badass trailer produced by Blur did a lot to get the Halo fans pumped up and RTS fans (well, the ones who would condescend to play an RTS on a console) would be placated by knowing that Ensemble Studios, responsible for the Age of Empires and Age of Mythology series, utter classics of the genre, would be at the helm.

The badass cutscenes were also produced by Blur.
“The badass cutscenes were also produced by Blur.”

Me? Well, as both a Halo fan and an RTS fan (and admittedly, not a hardcore one) and having played my fair share of Age of Empires II, I was probably about as close to their target demographic as you could get. Despite this, I wasn’t all that hyped up for it, and while I did play through the demo (which I briefly talk about here, though I somehow have no recollection of) I never got around to playing the full game. While it was pretty well received by fans and critics alike, it’s reasonable to assume that a similar level of disinterest (along with numerous internal factors) would lead to Ensemble closing its doors, sadly making Halo Wars their very last game.

For this playthrough I played the Xbox One Halo Wars: Definitive Edition on my Series X. The “Definitive Edition” is a remaster of the original game released alongside Halo Wars 2. With higher resolution textures and improvements to lighting and particle effects but not a lot else, it’s essentially just a re-release. While this means it’s not going to blow you away with contrast between the versions like the first two Halo games I covered, it is, at least, very faithful to the original. The game has aged pretty well, so that’s not a problem.

Well, it certainly LOOKS like an RTS...
“Well, it certainly LOOKS like an RTS…”

I’d actually started my playthrough on “Heroic” just as I did with the first three Halo games, but I found that the effort to beat some of these missions on Heroic simply wasn’t worth it – I could beat them, sure, but it took longer due to losing units more easily, and that sapped a lot of the fun out of the experience. Lowering the difficulty one notch to “Normal” was a big improvement for me. I suppose I enjoy overcoming bumps in difficulty in FPSes a lot more than I do in RTSes, where my builds and priorities are the biggest differences in how I play from session to session rather than toying too much with tactics. That, and the kinds of scenarios you encounter in a single player campaign like this so often constrain your options for the sake of variety, not doing a great job of reflecting the full array of options present in a pure skirmish match as a result.

The console control scheme makes excellent use of radial menus.
“The console control scheme makes excellent use of radial menus.”

I think another issue was the controls. Don’t get me wrong, I think Ensemble did a fine job with translating the RTS to the console, and from other console strategy game experiences I’ve had, I think the idea that strategy games don’t quite work on consoles is total bunk – there are plenty of examples of at least passable RTSes on console. Still, I have a lot of hours playing of RTSes on PC under my belt and playing them with a mouse and keyboard is in-grained at this point. For one, I found my ability to appropriately micromanage my units lacking. Halo Wars lets you select all of your units, all of your units on the screen, and all of the units of only a particular type in either case, which is just enough to allow you to do most anything you’d want to do with a little creativity. Still, that pales in comparison to being able to quickly make groupings of specific units of mixed unit types and assign them to hot keys for later use. Interestingly, I made the same complaint over 10 years ago when I played the demo. I definitely did feel slightly hobbled by this in some of my busier missions though, and this led me to coming up with numerous cheesy strategies of deploying tons of the same unit – masses of fully upgraded Warthogs being a particular favorite of mine, being both cheap to replace when they inevitably get blown away, and hilarious to watch bound haphazardly across the map.

Continuing the trend I started with my re-play of Halo: CE, I unlocked every skull and black box collectible on each map, though chasing them down really wasn’t all that enjoyable as it was in the previous games. Some don’t appear on the map until certain challenge conditions are met, making finding them more naturally impossible, and resulting in them being a bit of a distraction from the actual goals of the mission. More importantly, the reward for unlocking them is a let down. Skulls function similarly to previous Halo games, but in the case of the black boxes, each one unlocks a single entry on a giant timeline of the events around the game. This glorious lore dump is no doubt cool for fans of the franchise, but they’re just short text blurbs – no cutscenes, not even voiceovers. A little on the weak side.

Marines clearing out a nasty Flood infestation.
“Marines clearing out a nasty Flood infestation.”

While I’m being negative, I also encountered a few bugs and other oddities during my playthrough. Probably an artifact leftover from the remaster, but in-engine cutscenes seem to run at a reduced, stuttery looking framerate, I had at least one total system crash during a mission, and on another occasion (on the same mission!) I lost the ability to control a special vehicle which made winning the scenario impossible and caused me to have to reload and lose a bunch of progress. I wouldn’t say these issues were numerous enough to ruin my experience, however, but there were enough of them to take note. That said, I didn’t have any real issue with unit pathing, which is a common complaint I’ve seen online.

There’s also the story. As this is a side story taking place out of chronological order and well before the main series, I’ll go ahead and recap its plot right here. While I’m fairly vague in these plot summaries they absolutely do still contain spoilers, so skip the next paragraph if you don’t want the plot to be spoiled!

The Arbiter is back! Only this is a different one, and he has zero personality.
“The Arbiter is back! Only this is a different one, and he has zero personality.”

The Story: As part of the Harvest Campaign, an effort to retake the planet of Harvest, having the unfortunate distinction of being the first human colonized world decimated by the Covenant, marines of the UNSC colony ship “Spirit of Fire” discover a newly excavated Forerunner facility containing an interstellar map. Using the map, Professor Anders, a researcher aboard the Spirit of Fire, identifies another human colony world, Arcadia, as being a point of interest for the Covenant. Arriving too late, the Spirit of Fire finds Harvest’s defenses breached and the colony already under siege by Covenant forces. Linking up with local defenses, including Spartan Red Team, Arcadia City is evacuated. Efforts to further repel the Covenant eventually lead the UNSC to locate concentrated Covenant activity around yet more Forerunner ruins. The UNSC push the Covenant out, though the victory is short-lived as the Arbiter abducts Professor Anders and flees Arcadia. In pursuit, the Spirit of Fire arrives at an uncharted planet being overrun by Flood, which they quickly learn is actually a Forerunner Shield World. Professor Anders manages to escape, revealing that the Arbiter planned to use her to activate a fleet of powerful Forerunner warships to help the Covenant decisively win the war. Captain Cutter approves a risky plan to use the Spirit of Fire’s faster-than-light drives to destroy the entire Shield World, keeping the Forerunner fleet out of the hands of the Covenant. Successful but now without faster-than-light capability, the Spirit of Fire’s crew goes into cryogenic storage while the ship begins the long journey home.

It all feels, eh, a little generic. I say this having already played almost all of the other games in the series, so perhaps I wouldn’t have felt that way at all if I played it at the time. It might have been utterly groundbreaking for all I know. Either way, this isn’t helped by the fact that the characters were all just a little flat. I really couldn’t convince myself to care all that about Sgt. Forge, Captain Cutter, or Professor Anders. Hell, I probably liked the Spirit of Fire’s AI, Serina, more than the lot of them. Everyone just came across as low effort archetypes to me, and I think I would have felt the same back in 2009.

One of my Spartans jacked a Scarab. Ridin' in style!
“One of my Spartans jacked a Scarab. Ridin’ in style!”

While that all sounded more than a little sour, no, I didn’t dislike the game. In fact, I felt like Ensemble did a great job representing the Halo universe. The presentation is faithful to the original games and quite skillfully executed, with the new units added doing a lot to make both the Covenant and the UNSC feel more like actual military forces than what was represented in the previous Halo games. The soundtrack is great. The cutscenes, awesome! It also definitely succeeds as a RTS, with some interesting units, tech trees, a decent amount of variety in the scenarios you’re thrown into in the campaign, and an interesting take on the classic formula, with simplified resource gathering and some other concessions seemingly made around the platform. I think one of the bigger compliments I could give the game is that I had been feeling the urge to play some classic RTS games lately and Halo Wars managed to thoroughly scratch that itch. Once completing the campaign, I dove into several skirmish matches against AI which were a ton of fun and sealed my overall positive impression of the game.

I’d say if you’re a Halo fan, you should definitely give it a chance. If you don’t have any RTS (or other strategy game) experience you absolutely might bounce right off of the game. Then again, it might also end up being one of your favorite Halo games, and your gateway into a whole new genre. Now, back to Bungie