Download

Introduction

Experimental. Support for editing animation trees is early and incomplete. Expect rough edges — the editor will be improved and expanded over time.

Hardcoded parameters & callbacks. The game drives many animation trees through fixed parameter and callback names (via parameter / callback nodes). Those hooks are hardcoded in the engine — adding new ones, or renaming existing parameter / callback nodes, may do nothing or cause issues. Work with the parameters and callbacks already in the tree, and with the values they supply.

Open Edit → Animation Trees to launch the Animation Tree Editor. Animation trees live inside ANIMATION.PAK as ANIM_TREE_DB databases — they choose, blend, and layer clips based on parameters and game context.

This editor is separate from the raw Animation Archive Editor (PAK browse/extract). Use it when you need to inspect or change tree graphs, node parameters, and wiring.

For a full catalogue of node types, parameters, and pins, see Animation Tree Nodes.

Interface Layout

The editor uses a docked layout. Panels cannot be closed from their tabs.

Animation Sets

Left dock — split into two lists:

  • Sets (top) — each animation set / tree database loaded from the PAK
  • Trees (bottom) — trees in the selected set

Type in the search box above the trees list to filter by name (case-insensitive). Changing set clears the search and reloads that set's trees.

Select a tree to open its graph in the centre document area.

Graph Canvas

Centre document tabs show the open tree as a node graph. Nodes are coloured by type. Flow generally runs left-to-right from the tree root (ANIM_Tree_Top_Level).

Pan and zoom the canvas as with other OpenCAGE node editors. Select a node to populate the properties panel.

Node Properties

Right dock — property grid for the selected node. Every node has an editable Name; other fields depend on the node type (strings, floats, bools, enums, bone-mask flags, nested arrays, and so on).

Linked child / parameter references that are wired on the graph usually appear as read-only names in the grid — change those relationships via pins on the canvas.

Editing Trees

Pick a set and tree from the left, then edit on the graph and in the properties panel.

Selecting Nodes

Click a node on the canvas to select it. The properties panel updates immediately. Multi-select follows the graph editor's normal selection behaviour where supported.

Editing Parameters

With a node selected, edit values in the right-hand grid:

  • Name — renames the node in the tree and on the graph title
  • Scalars, bools, and enums — edit inline (dropdowns for enum types)
  • Bone masks — flag checkboxes for body groups
  • Nested arrays — expanded rows for pools and states (for example AnimationPool on randomised leaves, or States on selectors / parametrics). Empty animation pool slots are skipped on save

See Animation Tree Nodes for which fields each type exposes.

Adding Nodes

Right-click empty canvas space and choose Add Node, then pick a type from the submenu (exact ANIM_* names, alphabetically). The tree root cannot be added from this menu — it already exists for every tree.

New nodes appear near the click position. Wire them into the graph with pins, and set parameters in the properties panel.

Deleting Nodes & Links

  • Delete — removes selected node(s) from the tree and graph (the tree root cannot be deleted)
  • Delete / remove link from the context menu — clears hovered or selected connections and clears the corresponding model references

Right-Click Menu

On the graph canvas:

  • Add Node — submenu of creatable node types (empty canvas)
  • Delete Node — delete the selected node(s)
  • Delete Link — remove the hovered connection

Availability depends on what is under the cursor / selected (for example Add Node when clicking empty space; Delete Link when hovering a link).

Pins & Connections

Pins are colour-coded by role and sit on fixed sides of each node:

  • Left — flow input (usually trigger)
  • Right — flow output(s) to child nodes (for example State_01, base_node, NODES)
  • Top — value / reference inputs (parameters, callbacks, bindings)
  • Bottom — value output (usually value)

Connect a provider's bottom value pin to a consumer's top pin. Connect flow outputs on the right to the next node's left trigger.

Parameter, property, callback, and similar nodes typically have no trigger pin — they only expose a value output.

Saving

Use the toolbar Save button in the Animation Tree Editor window. That writes the edited tree databases back into the animation PAK entries — it is separate from File → Save Level in the script editor.