Executable Item
v1.0
Overview
ExecutableItem is the base class for all items that can be executed by an ActionExecutor. There are two concrete implementations:
ActionItem - Wraps a single
Actionasset and executes itGroupItem - Contains multiple
ExecutableItems that execute in parallel with configurable exit conditions
Both types support conditionals, chance-based execution, looping, and runtime lookup via unique identifiers (UIDs).
ActionItem vs GroupItem
An ActionItem represents a single action from your Action assets.
A GroupItem represents a collection of items. Groups can contain both ActionItems and nested GroupItems. Group Items have exit conditions, which determine when the Executor will start the next ExecutableItem.
Barrier
Wait for all items to complete
Synchronized animations, coordinated effects
Race
Complete when first item finishes
Competitive animations, interrupt-driven sequences
Timed
Complete after a fixed duration
Time-limited effects, fire-and-forget groups
Looking Up ExecutableItems by Unique ID (UID)
ExecutableItems by Unique ID (UID)Every ExecutableItem has a unique identifier that's automatically generated and persisted. This can be modified to a custom string in the Inspector, when viewing any Action Executor.

You can look up items in any ActionExecutor programmatically using their UID.
Working with ExecutableItems
Accessing Items from ActionExecutor
Modifying Items at Runtime
Filtering Items
Common Properties
All ExecutableItems share these properties:
Basic Settings
Conditional Execution
Looping
Runtime Loop State
Working with ActionItem Overrides
ActionItems support per-instance overrides without modifying the original Action asset.
Duration Overrides
Field Overrides
For fields marked with [CanOverride] or [MustOverride] in your Action:
Working with GroupItems
Accessing Group Contents
Modifying Group Behavior
Advanced: Dynamic Item Management
Adding Items at Runtime
Removing Items
Validation
ExecutableItems provide validation to help catch configuration errors:
Common Validation Issues:
Missing action asset reference
Chances outside valid range (0-1)
Invalid loop count
Empty groups
Invalid conditional configuration
Best Practices
Use UIDs for Persistent References
Cache Item References
Validate Before Execution
Use Groups for Coordinated Effects
Use Conditionals for State-Based Execution
See Also
Last updated
Was this helpful?