Thinblade - David A Wells

This book wasn't great, in fact, I don't even think it was that good. I couldn't finish it due to a number of reasons although I did try my best to do so. It has it's OK moments but those are far outweighed by the books downfalls.

I'll start with the positive; most of the characters are well rounded individuals and a lot of thought has gone into their development. The protagonist is a carbon copy of your generic hero and as a result is dull, uninteresting and predictable. The support cast is far more interesting, there's an alchemist character, Lucky, who has all kinds of different tricks that he uses to aid the group. He also has a big interest in food and often hands it out to people while conducting his affairs, this little detail is what makes him a better character than all the others in the novel put together.

The relationships between the characters is shown very well in points though the  novel, I won't go into it much but to illustrate my point there's this. After the hero thinks his father has been killed, someone shouts for 'Lord Valentine', at this point, our hero starts looking around, assuming the call was for his father, not him. It was a nice touch.

Some of the writing in the novel is very good, in fact, aside from the odd cliche here and there, its well written. What annoyed me so much I had to put the book down, was the constant repetition of the plot. I'm savvy enough to know what's happening the first time, one recap is OK, every time we meet a new character is just too much, it was like having it rammed down my throat and not to mention a little patronising. It got to a point where these little reminders would happen just before a fight. It destroyed the tension the author had created in previous paragraphs and interrupted the pacing.

Then there's the description. This book has more than it's fair share of description, of everything, all the time. It got boring to read. I don't really care what the guy fighting the hero looks like, where he came from or what he had for lunch. I care about how he gets killed. It's the same for every building they come across. Yes, I admit, its well written and some of its useful, but it could use thinning out to help the flow of the novel and to keep the reader interested.

You'd think with all that description that everything would be covered in the book right? Not so, there was an episode in the novel where generic hero has to rescue generic princess from generic bad guy. He does so after gaining a huge chunk of skills for free (he reads a skillbook... seriously?) and mullering the henchmen, great. What is omitted is how the baddie escapes. You just get a short sentence saying he got away. How? With all this descriptive power, you'd think Wells would be able to come up with something better than that. Most disappointing!

All in all, I wouldn't recommend reading this book in its current state. It needs another read through and the issues with it fixing before I even consider looking at the sequel.