Visual graphs
The quest and dialogue editors lay out lines, choices, markers and endings as connected nodes.
Choose your creator type on any feature page to see the tools in your own context.
Build branching quests and conversations as visual graphs, then step through them in Simulation to see where every path leads.
Map out quests and NPC conversations as branches, and step through each one to check every choice leads somewhere.
Draft dialogue and quests where choices matter, and walk every branch to see where it ends.
Build quests and dialogue as graphs with conditions and variables, simulate them, and export JSON files for your engine to import.

The featured screen and the explanation change with your creator type. What the feature does, and which plan includes it, do not.




Three ways Interactive Stories & Game Development helps, in your own context.
The quest and dialogue editors lay out lines, choices, markers and endings as connected nodes.
Simulation plays a graph one step at a time, pauses at each choice and lets you step back.
At the end, coverage shows how much of the graph you reached and lists what was not.
Three ways Interactive Stories & Game Development helps, in your own context.
Vitus tells you when a graph is fully reachable and every connection is complete.
Step back and take the other branch to see where it leads.
Variables such as fenrir_bound record what has happened, for later quests and dialogue to check.
Three ways Interactive Stories & Game Development helps, in your own context.
Each dialogue line links to the character who speaks it.
Choices show their options in plain words, so a branching scene reads like a script.
Shape the story in the narrative planner, then build its quests and dialogue in the same world.
Three ways Interactive Stories & Game Development helps, in your own context.
Typed, scoped variables can be read in conditions, changed by consequences and used in dialogue text.
Export a replay of a Simulation run, and see coverage and every variable when it ends.
On Worldsmith and above, export one JSON file per entry type, shaped for Unreal DataTable import, Unity or Godot 4. It is a one-way file export.
Related features change with the creator type you choose.