I think they stuck something addictive between the pages before they shipped it out. This was an impulse buy -- the title and the cover blurb got me -- and I've been stuck on it off and on ever since. ("part Robin Hood, part Ocean's Eleven" -- 'nuff said.) There are parts that I can't read without my author-brain kicking in -- but seeing (assuming) what the author is doing doesn't make a difference.
Part of this I think is that I like the trickster character type. Another part is that I like the worldbuilding and 'peeking around corners'*, particularly since I'm working on something now that requires extensive worldbuilding. (*I want to do this all the time, in my own writing or others', far beyond what's 'right for the story'. Like for instance: I wanna see Locke's other capers!)
Let's see...
That was a heck of a first line.
* World-building -- the date (Seventy-seventh Year of Sendovani)
* World-building and interesting characters -- the Thiefmaker of Camorr and the Eyeless Priest at the Temple of Perelandro.
* Instant conflict and worldbuilding -- desperately hoping to sell him the Lamora boy. (Mildly interested in the mention of Lamora here, but more because I know he's the MC. By context, all the rest sounds a lot more interesting.)
The rest of the conversation reinforces the above.
I didn't notice that this was a prologue until I reread. Likewise with the "interludes" between chapters.
The one place I noticed where misdirection worked was the first "Midnighters" scene. That was one place where the author-brain kicked in -- "Ok, here he goes, raising the stakes; how's Locke gonna handle this?" No notion that Locke was
behind this. It's still one of my favorite scenes, I think because of the trickster character again -- seeing Locke put on another face. The other place I didn't pick up the clues was the whole business with his name. (Though, in fairness, there were precious few clues for either one!)
The back-and-forth-and-all-over structure I think is one that readers would either be ok with or strongly dislike. I didn't mind it. (Except when I wanted to reread a particular part -- we should all have such problems!) As I said, didn't even notice the structural divisions at first. I think it was a good way to reveal information (via young Locke learning it) that was then relevant later, without either dumping it in the middle of the action or leaving too much space between the learning and the later action.
A couple of places did get annoying -- the handball match, the history of the Guilded Lilies, the history of the Bondsmagi (though that was slightly more relevant). I was willing to follow each of them on first read, to see where they were going, but was not too thrilled with them when I found out. The history of the Palace of Patience, too. (Locke crosses a bridge, not only pondering, but recalling history lessons? Uh, no.) Skimmed that section.
I thought the scene with the Grey King alone, watching his ship burn, was well-done ('Mother and Father wouldn't have cried...') Good job at giving the villain an empathetic moment...and yet I'm still fully rooting against him when the confrontation comes.
One thing that bugged me was the ever-present/never-present Sabetha. We know she's crazy, born queen of the charmers, and Locke's single-heartedly in love with her...and? Not one appearance on-page? The single-heartedness was kinda cool, making him different from other characters, added some humor vs. Dona
Sofia. Having her not around for the final conflicts worked; adding another layer of pressure would've been too much. But not even one appearance as a child? C'mon.
Also: don't
kill off characters I like! This was actually sort of an odd reaction -- author-brain and reader-brain in disagreement. I could see exactly why he did it -- it fit the characters, fit the world, raised the stakes on Locke (needing to avenge them, losing the advantages he was used to, etc.), increased tension for the later conflicts. Reader-brain didn't care. No other reaction there except
. I guess that means he succeeded in building unique, likeable characters!
Thought I had something else, but I'm being summoned elsewhere. More later, probably/maybe.