Character injury and state continuity

She broke her arm holding the gate in chapter twelve. In chapter fourteen she climbs the siege ladder, and the first comment under the chapter says only: "arm?" Injuries, illnesses, fatigue, broken gear, spent money: readers track character state with a patience that surprises writers, because the reader's only job is to remember, while the writer's job is to invent, and inventing crowds out remembering.

State continuity is the practice of recording what is true of each character's body and equipment as the story moves, so that "what was true of her at chapter twenty" is always a lookup rather than a guess. Its absence is the classic continuity error, which Wikipedia defines as "an inconsistency in a storyline that goes against the flow of logic established by the story's plot": the healed wound that was never healed, the sword that reforged itself, the fever that ended when the scene changed.

The state ledger

For each character, the states worth dating:

• Condition: injuries and illnesses with the chapter they happened, their severity, and the expected course.
• Fatigue: hunger, sleeplessness, long rides. Fatigue is the state writers forget first, and combat after two sleepless nights is a different scene whether the text mentions it or not.
• Equipment: what she carries that can break, be spent or be lost. Weapons, tokens, coin. Using what was lost is item drift, a continuity error in its own right (see the seven continuity errors).
• Emotional state: where she stands after the last chapter's events. Fear and grief change decisions, and untracked grief that resets next chapter reads false.

The rules are the ones from character state tracking: date every change, keep the history, note the scene that established it. The rest of this guide is about the fields specific to bodies and gear: the course of an injury, and the pacing of healing.

A wound is a contract

The moment a wound is on the page, it is a setup, and setups demand payoffs. The principle is Chekhov's. As Chekhov wrote in an 1889 letter: "One must never place a loaded rifle on the stage if it isn't going to go off." A broken arm is a loaded rifle. Either it constrains scenes until it heals, and the constraint is the story the wound tells, or it was set decoration, and set decoration readers tracked for twenty chapters costs trust.

That is also why wounds need a course rather than a state: onset, worst, improving, healed or permanent. Each phase is material. The climbing scene is impossible in week one, desperate in week three, fine in month two; the same scene against a different phase is a different scene.

Healing pacing, especially in serials

The failure mode has a name in craft discussion. On the Descriptionary craft blog, Shonna White calls out "The Convenient Recovery Timeline", where injuries heal exactly when the plot demands it: convenience strains credibility, waving away injury effects erodes tension, and readers drift from "how will they survive this?" to "why should I care?". Her advice runs the other direction: build the recovery into the plot, because "Limitations create tension", and victories over a real handicap feel earned. Practical translations:

1. Fix the course at the wound scene. Decide the realistic span and write inside it; healing references for writers put superficial cuts at days, deep lacerations at four to eight weeks, and major limb fractures at eight to twelve weeks (Rebecca Shedd's healing-timeline guide for writers). When the plot needs it faster, buy the speed on the page: a healer, a price, a permanent cost.
2. Let the wound cost scenes, not paragraphs. One acknowledgment per scene where it matters beats one reminder per page.
3. Escalate. Late-story wounds should be worse than early-story wounds; if chapter one and chapter two hundred both feature a sprained wrist and a two-day recovery, the physical stakes have flattened.
4. Exploit established wounds. The old injury flaring at the worst moment is one of the cheapest payoffs in long fiction, because the reader loaded that gun with you and remembers.

Serials add one wrinkle: chapter time and story time drift apart, and readers experience the gap in real time. A healing arc that spans a month of story time can span four months of publication; an injury that still reads as recent to the characters can read as ancient history to the audience, and comment sections will treat it accordingly. Dating states in story time, not publication order, is what keeps the ledger honest (see timelines across POVs and flashbacks).

Beyond the wound

The same discipline covers the quieter states. Illness runs a course: fevers break, coughs linger, concussions can leave headaches and fogginess well after the scene where they happened. Fatigue accumulates and is paid down by rest that has to happen somewhere. Money is state: the character who spent her last coin in chapter nine cannot buy passage in chapter ten without an income event. And across books, state is the handover: the injury carried out of book two is book three's opening condition, which is one reason a series-level record matters (see series bible vs book bible).

The habit that holds it all together: update the ledger at the chapter boundary, and before any action scene, check the condition and equipment of everyone in the room. Thirty seconds of checking buys the thing serial writers cannot buy any other way: being right in public, every week.

How Kanonara approaches this

Condition, location, inventory and similar states are structured records with full history in Kanonara, so "was she injured before chapter twenty" has an answer without archaeology. When a chapter is analyzed, detected state changes arrive as proposals with their evidence, and the record updates only when you approve them. See how Kanonara works.