When I first picked up Blood Oath, I was skeptical because I thought the name was completely unimaginative. I guessed that the name Blood Oath had been used in books, movies, and video games scores of times. Well I looked it up, there are about twenty.
Blood Oath follows young Zach Barrows, a White House employee who gets stuck in a job protecting America from "the other side" (anything Stephen King has written about) with a vampire that is bound to do the President's will. The vampire is named Cade. The book was good, It's strong point was the plot, which was the kind that made you want to scream for a sequel and kept you turning the pages (even though I wouldn't call it a page turner). It delivered story telling at its best.
However, Christopher Farnsworth used some very clichéd devices. Zach is a newcomer to working with the President's vampire, so he has to get it all explained to him (and the reader). This is a writer's escape route; if a writer resorts to making the main character a newcomer to the process that is central to the plot, it means, they aren't imaginative enough to explain it in some other way. Also, there's a character named Griff, and he is the veteran, who has been working with Cade since the seventies, and as soon as the I found out that Zach was replacing him so he could retire, I knew he was going to die in some painful way, and he did. Now, you may be saying, "Mickey! Quit ruining the story for us," but honestly, that is the most predictable event in any book I have ever read...... ever. So it's not really a spoiler, it's an idiot test, if you didn't guess it, you're the biggest moron I've ever met, and I know some dumb people.
At the end of the day, Blood Oath is a very good read, but it would be better suited as a screenplay, which makes sense because Christopher Farnsworth is a screenplay writer. I look forward to the Blood Oath movie.
No comments:
Post a Comment