Some of you may wonder, why do I post a review of a book and then yammer on about it here? What's the difference? Well, you can't really see much of a difference in the book before this one, mostly because there's nothing extra to reveal. Here, I get to divulge everything, bitch about endings, go into details, and so forth, whereas people wouldn't be all that happy if I did it in my review. That's the difference.
On to The Everlasting. I guess I should have known better since Lebbon also wrote Berserk. What's that you ask? Most of us writers tend to have the same devices, similar characters, and elements in our books. We can't help it. It just comes naturally. Take me for example, 99% of the time there's a woman in my books that kicks ass, she's similar to her other book counterparts and they even have similar names. I probably shouldn't do that, but I can't help myself. So when Lebbon introduces the reader to Scott, a man heading toward his 50s, and interrupts things with flashbacks, yeah. Should have see it coming I guess. But you never know.
That's actually my only real problem with this book - I had a real hard time getting into Scott's character. In fact, we start off immediately with past events and memories of by-gone days. I don't ever feel properly introduced to Scott's character, and what's more, with the way he totally sobs over his wife's disapperance, I didn't have enough time or info or something to truly see how much they cherished on another. I mean, yeah, I don't doubt husband and wife love each other and whatnot, but Scott, for quite some time, just seemed to constantly break down into bouts of crying over the kidnapping of his wife.
That too, annoyed me. No, guys, I'm not saying you shouldn't be super upset when your wife goes missing, but geez, after the first few times quit crying and try to do something about it! Especially once you have a direction to go in! Get mad at least! Scott's personality felt flat to me, which is probably due to the introduction, and he never got pissed when he should have. I wanted him angry out of frustration, he should have been angry, demanding answers, God throw something why don't you? Hmph.
Aside from my disconnect with Scott, the story was interesting. We're on a quest to find and destroy an ancient book written centuries, maybe even millenia ago (well, probably not millenia because humans had to have been around to write it). The whole concept of the Wide and where you go when you die and all that jazz was cool and Lebbon did his best to explain it in terms that would boggle your mind even as you tried to imagine it. I'm still having trouble accepting the only way Scott would do anything was if Lewis kidnapped Scott's wife and did all that buuut oh well. Likewise I'm not sure why Helen would believe her kidnapper. I also don't believe that Tigre would just ignore Scott for the rest of his life. Tigre, if he really is who Nina said he was, sounds like the kind of guy that would take you out just because. Maybe not immediately, but eventually. I don't buy that he'll just accept that the book's gone and not kill Scott because of it.
Otherwise, it wasn't bad. Some good, horrific elements and creepy things going on, fit for the genre. Cool locals and Old Man was a nice addition. And, I must say, that Lebbon has finally applied my definition of immortal. I don't use that term lightly - if you're immortal and you can't die, then you can't die. None of this vampires are immortal stuff - no, vampires aren't immortal, they're just ageless. Vampires can die, easy as anyone else as long as it's done right. But not Lebbon's immortals. One gets cut in half, but she's still trying to drag herself together, then she gets shot in the head, but all the pieces start moving back to wake her up again. Now that's immortal.
Read the Review
Guy on the cover obviously not immortal/everlasting...