How to use the Branching Story Planner.
Track consequences across branches so choices remain meaningful. If branches rejoin, preserve at least one difference in knowledge, resources or relationships.
Make the workflow fit your task.
Define each choice and record its consequences for knowledge, resources and relationships. When branches rejoin, carry those differences forward and check that later scenes acknowledge the earlier decision.
- What you provide
- Scenario and meaningful choices.
- What you get
- Choice tree with outcomes and consistency notes.
See the input and the result.
Illustrative input and output · a teaching example, not a live WebAct run
Example input
A traveler can help a stranded merchant or continue to the town gate.
Completed example
Helping costs time but earns a guide; leaving preserves daylight but requires navigating the town alone.
Load this input into the prompt, then copy it to WebAct to try the task. Your result may differ from the illustration.
Decisions and troubleshooting.
Can branches rejoin without making choices meaningless?
Yes, if the choice changes something that persists. Track the difference explicitly instead of relying on a cosmetic line change.
Why does a later scene assume an event from another branch?
Add a state condition or revise the shared scene. Audit the prerequisites for every fact used after a merge.
Try it with your own source.
Replace the example with your material in the task prompt. Keep the requirements you need, then copy the task into WebAct.
Customize and copy the task ↑