Wayscript vs Arcweave

The longer answer

The graph: two fluent branching canvases

Both tools speak the same first language — a visual canvas of connected elements, with variables, conditions and logic on the branches (Arcweave's arcscript, Wayscript's per-link conditions and expressions). Arcweave's boards keep big projects tidy; Wayscript's graph reads the same way and adds richer link logic — any-of/all-of gating included. On the canvas alone the two are close; the separation comes from what each tool builds around it.

Quests and world structure: a native layer vs the flat canvas

In Arcweave, a quest is a convention — boards and components arranged to look like one, maintained by discipline. Wayscript ships the quest layer as a first-class feature: gated unlocks and rewards, success and failure gates, per-link conditions, auto-complete rules and a player-facing quest journal, plus a world map with quests pinned to places, travel routes between them, and a live traveled-route overlay in Play Mode. Per-quest beat sheets and drafts (Quest Arc and Encounter Loop templates) give each quest its own writing room. If your game is structured as quests in a world — most are — this section is the biggest gap in the table.

Playtest and QA: two play modes, one debugger

Both tools let you play the branch you just wrote without leaving the app, and Arcweave's play mode shares as easily as everything else it does. Wayscript's Play Mode adds the tester's toolkit — a live variable debugger, saves you can branch from, and shareable prototype links — and behind it, flow analysis that hunts dead ends, unreachable nodes, soft-locks, undefined variables and conflicting gates. Arcweave catches some flow problems; Wayscript turns narrative QA into a checklist.

The entity database: components vs a typed bible

Arcweave's components are genuinely handy — reusable attribute bundles you attach to elements, enough to keep a cast consistent across boards. But they're an accessory to the canvas, not a world model. Wayscript's story bible is a typed database — characters, places, items, factions, relationships — with a self-updating backlink graph, so naming a character in a dialogue node adds that scene to her entry automatically. If your project is one shortish story, components may be all you need; if it's a world, the bible is the point.

Collaboration: the browser canvas vs the collaborative graph

This is Arcweave's home turf and it deserves the credit — real-time multiplayer in the browser with nothing to install is the reason many teams pick it, and it works beautifully. Wayscript matches the substance: the graph itself is collaborative, with presence, comments and history built in. What it can't match is zero-install — Wayscript's web app narrows the gap, but Arcweave's whole product is the browser tab. What Wayscript adds in exchange is that collaboration doesn't require the cloud to exist: your project is still yours, locally, when the Wi-Fi isn't.

Localization: two real pipelines

Both tools treat localization as a real workflow rather than an afterthought. Arcweave supports translated project content on its paid tiers; Wayscript does CSV round-trip — every line keyed and stable across edits — with AI-assisted translation as an optional, opt-in pass. Call this row a tie for most teams, and check both current feature lists if loc is your bottleneck.

Engine integration: plugins today vs open formats

Arcweave shows up well here: plugins for Unity, Unreal and Godot plus a web API, established and documented today. Wayscript's route is open formats — ink and Yarn, both with mature open-source runtimes proven in shipped games, plus JSON and a live fetch API that serves your latest build or a pinned version, so the engine pulls story like any other asset. Wayscript's first-party Unity importer remains a roadmap item, not a shipped feature. The practical difference is philosophy: Arcweave's plugins bind you to Arcweave's format; ink and Yarn outlive any one tool, Wayscript included.

Platforms and offline: the cloud vs local-first

Arcweave runs anywhere a browser does and nowhere one doesn't — cloud-only, no offline mode, no native apps. That's a fine trade for an always-online studio team and a bad one for a writer on a plane. Wayscript ships the full studio on Windows, macOS, Linux, iOS, Android and the web, local-first with your project in files you own; encrypted cloud sync is included on every plan, free included, and runs automatically — an account is required either way, but the writing itself never waits on a connection and the project stays in files you own. Native mobile and tablet authoring — the real editor, not a viewer — is Wayscript's alone in this pairing.

Price: seats vs a flat plan

Arcweave is freemium — a free tier that's enough to try real work, with team features on paid subscription tiers (check their site for current numbers; per-seat pricing changes). Wayscript's writing studio and story bible are free on every platform; the interactive studio — graph, quests, playtest, world map, engine export — ships with the Author plan at $8/month per writer. Both let a team start free and pay when it's serious; the difference is what the free tier includes and what the paid one unlocks.

Switching from Arcweave

Honestly: there's no importer for Arcweave project files. Boards, components and connections are re-created in Wayscript by hand — for most projects an afternoon or two of canvas work — and prose or scripts move across via standard document imports. Export what Arcweave gives you as an archive first, and nothing is burned. The rebuild is also the moment the new structure pays off: quests become quest objects, components become typed entities, and the backlinks start writing themselves.