Skip to main content
A Parley conversation is a single YAML file with three top-level blocks: 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

The rest of this page documents each block and node type in detail.

Top-Level Blocks

MetaData

Language and reading direction for the file. Used by Parley at load time and and used for UI layout decisions.
LanguageID
required
The language this file is authored in. See LanguageID.
TextDirection
required
Reading direction. LTR or RTL. See TextDirection.
Example

Dialogue

The conversation itself — a map of node IDs to nodes. Node IDs are arbitrary strings you reference via NextNode, 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.
string
required
Who’s talking.
string
How they feel.
string
required
What they say.
string
Node to advance to. Omit to end the conversation.
list of strings
Flags to set when this node plays.
Plain dialogue
With flags Flags persist across the conversation and can be checked later by a Branch Node.
A 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 a Choices 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.
string
required
Who’s prompting the choice.
string
How they feel.
string
required
The prompt itself.
list of choices
required
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. When CheckFlags is populated, the node evaluates: if every listed flag is set, it routes to TrueNode; otherwise FalseNode.
list of strings
required
Flags that must all be set for the True branch.
string
required
Node to advance to when all flags are set.
string
required
Node to advance to otherwise.
Example
Branch nodes are also how you build loops — point FalseNode back to an earlier node in the conversation to create a loop.