If Every Choice Becomes a Branch, the Module Will Never Be Finished
A module designer prepares a city that is about to come under siege.
The players can support the kingdom.
Help the rebels.
Work with the mercenaries outside the city.
Remain neutral.
Steal the relic protecting the city.
Assassinate one side’s leader.
Open the city gates early.
Sabotage the siege weapons.
Or leave with everything they have learned and let the people inside face the war themselves.
Every choice leads to more choices.
If the players help the rebels, they can work with them openly, provide information in secret, or simply use them as a way into the royal city.
If the players steal the relic, they can use it themselves, give it to one of the factions, sell it to a third party, or hide it somewhere else.
If the designer creates a new branch for every option, then continues branching for every choice inside those branches, the scenario quickly grows beyond anything one person could finish.
Ten choices with only two possible answers can already produce 1,024 combinations.
TTRPG players will not promise to choose one of those combinations just because the designer managed to write them all.
They will still find option 1,025.
If player freedom depends on the designer writing every possible future in advance, the work is impossible from the beginning.
Players Have Many Options, but Fewer Things Actually Reshape the Future
The players may have many ways to enter the royal city.
Obtain a pass.
Climb over the wall.
Bribe a guard.
Pretend to be envoys.
Hide inside a merchant caravan.
Enter through the sewers.
These methods differ in presentation, risk, and cost.
But for some later events, they may all change the same condition:
The players are now inside the royal city.
The players may also have many ways to prevent the rebel leader from acting.
Kill him.
Capture him.
Persuade him to leave.
Injure him badly.
Expose his secret and cause his followers to abandon him.
These results are not identical.
But they may all change another important condition:
Do the rebels still have a leader capable of holding the faction together?
Players can have a huge number of options.
The number of world states that continue controlling later events is usually much smaller.
Can an important character still act?
Can a location still be entered?
Who controls an important item?
Does a faction trust the players?
What stage has the crisis reached?
A module does not need to write a complete future for every method.
It needs to know which conditions those methods ultimately change.
Find the Choices That Change Conditions Before Deciding How Much to Prepare
Not every player choice needs to become part of the module’s long-term state.
Whether the players enter through the east gate or the west gate may only affect the current scene.
Whether they drink wine or water at a banquet may have no effect on anything that follows.
A joke, a short argument, or a route that creates no lasting consequences can remain part of the performance at the table.
The choices worth tracking are the ones that change later conditions.
If the players kill the commander defending the city, later command decisions, information, and faction structure may all be affected.
If they steal the relic, the city loses its protection and whoever carries the relic may become a target.
If they publicly support the rebels, the kingdom’s attitude toward them may change, along with the places they are allowed to enter.
If they wait too long, the siege may advance to its next stage.
When deciding whether a choice needs long-term state, the designer can ask a few questions.
Will this prevent an important character from acting?
Will it change who controls an important item?
Will it open, close, or destroy a location?
Will it change the relationship between the players and a faction?
Will it cause a future scene to become possible, impossible, or different?
If the answer to all of these questions is no, the choice may not need to become persistent state.
If the answer to even one is yes, the choice may be one of the conditions that reshapes the future.
High-Impact Conditions Usually Change Characters, Access, Resources, Relationships, or Time
A condition that changes the future is usually more concrete than “the players chose option A.”
It changes something in the world.
Characters can be pivotal.
Whether a leader is still alive changes who can give orders, negotiate, provide information, and keep an organization together.
Access can be pivotal.
Whether the players have permission, an invitation, recognition, or a particular ability changes which places and events are open to them.
Resources can be pivotal.
Who controls the relic, a key, an army, money, or information changes who can take the next step.
Relationships can be pivotal.
Whether a faction trusts the players, or whether an NPC is willing to cooperate, changes what approaches are available inside the same scene.
Time can also be pivotal.
Alert levels, the progress of a war, corruption, pursuit, and countdowns can gradually remove opportunities that once existed.
Once a module identifies these pivotal conditions, it no longer needs to turn every player route into a separate scenario.
Different methods can change the same condition.
The same conditions can also combine in different ways, causing later scenes to respond differently.
The designer is no longer trying to manage every possible story.
They are managing the smaller set of conditions that genuinely change the shape of the future.
The Same Scene Can Respond to Different World States
The players may eventually reach the siege of the royal city.
That does not mean the module needs a completely different war for every possible history.
The walls, streets, enemy forces, and central crisis can remain shared.
What changes is the world state brought into the scene.
If the rebel leader is still alive, he may arrive with reinforcements or use the chaos to seize power.
If he is dead, the rebels may be divided, and some of them may even join the enemy.
If the relic remains in the temple, the city keeps its original protection.
If the players took it, that protection is gone, and the enemy may turn its attention toward them.
If the kingdom trusts the players, they may enter the command center.
If the kingdom considers them enemies, they may need to avoid the city guard while taking part in the same battle.
If the alert level remains low, the players may be able to act in secret.
If it is already high, the gates, roads, and guard positions will have changed.
The module does not need to write a complete scene for every possible combination.
It can prepare one shared siege and explain how a few important conditions change the people, entrances, resources, and responses within it.
This kind of scene is not a fixed sequence of events.
It is a place in the world capable of receiving several different histories.
Prepare Principles for How the World Responds, Not Every Possible Combination
The designer can prepare principles for how the world responds to important conditions.
If the rebel leader can still act, the rebels remain unified and can participate in negotiations.
If the leader is dead, the lieutenants compete for control, and promises made under the previous leadership may no longer be valid.
If the relic remains in the temple, the city’s protection continues.
If the relic has been removed, the city loses that protection, and whoever carries it becomes a target for several factions.
If the alert level reaches stage two, more guards are stationed at the gates.
At stage three, the city enters lockdown and previously accessible routes are closed.
These are not complete story branches.
They describe how the world responds to important states.
During play, the Game Master can build the scene from the conditions that are currently true.
The rebel leader may still be alive but unwilling to help the players.
The relic may be gone while the city still trusts them.
The alert level may be high, but one guard may still owe them a favor.
The GM does not need a dedicated chapter for that exact combination.
They only need to understand the direction in which each important condition pushes the scene.
The module provides a structure for responding to changes in the world.
The actual story is still created at the table after the players make their choices.
Tracking Less Makes Important Consequences Easier to Preserve
State tracking can also grow out of control.
If every passerby has a numerical opinion of the players, every door has an open-or-closed flag, and every conversation has several progress stages, the GM will soon be buried under the data they created.
More tracking is not always better.
The states worth preserving are the ones with persistence and a meaningful area of effect.
How many later scenes will this state affect?
Does it change what a character can do?
Would forgetting it create an obvious contradiction in the world?
Is it worth checking again before the next session?
If the players open an ordinary door that will never appear again, the module probably does not need to track it permanently.
If they destroy the only gate into a city, affecting warfare, defense, and travel, that is worth preserving as world state.
If an ordinary merchant is briefly annoyed with the players, the GM may only need to remember it during the scene.
If a merchant guild controlling important resources becomes openly hostile to them, that may affect an entire part of the campaign.
The smaller and clearer the set of tracked states is, the more likely the GM is to maintain it.
Important consequences are also less likely to disappear beneath a large amount of irrelevant data.
InkWeave Tracks the Pivotal Conditions, Not Every Possible Future
InkWeave does not write every future the players might reach.
It also does not simulate the daily lives of every NPC after the players leave a city.
The designer still decides which events happen and which states are worth tracking.
InkWeave can preserve the pivotal conditions selected by the creator.
Whether characters are alive, where they are, and what identities they hold.
Who possesses important items and where those items are located.
Whether locations are open, restricted, sealed, or destroyed.
The members, leaders, and structure of factions.
Boolean flags can record whether a condition is true.
Enum flags can record the current stage of an event.
Counter flags can record alert levels, reputation, investigation progress, or other accumulating states.
When a later scene requires particular conditions, a condition gate can check whether the current world still supports it.
Once the players genuinely change one of these pivotal conditions, that event remains in the manuscript’s timeline.
InkWeave does not need to know every possible future.
It only needs to follow confirmed history and derive the world’s current state from it.
If the creator truly wants to preserve two complete and mutually exclusive futures, Git branches can be used to maintain separate timelines.
Ordinary choices do not all need to become parallel universes.
Most of the time, allowing the conditions that shape the future to keep counting is enough for the world to respond to the players.
Freedom Does Not Require an Infinitely Growing Story Tree
A TTRPG module can never predict everything the players will do.
They will ignore the most obvious path.
Trust the wrong person.
Save a character who was expected to die.
Kill an NPC the designer thought was safe.
Take an item that was never meant to leave its original location.
They will also make choices in completely unprepared places that are more interesting than the planned story.
The designer does not need to defeat this uncertainty.
They do not need to write every possible combination.
What they need to prepare are the pivotal world states that can carry those changes forward.
Who can still act?
Who controls the resources?
Which places remain open?
Which relationships still hold?
Which crises have reached their next stage?
A module designer does not need to write every future for the players.
They only need to know which choices have changed the conditions that allow those futures to exist.
Freedom does not require an infinitely growing story tree.
It requires a world that remembers what the players changed.