Documentation

Learn how to use NodeCanvas

Download PDF Version

  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. Save & Load
    3. Network Sync
    4. Global Variables
    5. Dynamic Variables
  4. Tasks (Actions & Conditions)
    1. List of Tasks
    2. Creating Custom Tasks
    3. Using Task Attributes
    4. Using BBParameters in Tasks
    5. Creating Generic Tasks
    6. The Script Control Tasks
    7. 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 Node Reference
    2. FSM Callbacks
    3. Creating Custom FSM Nodes
  7. Dialogue Trees
  8. Using Graph Events
  9. Working with Custom Types
  10. Working with AOT Platforms
  11. Creating Custom Object Drawers
  12. JSON Import/Export
  13. Scripting
    1. Interfacing with your code
    2. GraphOwner API
    3. Blackboard API
    4. Runtime Instantiation Tips
    5. Creating a Behaviour in Code
  14. FlowCanvas Integration
    1. Behaviour Tree -> FlowScript
    2. FSM -> FlowScript
    3. Using Tasks in FlowScripts
  15. Playmaker Integration

Tasks (Actions & Conditions)

Tasks are the actual Actions and Conditions; the what and if happens. In NodeCanvas, Tasks are assigned to nodes instead of a node itself containing the functionality. This allows for a great modularity and flexibility in design, since it decouples the design from the actual implementation as well as allows the same Task to be used for a variety of different reasons, since the functionality is encapsulated within it. This is a core concept of NodeCanvas.

There are a variety of Tasks included with the package, but of course it is also very easy to create your own Tasks, very customizable using an easy API.

With NodeCanvas, you have two broad options for implementing your own functionality, meaning mostly Actions and Conditions:

  • You can create your own Tasks.
  • You can keep your functionality in your own MonoBehaviours and use the Script Control Tasks to interface with it.
Yes No Suggest edit
3 of 3 users found this section helpful
« Dynamic VariablesList of Tasks »
Suggest Edit