Let’s set expectations in the first sentence: StorySplice is not a visual novel engine. There are no sprites, no backgrounds, no music channels, and no build targeting Ren’Py or Naninovel. What it is, is the layer most VN projects improvise badly — the place where routes get planned, scripts get written, and branching actually gets tested before anyone commissions art.
Most visual novels are drafted in documents and spreadsheets that go stale the moment a route splits. A VN is a branching structure wearing a costume, and writing one in linear documents means discovering your structural problems at engine-integration time, which is the most expensive possible moment. StorySplice keeps the script and the structure in one place: every scene is a node on the map, every route is a visible path, and the whole thing is playable as text from day one.
The standard VN skeleton — common route, branch point, character routes, endings per route — is a textbook hub-and-bottleneck graph, and it is dramatically easier to design when you can see it. Draw the common route as a spine, hang the character routes off the split, and the map shows you immediately whether route lengths are balanced and where a shared scene could save you a week of writing. The structure guide covers the underlying patterns.
Petrichor. Slice-of-life in a mountain town that empties every winter. A shared first act ends at the lantern festival, where the protagonist’s one free evening decides between three routes — the glassblower’s apprentice, the bus mechanic, the childhood friend who never left — each route arguing a different answer to whether staying is loyalty or surrender.
The Understudy. A backstage thriller: the lead actress vanishes during the interval, and whoever the understudy confides in — director, stage manager, the missing woman’s sister — determines which of four endings can be reached, and which truth about the disappearance the player is even allowed to see.
Because published StorySplice stories play as choice-based text in any browser, your VN script is testable the whole time. Share a draft link and route readers will tell you the mechanic’s route drags in act two while the art budget is still theoretical. The AI tools carry drafting weight — Branch Wizard to rough out a route split, continue and rewrite with accept-or-reject on every suggestion — and the Splinter tool can break an existing linear draft into scenes with proposed branch points.
Handoff is the point, so exports are structural, not screenshots. JSON export (free) gives you every scene, choice, and connection as clean data your pipeline can transform. Twee and Twine 2 HTML export (Pro) produce standard formats the IF toolchain reads. No exporter targets Ren’Py script directly — you or a small script convert — but you leave with the complete branching manuscript, not a lock-in. Details in the export guide.
No. It is a writing and structure tool: stories play as choice-based text. Art, sound, and presentation belong to your VN engine; the script and route structure are what you build here.
Not directly. You export the full branching script as JSON (free) or as Twee/Twine HTML (Pro) and convert to your engine’s format — the structure and prose carry over; the conversion is yours.
No — there are no variables. Model route logic through branch structure: the path where the flag would be true is simply a different path. Heavy flag systems are better added in your engine.
Yes. Draft sharing gives readers a private link and lets them comment, and published stories play in any browser with progress saved — a free text-only beta of your VN.
Writing, structure, playtesting, and JSON export are free (10 AI calls a day). Pro at $6/mo adds Twee/Twine export, 200 AI calls, model choice, and reader analytics.