The Flood (Halo)

Rating:
Summary: As good as Fall of Reach? No. Worth a read? Yes.
Review: Naturally for those who have played Halo, The Flood (regardless of different authors or not) will be slightly repetitive.
However, if you've read Fall of Reach, you'll definitely want to read The Flood. What makes The Flood slightly more unique than even the game itself is the fact that it tells the story of Halo from the Covenant's point of view and their opinion on the war with the flood, Halo, and the humans. While that might not seem like much it definitely makes the book a little more two-dimensional than the story told in the video game. Overall, the real reason I could not give this book 5 stars is simply because there was not a lot that was new except the Covenant's point of view. The side battles with the Marines were also pretty cool as it let you know what they thought about the war. Even if you have read Fall of Reach and played Halo, this is still a great pickup. Just not as exciting as the first if you've played Halo already.

Rating:
Summary: Don't Hate On This
Review: Alot of people trash this book because it basically retells the story of the game. I've played and beat Halo many times and I love the book. It really gives you a different look at the game from different character's perspectives. If you're a big Halo fan like I am, you gotta get the book. It will give you a better connection with the characters (even the Prophets) and the game. You'll look at the game differently after reading it. Check it out.

Rating:
Summary: Halo the Flood
Review: this book totally follows the game almost word for word it goes into a little more detail but its useless detail. if youve played the games at least once there is no reason to read this book. however the first book (fall of reach) and the third book (first strike) are a thousand times better with a better author (eric nylund)

Rating:
Summary: Nice indepth look of Halo 1
Review: Even if you've played Halo 1 and think you know the story, you need to read this book to really understand all that went on in the battle over Alpha Halo.

Dietz did not excite me the way Nylund did, but I think part of the reason is that you already know the story if you've played the game, and Dietz basically gives you a replay of the events of Halo 1. He will describe the process of clearing doors over and over, he will describe the process of scrounging for ammo over and over, and he will describe the process of reloading weapons over and over. This is not out of touch with what actually went on in Halo 1 as you played the perspective of the Master Chief.

He fleshes out the story well by talking about the struggle of the Marines, the plight of the grunt, Yayap, and the chaos that went on within the Covenant ranks as they fought both human and Flood.

One who only plays Halo 1 does not understand and appreciate the significance the Marines and Marine ODSTs on Halo 1. Playing Halo 1 would lead you to believe that only the Master Chief made everything possible and single-handedly save the day. While it is true that the most crucial points in the battle were turned over only by Master Chief and his trusty Cortana, it was the Marines that tied up large portions of Covenant and gave the Master Chief a home base to operate out from.

Rating:
Summary: hmmmmmmmmmmmm...
Review: A warning to those who have already played the game: This novel is essentially an adaptation of the plot and situations presented in the game. If you've played it, then you know how the story progresses and how it will end. What makes this worth reading (and worth 4 of 5 stars) is the additional material Dietz integrates into the basic plot.

We learn a great deal more about the origins of Master Chief and the SPARTAN program that developed him into a super-soldier. In the Halo game, Master Chief (aka John-117) says very little, and his thoughts and motivations are hard to discern. That's long been one of my (very few) criticisms of Halo: Despite all the development that went into visual design, gameplay, plot, and peripheral characters (343 Guilty Spark is one of the most fascinating characters in recent video game history), the main character comes across as unknowable and aloof. Here, Dietz alleviates that by allowing us glimpses into the mind of Master Chief, learning more about his feelings, thoughts, and motivations. We also see how others react to him: Most Marines are awestruck by him (he IS 8 feet tall, after all), but some--even in the UNSC leadership--see him as a freak, as a failed experiment that should have been eliminated long ago. His relationship/symbiosis with Cortana is also fleshed out, and she becomes a more in-depth character as well (who may be in the first stages of AI Rampancy; Dietz drops as many hints about that as the games and other novels do). He also provides a few details about the Forerunners, who built Halo and are worshiped as near-deities by the Covenant. Although he doesn't tell us much (I'm sure Bungie is saving many major revelations for Halo 3), he does drop a few interesting details about them (I won't spoil it for potential readers).

