Halo: First Strike is the third novel in the original Halo novel trilogy, taking place immediately after Halo: The Flood (and Halo: Combat Evolved) and right before Halo 2. For many fans of the Halo video games, that time period in-between the first two Halo games was always one of the franchise's greatest mysteries – Sgt. Johnson even relays that that information was “classified” in Halo 2, and so it was never mentioned in any of the games since. After Halo: Combat Evolved, so many things happened: the Covenant found Earth, Sgt. Johnson was alive and well, Master Chief got a new set of MJOLNIR armor, and new Covenant forces were introduced on the battlefield. For those like myself who had always wondered how such drastic changes took place between these two Halo games, this is the book for you; most of your answers will be answered in this novel...most, but not all.
One of my biggest gripes with Halo: First Strike is how it attempts to tell the untold story of the interim time between the first two Halo games, yet it stops just short of giving us all the answers despite being the last in the original book trilogy. Since no further books were planned at the time, having an ending as ambiguous as the one this book gave us is truly dumbfounding to me. I was not lying when I said that most of your questions would be answered by this book, but it will also leave you with an entirely new set of questions immediately afterwards. Basically, we trade one mystery for another, arguably more interesting mystery. I won't divulge exactly what prompts these new sets of questions so as not to spoil the story, but the ending leaves quite a significant hole in the Halo trilogy of books and games that will always irk me when thinking about it. Hopefully future Halo novels clear things up, but since this was supposed to be the end of a trilogy, I would have expected all loose ends to have been tied up by now rather than having more crop up in their stead.
One thing I noticed about the Halo book trilogy is that each book's title references something major in the Halo universe on which their plots are predicated – the destruction of the Human colony of Reach in Halo: The Fall of Reach; the outbreak of the parasitic Flood in Halo: The Flood – and although Halo: First Strike falls into that category as well, I felt that, ultimately, what took place in this novel was nowhere near as significant or impactful to the Halo universe as those other two novels' plots. Despite what the title would suggest, the operation in question, First Strike, does not take place until the very last section of the book, which consists of only a handful of chapters; the rest of the book preceding this section acts as build-up to this moment and establishing chapters for all the characters and locations. Now, none of this would be much of a problem if I thought that Operation First Strike was as huge a moment in the Master Chief's saga as the destruction of Halo or losing planet Reach to the Covenant. Alas, nearly everything about the main plot of this book is thrown by the wayside as soon as Halo 2 rolls around, making these supposedly major events in the book nothing more than a detour to the main action. I find this to be very disappointing because the stakes were so high in this novel – stakes exceeding or on par with the previous two novels – that it becomes sad to realize that very little of what happens here carries on in the games. Perhaps future books made more use of these events, but since this was originally meant to be the last in a trilogy of books, I found it to be a semi-lackluster end for a franchise as (formerly) great as Halo.
I said this was a semi-lackluster entry, but only because of its significance in the grand scheme of things. As far as entertainment value, this is definitely a great read throughout. Everything from the introduction of so many new and great characters and the further development of returning characters like the Master Chief, to the epic set pieces where tremendous battles take place and the emotional weight of the story, Halo: First Strike is rivaled only by Halo: The Fall of Reach in its storytelling. Truly, Eric Nylund was made to write for this series, which is a far cry for what I can say about William C. Diets, author of the excruciatingly average Halo: The Flood. Unlike the previous novel in this series, there is nary a dull moment of which to speak; the constant action is reminiscent of that found in the video games, which makes me wish that this book was adapted into a mainline Halo game. With the baffling direction that the latest Halo games have been taking these days, they would be fools not to utilize great stories like these from their past to bolster their newest entries.
My favorite aspect of this novel is easily the characters, both new and old. Of course, the Master Chief is present throughout, and I felt like this was a return of the complex character introduced in Halo: The Fall of Reach. In Halo: The Flood, the Master Chief was barely anything more than a cold, unfeeling killing machine with only a few sporadic emotions and free thoughts sprinkled in here and there. Thankfully, Nylund knows how to write this character perfectly, balancing his drive to kill with his desire to protect everyone around him beautifully.
The new characters were also written very well, and I felt like these were characters I could get used to reading about in future books. Each one brought a unique perspective to the plot, having their own motivations and reasons for fighting, and they worked well in the context of the story. Some of the most interesting moments of the novel included long stretches of dialogue between all the character because there was so much personality brimming from each line thanks to the diversity of character types. Admittedly, some character tropes were a bit cliché (like the tough guy who is always itching to kill something), but none were so egregiously stereotypical that I ever felt annoyed by these exaggerated traits. Overall, the characterization in Halo: First Strike is top notch (for a Halo novel) and will surely impress even the most ardent Halo fans.
With such great writing present this time around, I was a bit let down that the Covenant perspective was virtually absent in this novel. I will give Halo: The Flood credit for actually exploring this intriguing aspect of the Halo universe, something that was not done seriously until Halo 2. Though a disappointment, I am at least glad that a vast majority of the time and attention was paid exclusively to the human side of this event, reminding readers how dire the Human-Covenant War truly is when people without super human enhancements and power armor are so intimately involved.
More so than in other Halo novels, or frankly even other Halo games, Halo: First Strike delves more deeply into the idea that every single life has immeasurable value in this war, even that belonging to a lowly marine. Every death has weight in this novel, whereas the games and other books can easily kill off a handful of characters without so much as missing a stride in storytelling. I appreciate that this book stressed the importance of fighting for every last person's life.
In the end, your opinions about this book will boil down to where your priorities for reading a Halo book lie. If you are the type of Halo fan looking for major revelations about the Halo universe that would impact future titles, you may be left wanting. However, if you are more inclined to just sit back and enjoy whatever the book throws at you, then I think you will have a much better experience with this novel overall. Halo: First Strike offers very little in the way of universe building, at least to any significant degree, but where it falters in that regard it excels elsewhere in storytelling and characterization. This is a highly enjoyable Halo novel, one that should not be overlooked merely because of its smaller scope overall. Though it had some problems, Halo: First Strike is a must-read for die-hard Halo fans.