|Box Art N/A|
|Platform Win, Xbox One|
|Publisher Microsoft Studios|
|Developer The Creative Assembly|
|Release Date Feb 21, 2017|
Halo Wars 2 feels like the relic of two different histories.
On the one side you'd find the real-time strategy genre, a collection of games that found a brief period of big-budget dominance on the PC and occasionally ventured onto consoles. RTS games spawned the current 500-ton gorillas of modern free-to-play gaming in the form of League of Legends and DOTA 2, but the more traditional model of base-and-army-building games largely languishes
The original Halo Wars also came at a time when it seemed like an offshoot of Halo into new arenas outside the FPS was natural, even inevitable. But since Halo Wars’ 2009 debut, the series has remained content to play in its own first-person sandbox as the RTS genre faded. And now, in 2017, for whatever reason, Microsoft and Halo stewards 343 have worked with RTS legend and Total War developer Creative Assembly to build Halo Wars 2, a sequel that feels positively anachronistic.
This unexpected sequel is evolutionary, rather than a departure from the original idea, refining the strangely workable controller-based inputs that made a reasonably serious RTS possible on a console. It further elaborates beyond the "select all units" battering ram that became the first game's most successful tactic — surely in part because Halo Wars 2 is, now, a genuine, honest-to-goodness PC RTS as well.
But in other respects, Halo Wars 2 seems at the mercy of its namesake's best and occasionally worst habits.
Halo Wars 2 opens as the UNSC ship from the last game, The Spirit of Fire, is awakened from an extended cryosleep in deep, uncharted space, lost and out of contact with human civilization decades after the events of Halo Wars. What they find there is more conflict, this time in the form of The Banished — a nightmarish force of former-Covenant exiles so powerful and brutal that the combined might of the Covenant could not exterminate them. The Banished are led by a giant Brute named Atriox, who is determined to destroy anything standing in his path.
This characterization seems a little thin, I'll admit, but through generous use of pre-rendered cutscenes (whose production quality is phenomenal), Atriox is fleshed out and given a tangible sense of menace and personality that I haven't seen in a Halo game in years. Halo Wars 2, like the first game, takes place to the side of a greater conflict, and the stakes are somewhat removed from the fate-of-the-universe determinations the Master Chief is responsible for. This results in something that feels more like a war movie involving two sides than a sci-fi savior epic, and the story and themes really work in a way that few shooters — even Halo — manage, to say nothing of most real time strategy titles.
The problem? Halo Wars 2 can’t quite stick the landing. While Halo Wars 2’s story is considerably more coherent than many mainline Halo entries, it adopts one of the series’ most obnoxious tendencies in an ending that avoids any meaningful sort of resolution. In mainline Halo games I’ve almost come to expect it, but here, I was surprised, and annoyed, in equal measure, especially in a game with only 12 missions — not all that many by RTS standards.
Regardless, that story almost single-handedly gave me the patience to relearn Halo Wars 2's console control scheme, because any frustration I initially felt was offset by my desire to see where things were going. Which is good, because if you're playing on Xbox One and haven't played the original recently, there's a hell of a learning curve.
From above, Halo Wars 2 looks like a traditional RTS. You’ve got one or more bases (usually) with different structures that can pump out different kinds of units and upgrades for your army, which you then use to take various objectives that generally include destroying an enemy compound.
Halo Wars 2, like its predecessor, squeezes a nearly full suite of PC RTS control inputs and commands onto a controller with only a dozen or so discrete button presses available at any given moment. Some of this is obvious — you navigate the battlefield with the left analog stick, and you zoom in and out and rotate the camera with the right. The latter is, amusingly enough, a much more intuitive option to do those things than just about any PC RTS I can remember, and I ended up rotating the screen quite a lot to compensate for the cumbersome feel of moving a cursor around the screen with an analog stick.
This specific contrivance is Halo Wars 2’s biggest problem, much as it was with the first game. It’s hard to be precise with selections with an analog stick instead of a mouse. Halo Wars made up for that with "select all units," a command available with a single button press. This became a go-to, winning strategy in the first game — pump out a blob of units, select them all, and run over the enemy. There were wrinkles, but it worked most of the time.
Halo Wars 2, however, makes this less of an option, in large part because there are often too many things happening at any given moment for one army to do all the work for you. Missions tend to have multiple objectives, many of which can be retaken by the Banished if you leave them unattended. When multiple units are selected, the group seems to move at the slowest unit speed in the bunch, and that’s just not fast enough to respond to everything that’s happening on the map at once.
Thankfully, this is all augmented by a reasonably well thought out series of modifier commands. Holding the right trigger allows for creating and accessing user-defined groups of units assigned to the d-pad, which are in turn selected by holding the right trigger and pressing the appropriate direction. Press that direction twice and the camera will focus on those units. Without the right trigger held, the d-pad cycles through units and buildings accordingly.
Ironically, in many ways, using the controller can actually feel faster to do certain tasks than the keyboard can in the Windows 10 version of Halo Wars 2. It may be a more demanding game, but Creative Assembly provides the tools needed to properly do what you need to — at least most of the time.
In my main play through, I never felt that Halo Wars 2 was too difficult. But the moments where I failed missions often came unexpectedly, when the enemy moved in a way that had not been telegraphed, or in a way I didn’t feel I could especially plan for. Halo Wars 2 is old school this way, and there’s something almost charmingly trial and error about it, save for the frustration I felt in having to restart some levels multiple times.
Of course, this was on Xbox One, which provides a reasonable challenge to casual to intermediate RTS players. On PC, normal felt almost comically easy, because it’s so much faster to select specific units and their special abilities with a mouse than it is with an analog stick. In other regards, Halo Wars 2 on PC plays like a traditional, albeit somewhat streamlined RTS with a heavy action emphasis. But in a genre that can sometimes feel like an arms race of overcomplicated systems, it was a relief to be challenged in a more action oriented manner.
Halo Wars 2 can't stick its landing, but it remains accessible without feeling dumbed down
I couldn't tell you why, from a business perspective, Halo Wars 2 exists. It doesn’t seem like the kind of project that will yield blockbuster returns for anyone involved. It doesn’t move the RTS genre forward. But it does make for an accessible RTS that doesn’t feel stupid in the process, and it serves as a reminder of how well Halo’s world and fiction lends itself to spaces outside of the first person shooter, even if it can’t quite shake its franchise avoidance of meaningful denouement.
Halo Wars 2 was reviewed using a pre-release "retail" Xbox One/Windows 10 key provided by Microsoft, and was played across both platforms for this review. You can find additional information about Polygon's ethics policy here.About Polygon's Reviews