Another strong aspect of the novel is how Dietz explores the Covenant side of the conflict through the eyes of a lowly Grunt, Yayap. We see more of their hierarchy (with hints of what we would learn in Halo 2 about the Covenant's ruling order) and learn more about the individual races, such as the Grunts, Elites, Hunter, and Jackals. The lead Covenant Elite featured in the novel, Orna'Fulsamee, may also be the same Elite who takes on the mantle of the Arbiter in Halo 2. There's also more info on the Covenant's history and their motivations in their war with humanity.

The UNSC Marines, often little more than cannon fodder in the game, are also fleshed out a lot more. We learn more about Foe-Hammer (always heard but never seen in the game) and other Marines, plus we gain some more insight into Captain Jacob Keyes.

Dietz' writing style is sparse, with just enough descriptive detail to give the reader a good sense of time and place. Weapons and combat tactics are adequately described, and the author has a good sense of action (though his occasional need to give too much information about a weapon or its effects detracts from the action and slows the story's momentum, though only temporarily).

Overall, that's what makes this novel worth reading, even for those already familiar with the game: The complex and detailed Halo universe is given even more depth, making the overall story as rich as most sci-fi novels. Eric Nylund's two Halo novels, "The Fall of Reach" and "First Strike" are also recommended, and add much more to the growing story of Halo. And if you've played Halo and are going to play Halo 2, you may want to read "First Strike" first. It details what happens between the two games and prepares you for the complex storyline of Halo 2.

I hope this review was helpful

--Christian Wheeler

Rating:
Summary: Disappointing if you've played the game
Review: The only people I can recommend this book to are those who have not played Halo but wish to play Halo 2. It basically tells, blow by blow, exactly what happens in the first game and what astute players were supposed to infer from hints dropped through the game.

It's competently enough written, but is a waste of time if you want more from the Halo universe. Try "First Strike" instead, which takes place immediately after Halo.

Rating:
Summary: Nylund remains Halo
Review: Well this book is pretty great, except for the fact that it takes place on Halo!!! Anyone who owns the game (and all of you reading this should) already knows what's going to happen. Sure there are a few surprises and humor, but nothing too incredible to make a book out of. The only key feature that this book contains is the little parts outside of the Master Chief. I liked seeing what the enemy was thinking, and thought that Dietz made this book more amusing by relating a grunt's (Yayap) story into this wide scale mayhem known as Halo.

Rating:
Summary: Better than the first
Review: Makes the game funner and easier. This is the book of the game. SO good it has to have a sequel in between it and halo 2, in the next book. 2 days for halo2!!!!!!!

Rating:
Summary: Is it good or great?
Review: Halo: The Flood, the second book in the Halo book series written by William C. Dietz, was a very good book. I thought it was very impressive how he put things from the video game into the book. Most of this book was very well written; it had plenty of detail, which left the reader craving more of the tremendous story after each chapter. The book also answered questions I had about the game. In the game the time of day changes nearly every chapter, and it makes the player wonder where the main character goes in-between levels, and this is answered in a very well described part of the book. After reading the book, I found out that the valiant Earth Forces had invaded a butte and made that their base, which answered my question. This book/book series is not only great stories about a tremendous video game, it is also a guide for people to know what happens before, during, and after the game that one would not know without the books. Although this book was very good and entertaining, it did have some flaws in it.
In the book, there is a part where the Covenant, the alien enemy, captures Captain Keyes, the captain to the ship the Pillar of Autumn, and some of the crew. In the game, Keyes and other members of the crew are taken captive aboard the Covenant ship the Truth and Reconciliation; however, in the book, Keyes is the only person taken captive. This conflict between the game and book makes readers/players confused at which one is right. Also, the beginning of the book and the end of the book are written very well with powerful describing words, but the middle of the book lacked complex sentences, good adjectives, and mainly just good writing. It seemed as though William C. Dietz had the middle of the book be his time to relax and not use his great writing skills that he showed the readers he had in the beginning and end of the book.
Beside some minor flaws in plot and writing, this book was well written and there were many similarities and differences between the book and the game, which, I think, was needed greatly. This book was not just a retelling of the game, it also had many different parts from the game, which made Halo fans say, "So that's why that happened!"