A branching short story forgives improvisation; a branching novel does not. At novel length the questions become structural: where do paths converge so the writing stays finite, how does a chapter mean anything when readers arrive at it from three different directions, and how do you keep a voice consistent across scenes written months apart on branches you visit rarely?
StorySplice was built with long work in mind. The story map zooms from single-scene close-up to whole-book overview, so a two-hundred-scene novel stays legible as a shape rather than dissolving into a folder of fragments. Validation continuously checks for orphan scenes and broken links — the structural typos of long branching work — and readers’ progress saves automatically, which is what makes a multi-session novel playable at all.
The load-bearing pattern for interactive novels is branch-and-bottleneck: paths diverge within a chapter and reconverge at its end, so the book stays writable while choices still matter. The trick is carrying consequence through prose rather than plumbing — a reader who betrayed the patron in chapter two should feel it in how chapter five is worded on their path into it. The map makes bottlenecks visible as pinch points; if your graph never narrows, you are writing several novels at once and the map will tell you so early. The branching structure guide covers the standard shapes and their costs.
The Cartographer’s Daughter. Lisbon, 1799. Ines inherits her father’s unfinished survey of a coastline three empires want mapped. Three patrons offer to fund the completion — the navy, a smuggling syndicate, a rival cartographer — and each patron is a route with its own chapters, converging only at the final headland.
Vessel. A generation ship, four decades from arrival, and two narrators who contradict each other about what happened on deck nine. The reader chooses whose chapters to trust; the choice compounds quietly until the docking, where both versions are due at once.
Branch prose drifts. The scenes on your main path get polished on every pass; the scenes two choices deep get visited twice a year and sound like it. The AI tools help here in an unglamorous way: continue drafts forward in the story’s established register, rewrite takes a custom instruction ("tighter, less wistful"), and everything arrives as a suggestion you accept or reject — nothing lands in the manuscript unreviewed. Used on the rarely-visited branches, it is less a co-writer than a consistency tool.
Long work needs readers before it needs an audience. Draft sharing gives beta readers a private link to the unpublished story, and they can leave comments in place — the branching equivalent of margin notes. When it ships, publish to the community library or keep it unlisted. Pro reader analytics then show which routes real readers take and where they stop, which for a novel is plot-level information: an ending nobody reaches is a chapter you can cut or a signpost you can fix.
No practical one — the editor and map are built to handle hundreds of scenes, and zoom, pan, and validation exist precisely so big structures stay manageable.
No. Reading progress saves automatically in the browser, with no reader account required, so a novel can be played across many sessions.
Share the draft by link. Beta readers play the unpublished story and leave comments tied to what they read — no account juggling, no exported files.
Fewer than you fear. Four to eight endings that pay off different throughlines beat twenty variations on two outcomes. Budget endings first and structure backward from them.
Always. JSON export is free on every plan, and Pro adds Twee and Twine 2 HTML export for the wider interactive fiction toolchain.