I do not know how long my branching story takes to play

A store page needs a playing time, but a story with branches has a shortest and a longest way through, and counting all words together gives a number no player will ever see. Here is how to work out both ends from the scenes, and what to do with loops.

Why this works

A story with branches has no single length, only a range, and the honest ends of that range are the shortest and the longest way through. Add up the cost of each scene along a way, not the whole text, because no one reads everything in one go.

When not to use it

A range from the text alone is a poor guide when time goes into things other than reading, such as puzzles, fights or exploring. Then play it, time a few real people, and use what you saw.

In the full entry

• What to build, step by step
• Starting values and the reason for each
• 3 common mistakes and the fix
• 41 lines of example code with 5 checks that pass
• How your AI shows you that it works

Say this to your AI

Use the Spielerando entry "I do not know how long my branching story takes to play" (read_entry estimate-playtime-of-a-branching-story) in my game. Build it step by step, and show me how you checked that it works.

Or skip this and connect the MCP: your AI then finds all of this by itself.Connect the MCP