About the Reference#
Summary
The Reference catalogs Visual Script's Triggers, Conditions, Instructions, and Signals. Use it to look up a node's parameters and behavior when configuring an Event.
Reference entries come from source code
Node entries are generated from the asset's source code. If an entry differs from your installed version, check the release notes for changes.
How to use it#
If you're learning how a system works, start with its Manual page. Then use the Reference when you need the exact parameters of a specific node.
Search for the node at the top of this site, or browse the catalogs below. They use the same organization as the editor's dropdowns.
Visual scripting#
These three node types determine when an Event runs and what it does:
- Triggers — listen for an action or state change and start an Event.
- Conditions — check the state of the game and return
trueorfalsewithout changing it. - Instructions — perform actions such as moving objects, changing values, loading scenes, and waiting.
See the Visual scripting overview for how the three fit together.
Signals#
Signals are the typed fields that supply values to every node. The catalog is grouped by the type of value produced, mirroring the dropdowns in the editor.
Reading an entry#
Each entry lists:
| Part | Is |
|---|---|
| Title | The name as it appears in the editor. |
| Category | Where to find it in the dropdown. |
| Description | What it does. |
| Parameters | Each configurable field and what it means. |
| Keywords | Additional terms the editor's search matches on. |
| Notes | Caveats and behavior worth knowing. |
If a title search doesn't find the node you need, try a related term. The editor also matches keywords, so you can find a node using words that aren't in its name.
Nodes that aren't listed here#
Two categories won't appear:
- Nodes from other packages. Anything you install alongside Visual Script documents its own nodes.
- Nodes from the Registry. Community-published content is documented on its own listing.