Documentation

Learn how to use NodeCanvas

  1. Getting Started
    1. Framework Concepts
    2. The GraphOwner Component
    3. The "Self" Parameter
    4. BBParameters
    5. Visual Debugging
  2. The Editor
    1. Controls & Shortcuts
    2. Assigning Tasks
    3. Canvas Groups
  3. The Blackboard
    1. Data Binding Variables
    2. Blackboard Parenting
    3. Global Variables
    4. Dynamic Variables
    5. Network Sync
    6. Save & Load
  4. Tasks (Actions & Conditions)
    1. Tasks Included
    2. The Reflection Tasks
    3. Using Task Lists
    4. Creating Custom Tasks
    5. Using Task Attributes
    6. Using BBParameters in Tasks
    7. Creating Generic Tasks
    8. Using FixedUpdate and OnGUI
  5. Behaviour Trees
    1. BT Nodes Reference
    2. Reactive Evaluation
    3. Creating Custom BT Nodes
  6. State Machines (FSM)
    1. FSM Nodes Reference
    2. FSM Callbacks
    3. Creating Custom FSM Nodes
  7. Dialogue Trees
    1. Dialogue Tree Nodes Reference
  8. Mapping Sub Graph Variables
  9. Using Graph Events
  10. Using Signal Events
  11. Working with Custom Types
  12. Working with AOT Platforms
  13. Using the Graph Console
  14. Using the Graph Refactor
  15. Using the Graph Explorer
  16. JSON Import/Export
  17. Scripting
    1. Interfacing with your code
    2. GraphOwner API
    3. Blackboard API
    4. Runtime Instantiation Tips
    5. Creating a Behaviour in Code
    6. Creating Custom Object Drawers
    7. Appending Custom AutoConverters
  18. FlowCanvas Integration
    1. Behaviour Tree -> FlowScript
    2. FSM -> FlowScript
    3. Dialogue Tree -> FlowScript
    4. FlowCanvas -> NodeCanvas
    5. Using Tasks in FlowScripts
  19. Full API

Dialogue Tree Nodes Reference

Say

The Say node will simply make the selected actor say a statement. The text in the statement can be made dynamic by using variable names in square brackets “[” and “]” (e.g. “[myVarName]”), which will be replaced with the variable value to string in runtime.

Task Action

The Task Action node will execute an Action Task assigned. The selected Actor is used for the Action.

Branching

Branching nodes allow diverting the dialogue in different directions and thus they can have more than just one out connection.

Task Condition

The Task Condition node will evaluate a Condition Task assigned and continue with either the left or the right connected child when the condition is True or False respectively. As such the Task Condition node can have up to two child nodes. The selected Actor is used for the condition check.

Multiple Task Action

The Multiple Task Condition node is similar to the Task Condition node, but can have any number of connected children. All connected children connections can be assigned a Condition Task independently and the first one (from left to right) that evaluates to True will execute.

Multiple Choice

The Multiple Choice node will prompt any number of choices in the UI for the player to select. Each choice can also have an optional Condition Task assigned. A choice is shown only if its condition evaluates to True, which is checked only once at the time the Multiple Choice node is executed. There is optionally a parameter to allow a specific time for the player to choose a response. If the time runs out, the first available response is selected.

Probability Selector

The Probability Selector will select a child to execute at random based on the weights provided for each child. An optional Condition Task can also be set per child, to exclude it altogether in case the condition evaluates to false.

Control

Control nodes are meant to control the dialogue flow.

Jump

The Jump node will simply continue with the selected node that you linked to in its inspector. This node is there to help you with the dialogue tree organization.

Finish

The Finish node will finish the Dialogue Tree. Please note that a Dialogue Tree will either way finish in Success on its own if any of its nodes is finished and has nowhere else to go (e.g. no further connections). However if you want to finish the Dialogue Tree in Failure, this node is required.

Sub Graphs

SubGraph nodes execute another entire graph.

Sub Dialogue Tree

Sub Dialogue Tree

The Sub Dialogue Tree node can hold an entire other Dialogue Tree. When the Sub Dialogue assigned is finished, the Sub Dialogue Tree node will continue either with the “Success” connection or the “Failure” connection (if any of those exist), depending on how the Sub Dialogue finished (see the Finish node above).

Yes No Suggest edit
5 of 5 users found this section helpful
« Dialogue TreesMapping Sub Graph Variables »
Suggest Edit