dialogue-systems

1# Dialogue systems
2 
3Model conversations as a **graph**: nodes hold lines, choices branch the flow,
4conditions gate options, and variables remember what the player did. The first
5real decision is *build vs. buy* — adopt a proven authoring tool (**Ink** or
6**Yarn Spinner**) or write a small data-driven runner. This skill owns both Ink
7and Yarn; the `visual-novel` and `rpg` genres consume it.
8 
9## When to use
10 
11- Use to design branching conversations, choice menus, or narrative state
12  (flags, relationship values) that affect later dialogue.
13- Use to decide between Ink, Yarn Spinner, and a custom JSON/resource format.
14- Use to wire a dialogue script into your game loop (advance line, present
15  choices, run commands, resolve variables).
16 
17**When *not* to use:** for engine UI (text boxes, portraits, choice buttons), use
18`godot-ui-control` or the engine's UI skill. For persisting narrative variables
19across sessions, use `save-systems`. For data-as-resources in Godot/Unity, see
20`godot-resources` / `unity-scriptableobjects`.
21 
22## Core workflow
23 
241. **Choose the authoring approach.**
25   - **Ink** — prose-first, writer-friendly, weave/gather flow; great for
26     dialogue-heavy or CYOA narrative. Integrate via ink runtime / inkle plugins.
27   - **Yarn Spinner** — node-based, explicit `<<commands>>`, strong for
28     game-driven dialogue with lots of engine hooks.
29   - **Custom runner** — a JSON/resource graph + a small interpreter when you need
30…