Branch View

Branch View helps you analyze the different routes a player can take through your visual novel.

What it is

This view looks at your story as a set of playable paths. It helps you understand how choices branch, where routes reconnect, and whether every path can reach a satisfying ending.

INFO

Use Branch View when you want answers, not just a map. It focuses on route logic and player outcomes.

What it shows

• All possible routes from a chosen starting point to later scenes or endings
• Branch points where player choices create meaningful splits
• Path lengths so you can compare short and long routes
• Convergence points where different paths meet again
• Which choices lead to which scenes, outcomes, or route locks

How to use

1. Open Design mode in the workspace.
2. Select Branch View.
3. Choose the label you want to use as your starting point.
4. Review the generated routes and follow each branch step by step.
5. Compare path lengths to check pacing and content balance.
6. Look for dead ends, missing transitions, or routes that never reconnect.

Questions it can answer

• Can every route be completed?
• Which choices create the biggest story changes?
• Are some branches much shorter than others?
• Where do separate routes merge back together?

When to use it

• Before playtesting a branching chapter
• When balancing route length across multiple choices
• When checking that each ending path is reachable
• When hunting for dead ends or forgotten transitions

Tips

• Start from your opening label, then repeat the analysis for major chapter entry points.
• Pair it with Story Graph for both a visual overview and a route-by-route breakdown.
• Review convergence points carefully so shared scenes still make sense for every path.

TIP

If a branch looks too short or too isolated, it may need an extra scene, a clearer transition, or a stronger payoff.