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. Blackboard Parenting
    3. Global Variables
    4. Dynamic Variables
    5. Network Sync
    6. Save & Load
  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
    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. Creating Custom Object Drawers
  14. JSON Import/Export
  15. Scripting
    1. Interfacing with your code
    2. GraphOwner API
    3. Blackboard API
    4. Runtime Instantiation Tips
    5. Creating a Behaviour in Code
  16. FlowCanvas Integration
    1. Behaviour Tree -> FlowScript
    2. FSM -> FlowScript
    3. Using Tasks in FlowScripts
  17. Playmaker Integration
  18. Full API

The "Self" Parameter

By default, a Task will execute for the same agent as the one that the behaviour is executed for, or in other words the game object that the GraphOwner is attached to. You are though able to override this through the task inspector and instead specify another agent for the task to work with. You have two options when overriding the agent.

  • Assign a reference object directly.
  • Select a Blackboard variable of the same or an assignable/convertible type.

TaskSelfParameter

On the task inspector, the type in the parenthesis state the type that the agent needs to have in order for the task to work correctly and without errors. If that type of component does not exist on the current agent, it will show in red.

Yes No Suggest edit
21 of 22 users found this section helpful
« The GraphOwner ComponentBBParameters »
Suggest Edit