Ask one question

Conditionals inspect game state and return Success or Failure without performing the main behavior. Examples include comparing a variable, checking a collision or trigger, testing an Animator state, and Has Received Event.

Keep a Conditional focused on one readable question, such as Can See Target? or Is Health Low?. Store discovered data such as the current target in a Shared Variable so a following Action can use it.

Make a branch reactive

A normal Conditional runs only when traversal reaches it. Configure a Conditional Abort on its parent Composite when the value must be reevaluated while another task is Running.

Use Writing a New Conditional Task for a project-specific check.

Used in common behaviors