Clothes Get Wet, Dirty, or Taken Off in a Branch: How Do You Prevent a Character's State from Suddenly Resetting?
Manage clothing as an independent state line, not as an accessory description attached to a character illustration. The method has four steps: give each key garment an observable initial state; at branch nodes, write clearly "what action changed it"; give each change a recovery condition; and finally require downstream text to reference only the current state, not rewrite from impression. Below, a fictional teaching example is used to walk through the whole process; the characters, numbers, and dialogue are all made up, only to demonstrate the method.
Introduction
Manage clothing as an independent state line, not as an accessory description attached to a character illustration. The method has four steps: give each key garment an observable initial state; at branch nodes, write clearly "what action changed it"; give each change a recovery condition; and finally require downstream text to reference only the current state, not rewrite from impression. Below, a fictional teaching example is used to walk through the whole process; the characters, numbers, and dialogue are all made up, only to demonstrate the method.
First distinguish "observable state" from "emotional description"
"Bedraggled," "a bit cold," and "in a very bad mood" cannot be checked, and once they are written into the next paragraph they easily drift back. An observable state is something that can be seen by a person, recorded by a prop, or pointed out by another character: whether the coat is on the body, how far up the cuff is wet, whether the badge is still pinned on, which side the mud spot is on. These are what the author should write.
Take the fictional story "Rainy Night Duty Room" as an example. Duty officer Lin Huai has three related items: a dark gray coat, the left and right cuffs of a shirt, and a copper badge pinned to the left chest. The initial state is recorded as:
| Item | Initial state | Observable basis |
|---|---|---|
| Dark gray coat | Worn on the body, dry | When entering, the shoulder line is intact, with no dripping |
| Shirt cuffs | Dry on both sides | Rolled to the middle of the forearm |
| Copper badge | Pinned to the left chest, positioned straight | Level with the second button |
This table is placed at the beginning of the branch, and all later paths start from here. It does not say "Lin Huai is very tired"; it only records the visible parts.
For each branch, write the "triggering action," not a description of the result
The value of a branch lies in different actions. The same rainy night can be split into three paths, each changing only one or two items.
Path A: Going out in the rain to pick someone up. The triggering action is "pushing open the side door and walking into the rain for about four minutes." Result: the shoulders and back of the coat are soaked through, the rolled cuffs are wet from the rain, and the badge is still pinned on but has water droplets on its surface. The coat is not taken off.
Path B: Carrying a leaking bucket indoors. The triggering action is "bending down to carry the bucket, and the rim of the bucket brushes across the left chest." Result: a gray-black water mark is smeared on the left chest of the coat, the badge is knocked askew and shifted toward the armpit, and the cuffs are wet up to above the wrists because of repeatedly wringing the rag. The coat is not taken off, but it is dirty.
Path C: Feeling stuffy, taking off the coat and draping it over the chair back. The triggering action is "unbuttoning, taking off the coat, and draping it over the chair back." Result: the coat is off the body and dry; the shirt cuffs remain dry; the badge leaves the body together with the coat and is pinned on the left chest of the coat. Only the shirt remains on the person.
The differences among the three paths must land on specific items. Writing "Lin Huai becomes very miserable" is useless; writing "the badge moves from the chest to the left chest of the coat on the chair back" is useful.
Recovery conditions must be fixed, not left for the next paragraph to guess
Clothing will not restore itself. If you want the coat to become dry again, you must write a condition under which it can dry, and write the cost clearly.
Recovery condition for Path A: enter the heated inner room, hang the coat on the wall hook, and let at least a period of time pass that can be covered by dialogue. During this time, Lin Huai can only wear the shirt, and the shoulders still carry dampness. If the plot does not allow waiting, the coat must remain wet the whole time, and a wet coat will limit the actions he can take, such as not being able to sit for long or lean his back against the filing cabinet.
Recovery condition for Path B: the coat can continue to be worn, but the water mark on the left chest needs wiping to fade, and if it is not wiped clean it will leave a stain. The badge can be pinned straight again, but "pinning it straight again" is a clear action, and someone has to do it. If this action is not written, the badge stays in the crooked position.
Recovery condition for Path C: putting the coat back on the body requires an action of "picking it up and putting it on." Before it is put on, the badge is not on the person, and any "badge on Lin Huai's left chest" does not make sense.
Recovery conditions are best given irreversible items: after the water mark is wiped lighter, a stain remains; after wet cuffs dry, they wrinkle; after the badge is brushed, the pin is slightly loose. These details give the state memory and prevent a one-click reset to zero.
Downstream references recognize only the current state
After the three paths merge, later scenes cannot vaguely write "Lin Huai stands at the door." Words must be chosen according to the current state. The merge handling can be written like this:
- Before the merge point, first declare "entering the inner room of the duty room is the merge condition."
- After the merge, the first sentence references only the items in the state table that still hold.
- If the state of a certain path conflicts with the merge scene, first add a transitional action, then merge.
The comparison is as follows:
| Action to be written in the merge scene | Can Path A write it directly? | Can Path B write it directly? | Can Path C write it directly? |
|---|---|---|---|
| Lin Huai hangs the coat on the wall hook | Yes, the coat is already wet | Yes, but the left chest has a mark | No, the coat is still on the chair back |
| Lin Huai looks down at the badge on his left chest | Yes, the badge is on his body | Yes, but the badge is out of position | No, the badge is on the coat |
| Lin Huai rolls up his cuffs | Yes, the cuffs are already wet | Yes, the cuffs are wet up to the wrists | Yes, the cuffs are dry |
The purpose of this table is to force the author to check once before writing the merge sentence. If a certain path does not hold, either change the merge sentence or add an action in that path to push it into a state that can merge.
An easily missed check: who does the badge follow?
The badge is an object pinned to clothing, and its position depends on where the clothing is. In Path C, the coat is off the body, so the badge follows the coat. At this time, if downstream text says "Lin Huai raised his hand and touched the badge on his chest," readers will notice that the badge has come back out of nowhere. The correct way to write it is to first write "he took the badge from the coat on the chair back," then write the action of putting it on. This order cannot be omitted.
Similarly, after the cuffs are wet, writing "he rolled up his sleeves" and writing "he lowered his sleeves" have different effects. Lowering wet cuffs will get the wrists damp, and this associated change must also be recorded in the state table.
Completion check
After writing a branch, go through it with the following five items:
- Every key garment has an initial state, and the initial state uses observable description.
- Every branch node writes at least one triggering action that changes clothing.
- Every change is paired with a recovery condition, and the recovery condition contains one irreversible detail.
- Before merging, first declare the merge condition, and the merge sentence references only the state that still holds.
- For objects that "follow the clothing," such as badges and cuffs, the position is consistent with the position of the clothing.
When AI-assisted generation is involved, only one point needs to be remembered: it may restore the clothing state not clearly written in the previous paragraph according to common impressions, so the state table must be maintained by the author, and the generated result must be checked sentence by sentence against it, rather than expecting it to remember automatically. This method is a checking scheme and does not guarantee that the output of any tool will be consistent every time.
The next step is very small: pick a scene you are currently writing, list only three garments, fill in the three columns of initial state, triggering action, and recovery condition, and then check the merge sentence.
