Skip to content
Bit Quirky Behavior Trees and
State Machines

Search documentation

All topics and APIs

Close returns focus to Search.

What are you looking for?

Try a common topic or enter a complete API identifier.

Browse the reference instead

Esc closes · Tab reaches results · Enter opens the focused link

v0.11.0
Menu

Attach and inspect

Attach Live to the exact agent you mean, read what the toolbar says about it, and open the values behind the decision it just made.

Attachment is exact. You select one agent, the editor opens that agent’s graph, and it never quietly hops to a nearby candidate that looks similar.

Platformer’s Enemy Platform carries two Behavior Agent components: one runs EnemyPatrol, the other runs EnemyStateMachine. Dungeon Heist has several guards, each running its own instance of the same graph. In both cases “open the enemy’s graph” is ambiguous until something names the graph, and a debugger that guesses is worse than one that asks.

  1. Press Play. Attachment needs a running, initialized agent on an active object.

  2. Select the object, or select the exact Behavior Agent component. Selecting the component is always exact. Selecting the object attaches when exactly one of its agents is eligible, or, when several are, when exactly one of them runs the graph the editor is showing. With EnemyPatrol open, selecting Enemy Platform in the Hierarchy attaches to its EnemyPatrol agent.

  3. Read the toolbar. The mode control shows Live, the identity names the follower you hold, and the attachment word reads ATTACHED.

There is no list to pick an agent from, by design. You select the agent and the window follows that one attachment until its identity changes.

The Live segment uses that same selection. If you switched the window back to Static, press Live during Play and it attaches again to the agent you still have selected. When Live cannot open, it reads dimmer than an available segment and does not light up under the pointer. Hover it and it says whether you need to enter Play Mode or select the agent running this graph.

Reading Meaning
ATTACHED Bound to a live runtime
DETACHED No active binding, including after you select an object with no agent: the instance keeps running and keeps its live edits
LOST The runtime is no longer reachable: it was destroyed, reset, replaced, or reimported
GRAPH LOCKED Live cannot author the graph. Eligible value fields still edit the attached instance
Tick The effective tick rate in Hz, sampled from the agent’s own ticked frames

The status bar keeps the same story in words, reading State ticking · Tick 60.0 Hz for a behavior tree and Player attached · 60 Hz for a state machine. The follower identity is clickable, and its popover carries a Follower id field with View Id and View Selected. In this release neither button changes the attachment: Unity selection is the control, and the popover reports the follower you already hold.

A Live document is pinned to the runtime you selected: the component, its runtime generation, the graph asset, the executable fingerprint, and the follower key. Reinitializing, resetting, replacing the graph, or reimporting the asset with different executable content changes that identity, so the document detaches rather than showing one graph beside a different executable.

When an attachment ends, the graph stays open: the canvas shows a Detached card, every member card clears its runtime values, and the Blackboard values rows read cleared. Selecting an object with no agent reads DETACHED in the toolbar and detached · no running agent selected in the status bar; a runtime that is gone reads LOST, with runtime binding lost for a behavior tree and Player lost for a state machine. Selecting the same still running target attaches afresh. Leaving Play Mode is different: no runtime is left to view, so the window returns to the graph’s Static document, ready to edit.

With nothing selected on the canvas, the rail carries the attached agent’s values in two sections, and they behave differently on purpose.

Member binding, marked surfaced, holds one card per member binding the graph surfaces. A card shows the value the graph received and the value on your component, states its health, and turns into an editable field when the binding may write the member.

Ten surfaced Guard_2 member cards under Member binding: catch_reset_position and liveFocus have read-only locks, focusPosition has an unavailable triangle, the alarm and indexed waypoint bindings sit between them and editable patrolSpeed at 2.2
Figure 1. Guard_2’s ten cards. The locks refuse edits to read-only values, the triangle marks a missing focus, and the editable fields include patrolSpeed. Live editing reads each card’s details.

Blackboard values below it is a read-only snapshot of the whole blackboard, with one exception: a graph that binds an explicit shared numeric source leads the section with a SHARED card instead of a plain reading, editable in place. Every other row’s details arrow opens the words Read-only runtime snapshot and a Pin toggle, so the rows you care about stay at hand; it is the place to confirm that an input changed before the branch evaluated.

The current Guard_2 Live Blackboard values section with its search field, the All, Host, and Client filter, HOST AUTHORITATIVE 31, and read-only rows for clear_sight, catch_distance_reached, and player_position components
Figure 2. A guard’s 31 live blackboard values, grouped as a read-only snapshot. Each row has its current value and a details arrow, not an edit field.
The Behavior Tree Editor’s Blackboard following the running director: the SHARED group holds wave_difficulty at 1 with a shared WaveDifficulty chip, above the director’s private HOST AUTHORITATIVE rows.
Figure 3. Horde Survival’s running director: the SHARED card names wave_difficulty as shared WaveDifficulty, distinct from the private rows beneath it.
The same SHARED wave_difficulty card now reads 1.75 and is tinted as just changed.
Figure 4. The same card after an edit made in WaveDifficulty’s own Inspector: 1.75, with the recent-change tint every refreshed reading gets. Live editing covers typing into the card itself.

A Live edit reaches the one attached agent, runs the member’s setter once, and reaches the graph at its next evaluation, or at the next step while this follower is paused. It never touches the graph file, the document’s saved state, or undo.

  • Graph runtime status names the active node, the current state, the last result, the last transition, and which side owns the values.
  • Pending requests appears whenever the graph is waiting on something external, and names the request and the frame.
  • Selected node details carries that node’s own last result and its live target reading.
  • Recent transitions and events gives bounded context around the current snapshot.

Repainting the Live view observes only. A refresh never invokes a member, evaluates the graph, writes a slot, dirties the file, or advances a tick.

When it goes wrong

SymptomCheckFix
Selecting the object opens nothing.Count the eligible agents on it, and the ones running the graph the editor shows.Open the graph you want first, or select the exact component. An object whose agents leave none or several running the open graph attaches to nothing on purpose.
In a Static window, Live reads dim and does not light up under the pointer.Hover it for the reason.Enter Play Mode, then select the Behavior Agent running this graph, or its GameObject if no other agent there runs it.
The toolbar says LOST.Look for a reset, a graph replacement, a destroyed object, or a reimport.Each of those changes identity. Select the running target again.
The follower popover will not switch agents.That is this release: the buttons report the follower you hold.Select the other agent in the Hierarchy instead.
A blackboard row will not take an edit.Open the row’s details arrow: it says Read-only runtime snapshot.Edit the authored default in Static, or use a two-way member card for an instance edit.
A member card will not take an edit.Open its details and read the chip: read only, unavailable, or incompatible, each with its reason.Live editing lists what each refusal means and what to change.
An edit was accepted and nothing changed yet.Read the toolbar: resume in place of pause means this follower is paused. The rail’s Evaluation section reads Waiting for Step.Step once and the graph reads it, or resume.
Full-size image