I certainly won't argue that The Flood wasn't a horrible book, because it was. I'm surprised to find that a lot of people I've spoken to didn't like the other Halo books either, which makes me hesitant to defend them, but I will because I do think they were great books. I don't see how having action in them is a valid critisism, hell at one point you say there's too much action in the books, then you complained that the actual battle for Reach was just a tiny bit at the back of the book. The Fall of Reach, First Strike, and Ghosts of Onyx gave a lot of very interesting background into humanity's plight, the Covenant, and the Forerunners. And Contact Harvest did the same with the background to how the entire conflict began. Sure they weren't perfect, but I don't see how people couldn't like them.Geo Da Sponge said:It won't happen because the books were such unmistakeable dross that they just make me want to throw up. Fall of Reach was crippled because the author decided there had to be multiple action sequences in the book, even when Master Chief is a ten year old. I don't care about a bunch of pre-teens smacking around elite commando troops. It just brings back sickening memories of all the 'family movies' where you end up feeling sorry for the 'bad guys' because they're getting smacked around by retarded children hyped up on fairy sticks. That and the fact that the actual battle of Reach is a tiny section at the back of the book after a bunch of irrelevant stuff happend makes me want to forget this as fast as possible.
Then there's The Flood, which I have bought but have barely started because at least half the book is just the exact details of the first game listed in the most unimaginative way possible. I'd swear the author was just playing through the game and making notes, up to and including the number of enemies killed and the number of bullets he fired, occasionally adding bits like "Master Chief smiled inside his helmet", because we all know how great a writing technique that is.
And Contact Harvest, of which the first half of the book seems to be dedicated to explaining what the different acronyms mean. However, it is still relatively good, mainly because they got a different author to do a decent job.
But I've saved the worst till last. First Strike. I wanted to know how the Master Chief escaped the ruins of the Halo. I really did. But afterwards I just wanted to reject the reality out of sheer disbelief. What's up with this book? It seems like they can't go five minutes without a fast paced action sequence going past, which always has some unorthodox but hugely effective solution. There's a whole sub-plot about a crystal, which pretty much serves as nothing but an excuse for the author to write in whatever he feels like. It sounds like it came out of the mid of a seven year old.
In short, whether they go into the details of the Halo universe or not, you will end up denying what has happend in the books. What was going through the guys head when he decided to bring back several surviving Spartans that were still around at the end of First Strike? Why are none of the events mentioned in Halo 2? Are they, as Sergeant Johnson says, classified? Is that because they don't want anyone to know just how stupid the war is and that they might as well not bother because Cortana and the Chief will "have a plan"?
You're much better off reading the Mass Effect books. Certainly, the second one is quality.
And I did read the first Mass Effect book, haven't gotten a chance to read the second one, but I plan to along with the Gears of War book.