2.3 KiB
title, category, tags, contextKey, micro, quickTitle, quickSummary, screenshot
| title | category | tags | contextKey | micro | quickTitle | quickSummary | screenshot |
|---|---|---|---|---|---|---|---|
| Attribute History | Characters | characters, attributes, changes, continuity | characters.attributeHistory | Track visible or story-relevant character attribute changes over time. | What is Attribute History? | Attribute History records changes such as condition, status, appearance or other traits that matter to continuity. |
Overview
Attribute History captures changes to a character that become true at a point in the story. It is useful for injuries, disguises, emotional states, social status, abilities, public reputation or any other tracked trait that affects later scenes.
Use it when the change needs to remain true after the scene where it happens. If an injury, disguise, recovery or revealed trait affects later chapters, record the moment it becomes true.
How To Use It
Review attribute entries in story order. Use the linked scene to check whether the change is introduced clearly and whether later scenes respect it.
Understanding the Fields
| Field | What it means | Example |
|---|---|---|
| Attribute type | The kind of trait being tracked. | Injury, disguise, status, appearance, ability. |
| Attribute value | The specific state that becomes true. | "Broken wrist", "using a false name", "publicly disgraced". |
| Effective scene | The scene where the value becomes true. | The warehouse fight where the wrist is broken. |
| Description | Why the attribute changed or how it should affect later scenes. | "Cannot climb easily until recovery is shown." |
Example
If Rebecca injures her hand in Chapter 8, later scenes should not show her playing piano easily unless the story accounts for recovery. Attribute History helps catch that.
Writer Tip
Record the first moment a change becomes true, not every scene where it remains true. Add another entry when it changes again, such as recovery, disguise removal or status reversal.
Common Mistakes
- Tracking tiny details that never affect the story.
- Forgetting to add an attribute event when a visible condition changes.
- Mixing author planning notes with in-story changes.
- Leaving recovery or reversal moments unrecorded.