If you already have lore, world docs, or character notes written down, start with LoreWeaver Architect. It'll convert your prose into structured game data. If you're starting from nothing and want to learn how branching stories work, start with Twine. Both are free.
If you have existing material: LoreWeaver Architect
LoreWeaver Architect takes your written lore, character descriptions, design docs, or world bibles and turns them into structured narrative data: entity graphs, dialogue trees, quest flows, relationship maps. You paste in what you've written, and Architect builds the structure. You edit from there.
In the narrative board, you can open a text editor per arc or beat, so you can keep writing in prose while Architect handles the structuring underneath. You can also work visually, dragging nodes and connections the way you would in articy:draft or Arcweave.
It's free. You can start in minutes if you have docs to feed it.
If you're starting from scratch: Twine
Twine is free, open-source, and runs in your browser. Click "New," create a passage, write some text, add a link with [[Go left]]. That creates a new passage. Do it a few more times and you've got a branching story. Hit "Play" and click through it. Thirty minutes, tops.
Twine doesn't connect to game engines. It outputs HTML. But that's fine for now. The point is learning how branches work, how choices fan out, how quickly things get complicated. Build something small here before you commit to a production tool.
When you need engine integration: Ink or Yarn Spinner
Once your story structure works and you need it running inside your engine, pick one of these.
Ink is an open-source scripting language by Inkle Studios. It reads like a screenplay, handles variables and conditional logic cleanly, and has an official Unity plugin. Community plugins exist for Unreal (Inkpot) and Godot (inkgd). Ink powered Sea of Thieves and 80 Days. Free, MIT licensed. About an hour to your first working prototype in the Inky editor.
Yarn Spinner is built specifically for Unity. Simpler syntax than Ink, tighter Unity integration. Used in DREDGE and Night in the Woods. Free, MIT licensed. About an hour to get running.
If you're on Unity, either works. Yarn Spinner is simpler to start with. Ink is more expressive for complex branching. If you're on Unreal or Godot, go with Ink.
When you need production-scale management: articy:draft
Your project now has hundreds of nodes, multiple characters with relationship tracking, and a quest log. You need a dedicated visual authoring suite.
articy:draft X has been the standard for 15+ years. Hogwarts Legacy and Disco Elysium were built with it. Visual flow charts, entity databases, localization pipeline, official plugins for Unity and Unreal. Free tier available, paid plans from 5.99 euros per user per month. The learning curve takes half a day, but the documentation is solid.
Arcweave is a browser-based alternative if your team is remote and needs real-time collaboration.
Mistakes that'll cost you a weekend
Mapping your entire story before testing one scene. Start with one scene, three choices. See if those choices feel different. If they don't, fifty more branches won't fix it.
Skipping the paper outline. Twenty minutes with a notebook before you open any tool saves hours of spaghetti logic. Write down your 3 to 5 key decisions, what variables track the player's choices, where branches merge back.
Ignoring your engine's import pipeline. Before you write 10,000 words in any tool, export a small test file and import it into your engine. Make sure that works first.
Go build something
If you've got existing docs, paste them into LoreWeaver Architect. If you're starting fresh, open Twine in your browser. Either way, thirty minutes of building teaches you more than another hour of reading.