Choices and branches
Learning paths through this topic
How to Build a Branching Story That Does Not Break
Model every scene with what it needs and changes, then have a checker walk every path. It finds dead ends and gives you the exact path to each one.
How to Make Player Choices That Really Matter
A choice matters when the game remembers it and shows the result later. Model every choice and have a checker find the paths where nothing changes.
Story path check
Your AI walks every way through a story written as scenes and choices, and finds out whether a player can get stuck. It tells you if an ending can never be reached, if a scene is cut off, or if a scene needs something nothing ever gives you.
Branching Choices
Choices make the reader a part of the story. The player feels that what they pick matters when later scenes remember it, when some paths close and others open, and when a bad pick can be taken back without leaving the story in a broken state.
Multiple Endings
Different endings make a story worth playing twice. The player must feel that their deeds led to the end they got, and must never reach a finish that looks like a mistake: no ending, the wrong one because of a hidden rule, or one that changes after it was shown.
Timed Dialogue Choices
A countdown makes a conversation tense: the player has to answer on instinct, and saying nothing becomes a choice with a cost. It only works if the time feels fair, which means enough time to read, a clock that never runs while the player cannot act, and a way for players who need longer to get it.
Let an advisor council vote, with unequal weight, abstentions and ties
A ruler's council can give each decision a story of its own, but only if the vote has clear rules. Here is how to count weighted votes, handle advisors who stay silent, and settle a tie in a way the player understands rather than a coin flip.
Make asking an ally for help cost more each time you ask
If an ally helps whenever asked, the player calls in the cavalry every turn and the alliance means nothing. Here is a favour balance that pays for each request, makes quick repeat requests cost more, forgets old ones, and lets a refusal be a story beat that costs nothing.
Stop the autosave from trapping the player in a lost situation
A game that autosaves when the monster is already unavoidable sends the player into a death loop on every load. Here is how to keep a short history of saves, skip the ones that can no longer be won, and fall back to the last good one.
Find the battle stance that is always best before players do
If one stance beats every other no matter what the enemy does, the choice is fake and players will find it by the third battle. Here is a quick table check that names the stance that always wins and the ones nobody should ever pick, so you can fix the numbers early.
Count what is already built when the story asks the player to build
A story asks for three farms, and the player already has two, or has one halfway built, or tears one down after the reward. Here is how to count what exists and what is on its way, give the reward once, and decide whether old buildings count.
Carry your army from mission to mission without bringing back the dead
In a campaign of linked battles, the units a player keeps are part of the story. Here is how to hand the survivors to the next mission, heal them fairly, add reinforcements, and stop a fallen favourite from quietly walking back in through the recruitment screen.