Make a choice carry a consequence
Start with a small graph before adding more scenes.
A choice is a promise
Give each option a label that tells the reader what action they are taking. “Open the letter” and “Leave it sealed” establish different expectations. Two buttons called “Continue” may be structurally valid, but offer little help in understanding the decision.
Sketch a five-passage experiment
Begin with an opening, two consequences and two endings. Let the opening point to the consequences, then give each consequence an ending. This small structure is enough to test whether the options feel distinct. Add a return route only when revisiting the earlier moment makes narrative sense.
ForkFable treats every saved choice as available. There are no inventory flags, random outcomes, variables or conditions. A passage reached for the second time has the same text and options as the first visit. Write with that limitation in mind.
Converging paths can still matter
Two branches may meet at one passage. That does not automatically erase the significance of the earlier choice, but the shared text must work for either arrival. Read the shared passage after each incoming route. Avoid a line such as “You still carry the key” when one route never gave the reader a key.
Keep a portable draft
Save JSON before a major revision. The Markdown export is a readable ledger of all passages and destinations; it is not a playable story or a Twine/ink source file. The SVG map shows connections, while the reader panel lets you rehearse the choices inside this workspace.