Wayscript vs Yarn Spinner

The longer answer

What Yarn Spinner gets right

Yarn Spinner, from Secret Lab, earned its place as the Unity dialogue favourite honestly. The node-based .yarn language is approachable, the Unity integration is first class — commands, variables and dialogue UI wired straight into the engine — and support for Godot and Unreal has been expanding. The core is open source under MIT, the VS Code extension gives writers syntax help and preview, and an active community keeps the ecosystem healthy, with optional paid add-ons funding development. If your game's dialogue lives close to the code, this is a genuinely good home for it.

Authoring model: nodes in files vs a studio above the dialogue

Yarn's unit is the node — a titled block of dialogue and options in a plain-text .yarn file, with a node map view for overview while the authoring itself stays in the script. That's exactly right for dialogue that programmers own. Wayscript moves authoring into a visual flow graph and builds the layers Yarn leaves to game code: a typed quest graph with gated unlocks and rewards, success and failure gates, per-link any-of/all-of conditions, auto-complete rules and a journal; a world map with quest pins, travel routes and a live traveled-route overlay; and per-quest beat sheets (Quest Arc and Encounter Loop templates) so each strand is planned before it's wired. The output is still Yarn.

Testing and QA: compiler checks vs sweeps and a debugger

Yarn Spinner's compiler catches syntax and variable errors, the VS Code extension previews dialogue, and real testing happens in-engine — which means booting the game. Wayscript's Play Mode runs the story without the engine: a live variable debugger, save states, and shareable prototype links a teammate or tester can open from a URL. Above that, flow analysis sweeps the whole graph for dead ends, unreachable nodes, soft-locks, undefined variables and conflicting gates — the structural bugs that pass every compiler check and still strand a player.

The world behind the nodes

Yarn Spinner is a dialogue system, not a world model — characters, factions and places live wherever your team keeps them. Wayscript builds the bible into the studio — typed entries for the cast, factions and places, related to one another, with backlinks that collect automatically wherever a name appears and a graph of the world that redraws itself as you write. When one writer owns everything, a wiki works fine. When three writers share a canon and a producer asks what touches this character, the bible answers in one click.

Collaboration: files in git or a live shared graph

Fair's fair — plain-text .yarn files in git are a real strength for programmer-led teams, and Wayscript concedes that row: it exports plain Yarn, ink and JSON, but authoring lives in the studio. What Wayscript offers instead is real-time collaboration on the graph itself — presence, comments and history — which is aimed at the writers a git workflow quietly leaves out. A team of two developers loses little by staying in files; a team with dedicated writers usually feels the difference in the first week.

Localization

Yarn Spinner does have localization support in its Unity workflow — line IDs and string handling that integrate with the engine's tooling — which puts it ahead of most lightweight tools. What it isn't is a translation workbench. Wayscript's localization runs CSV round-trips with translators and AI-assisted draft translations, keyed to the flow so changed lines resurface for review before they ship stale.

The engine pipeline: nothing changes downstream

Wayscript's relationship to Yarn Spinner is the whole point of this page: it exports standard Yarn, so the open-source runtime, your custom commands and your dialogue UI stay exactly where they are. Teams keep the pipeline and change only where the words are written. There's also ink and JSON export for pipelines that prefer them, plus a live fetch API that serves the latest build or a pinned version straight to the engine. A first-party Unity importer is planned, though not yet shipped.

Who shouldn't switch

Solo developers and code-centric teams, quite possibly. If dialogue is written by the same people who write the C#, the files are small, and the VS Code loop feels fast, Yarn Spinner alone is a complete answer at zero cost — and re-creating an existing project in Wayscript is manual, since there's no .yarn import. Wayscript's case begins when the writing team stops looking like the engineering team: more writers, more quests, more languages, and a canon that needs keeping.

Price: zero vs eight a month

Yarn Spinner's core is free under MIT, with optional paid add-ons that support development — money well spent if you use them. Wayscript's prose, planning and story-bible studio is free; the interactive studio — graph, quests, world map, Play Mode, QA, localization and the Yarn/ink export — ships with the Author plan at $8/month. If the free toolchain covers the project, keep it. The $8 buys the writing room, not the runtime — the runtime was always free.