Build branching stories, game dialogue and guided experiences with a visual scene map, typed variables, conditional choices and scene effects. Playtest paths, inspect live values and export a standalone playable HTML story.
Visual branching mapVariables & conditionsPlayable HTML export
◇ → ◆SCENES · CHOICES · CONSEQUENCES
From an idea to a usable result
Load the lantern adventure or orientation example. Add scenes, choose a starting scene and mark conclusions as endings.
Use Write to edit scene text, speakers, choices and destinations. Include {{variable_name}} in text to display a live value.
Create typed project variables. Add choice conditions, choice effects and scene entry effects without writing code.
Playtest choices, go Back to restore earlier values, inspect the trail and resolve Review findings. Save the project and export a playable story or scene map.
What to expect
Up to 150 scenes, 20 choices per scene, 600 total choices and 30 variables. Rules use all-of comparisons and ordered set/add/toggle effects. No arbitrary scripting or game-engine-specific format export. Structural reachability ignores conditions; manually playtest varied values. Numeric values are bounded to ±1 billion. Playtests allow 1,000 steps. Projects: 8 MiB.
Processing happens in your browser. Save a project before closing the page. Optional drafts stay in this browser. Public pages include advertising and optional analytics under our privacy policy.
Using Interactive Story & Dialogue Designer
Build branching stories, game dialogue and guided experiences with a visual scene map, typed variables, conditional choices and scene effects. Playtest paths, inspect live values and export a standalone playable HTML story.
Load the lantern adventure or orientation example. Add scenes, choose a starting scene and mark conclusions as endings.
Use Write to edit scene text, speakers, choices and destinations. Include {{variable_name}} in text to display a live value.
Create typed project variables. Add choice conditions, choice effects and scene entry effects without writing code.
Playtest choices, go Back to restore earlier values, inspect the trail and resolve Review findings. Save the project and export a playable story or scene map.
Example
Load the lantern adventure or orientation example. Add scenes, choose a starting scene and mark conclusions as endings.
Questions & answers
How is this different from a simple branching flow?
Scenes can change typed variables, choices can depend on values, and playtesting shows the effects of earlier decisions. Back restores the preceding values.
Can I export a story people can play?
Yes. After resolving Review items, download a standalone HTML story with choices, text, Back and Restart controls. It does not need an account or server.
Can I insert code into a condition?
No. Rules use listed comparisons and set/add/toggle effects. This keeps the project predictable and avoids executing arbitrary scripts.
Does Review prove every conditional path is completable?
No. Review checks references, typed rules and structural paths. Conditions can still create value-dependent dead ends, so test different choices and values.
