MetaData (language and reading direction), Aliases (reusable text snippets), and Dialogue (the actual nodes). Files live under Resources/{languageEnglishName}/{folderName}/{langCode}.{fileName}.yaml.
A complete file
Top-Level Blocks
MetaData
Language and reading direction for the file. Used by Parley at load time and and used for UI layout decisions.The language this file is authored in. See LanguageID.
Reading direction.
LTR or RTL. See TextDirection.Dialogue
The conversation itself — a map of node IDs to nodes. Node IDs are arbitrary strings you reference viaNextNode, TrueNode, and FalseNode. The first node in the map is where the conversation starts.
Example
Node Types
Every node uses the same underlying schema — the fields you populate determine what kind of node it acts as at runtime.Dialogue Node
Spoken dialogue. The most common node type. Plain dialogueA node’s name can be any string such as “node_3” or “help”.
Choice Node
A dialogue node that presents the player with options. Same as a Dialogue Node but with aChoices list. When Choices is populated, NextNode on the parent is ignored and is prefered to not be set as it is semantically incorrent. The player’s selection determines the next node.
Example
Branch Node
A utility node that routes to one of two targets based on flag state. Branch nodes have no speaker or text. They’re invisible at runtime, used for control flow. WhenCheckFlags is populated, the node evaluates: if every listed flag is set, it routes to TrueNode; otherwise FalseNode.
Example
FalseNode back to an earlier node in the conversation to create a loop.