A Twine alternative for professional game teams
Twine is where many writers draft their first branching story. When that story has to run inside a game, in several languages, written by a team, the needs change. Here is how LoreHub compares, and when Twine is still the right tool.
Written by the LoreHub team. Facts about other tools come from their own websites and docs, checked in November 2026. Spotted something out of date? Tell us on Discord.
When Twine is the right tool
Twine is free, open source and quick to learn. You write passages, link them with [[links]], pick a story format such as Harlowe or SugarCube, and publish a standalone HTML story anyone can play in a browser. For a prototype, a game jam or interactive fiction that lives on the web, it is hard to beat.
When teams outgrow it
- The game engine needs data, not a web page. Twine publishes HTML or Twee source; a game needs structured dialogue it can load.
- The game ships in several languages. Twine has no localisation for stories.
- Several people write at once. Writers, designers and translators need the same story, not copies of a file.
- Logic depends on the story format. Variables and scripting differ between formats, so the logic is tied to the one you picked.
Twine vs LoreHub
| Twine | LoreHub | |
|---|---|---|
| Built for | Nonlinear interactive stories published as HTML | Branching game dialogue and lore for game teams |
| How you write | Passages linked with [[links]], scripting per story format | Visual canvas of nodes, options and links |
| Logic | Variables and code depend on the story format (Harlowe, SugarCube, Snowman, Chapbook) | True/false variables, conditions on options and links, played/selected state |
| Output | Standalone HTML, or Twee source | JSON, YAML or OSF for any game engine |
| Translation | No localisation for stories | Translate tab, outdated tracking, no language cap |
| Team work | Not described in the Twine reference | Live presence and edits, history and revert, viewers free |
| Story checks | Missing target passages are created for you | Route Planner and validation: dead ends, unreachable nodes, missing translations |
| Lore | Not part of Twine | Worldbuilder: documents, relations, gallery, timeline |
| Price | Free, open source | Free plan; Indie €9/mo, Team €49/mo per world |
What LoreHub adds for game teams
Dialogue your engine can load
The Dialogue Builder exports a documented, versioned JSON schema with every node, option, link, variable and translation. Unity, Unreal, Godot or your own engine reads it with a small loader, and the Unity tutorial walks through one.
Translation built in
Every line and option has a stable key. The Translate tab shows one column per language, marks translations outdated when the source line changes, and lets each language block the build on a missing line or fall back to the source. There is no cap on languages on any plan.
One story, the whole team
LoreHub runs in the browser with live presence and edits, history and revert for every line, and viewers who never take a seat. Stories are saved as plain-text OSF files you can keep in Git or Perforce.
Routes that are checked
The Route Planner links dialogues into the routes a player can take and checks what each one requires and produces, so dead ends show up before playtesting. The lore behind the story lives next to it in the Worldbuilder.
Moving a Twine story to LoreHub
LoreHub has no Twine importer. A passage usually becomes a node, and its links become options. Rebuild one scene by hand to get a feel for it, or export Twee source and ask an AI agent connected through the LoreHub MCP server to create the dialogue, then play it in the browser. The Free plan covers that; see pricing for bigger projects.
Also compare LoreHub with articy:draft, Yarn Spinner or the full list of the best narrative design tools.