Continuity Errors in Famous Novels (and What They Teach You)

Continuity errors in books aren’t a sign of bad writing. Some of the most celebrated novels in print contain them, waved through by the author, the editor, the copyeditor, and decades of reprints. That’s both reassuring and instructive: reassuring because you’re in excellent company, and instructive because the reason great books still slip is structural, and the structure is something you can beat. Here are four famous examples and the lesson each one teaches.

Sherlock Holmes and the wandering wound

Dr. Watson is struck by a Jezail bullet during his service in Afghanistan. In A Study in Scarlet the wound is in his shoulder. By The Sign of Four it has moved to his leg, and later stories reference it in ways fans have argued about ever since. Arthur Conan Doyle also let Watson’s wife call him “James” in one story, though his name is established as John.

Doyle wrote quickly, in serial installments, across years, with no master reference sheet for his own character. The wound moved because nothing was checking the first story against the fortieth. It’s the textbook attribute error, and its cause is the absence of a single source of truth.

Robinson Crusoe, naked with full pockets

Daniel Defoe gives us one of literature’s most quoted slips. Crusoe strips off his clothes to swim out to the wrecked ship, then, once aboard, stuffs his pockets with biscuits. The pockets he no longer has.

This one is striking because it isn’t a long-distance error at all; the contradiction sits inside a single scene. It’s a reminder that continuity isn’t only about remembering a detail three hundred pages later. It’s about anything in the text disagreeing with anything else, and even a paragraph can contradict itself when no one is cross-checking.

Harry Potter and the reversed echoes

In Goblet of Fire, Harry’s wand and Voldemort’s connect, and echoes of Voldemort’s victims emerge in reverse order of their deaths. In early printings, the echo of Harry’s father appeared before his mother, even though she was killed last and so, by the spell’s own logic, should have emerged first. Readers caught it, J.K. Rowling acknowledged it, and it was corrected in later editions.

This is a timeline and ordering error, the kind that hides inside a rule the author themselves established. It’s also the happiest example here, because it shows the correction loop working: the rule was explicit, so the violation was checkable, and once someone checked, the fix was a single change.

Tolkien fixing his own ring

The most instructive case is one where the author caught himself. In the first edition of The Hobbit (1937), Gollum behaves very differently around the ring; he even offers it as a prize and is dismayed to find it already gone. When The Lord of the Rings turned that ring into the One Ring, an object no creature would willingly surrender, the old scene no longer fit. Tolkien rewrote the “Riddles in the Dark” chapter for the 1951 edition to reconcile them.

This is series continuity, the hardest kind, because the contradiction spans two works written more than a decade apart. Even Tolkien, the most meticulous worldbuilder in the canon, had to go back and patch the record once the world grew.

The pattern behind all four

Notice what these have in common. The distance between a fact and its contradiction is large (chapters, editions, whole books), or the writing was fast and serialized, or both. In every case the missing ingredient is the same: a queryable source of truth that gets checked against the actual text. Human memory can’t hold every fact across a novel, and editors, for all their skill, are optimizing for prose, pacing, and sense, not for mechanically cross-referencing every stated detail against every other one. These are exactly the five continuity error types every long manuscript is prone to, showing up in the best books we have.

Why it’s easier to catch now than it was for Doyle

Here’s the part that matters for your own manuscript. Doyle had no way to ask “everywhere Watson’s wound is mentioned, do they all agree?” without rereading his own catalog by hand. You do. A structured record of your world, connected to your prose and checked as you write, turns each of these famous slips into a flag you would see in seconds. That’s the whole idea behind tracking continuity as a system rather than a feat of memory, and it’s how AI continuity checking works under the hood: the world and the manuscript, read together and compared.

This is the problem StoryGuard exists to solve: a world graph linked to your chapters, scanned by AI to flag the wandering wound, the reversed echo, the rule your plot quietly broke. The comforting truth is that continuity errors have always survived great authors and good editors. The useful truth is that your readers run exactly this check for free, on their second read, and then they email you about it. Far better to run it first.