> For the complete documentation index, see [llms.txt](https://docs.msquared.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.msquared.io/creation/unreal-development/features-and-tutorials/the-animated-crowd/crowd-animation/crowd-anim-blueprint/reference-guide-abp-nodes/states-and-state-machines.md). # States and State Machines ## State

State Properties

#### Supported Properties * Check Mark Graph Node * Fully supported * Cross Mark Animation State * Cross Mark Events ## State Alias

State Alias Properties

#### Supported Properties * Check Mark Graph Node * Fully supported * Check Mark State Alias * Fully supported ## State Machine

State Machine Properties

#### Supported Properties * Check Mark Graph Node * Fully supported * warning Settings * No settings here are directly supported, all of these settings are ignored. * In terms of transitions per frame and max transition requests, crowd differs from regular ABP execution since it doesn't enforce limits. *However*, these transitions aren’t quite the same as Unreal’s transitions. * With Unreal, if a transition is passed through, it gets played. If we execute 3 transitions in a frame for example, these will all typically get played back, blending from one to the next * With crowd, if a transition is passed through, it’ll do nothing. * Example: If we transitioned Idle → Walk → Run states in a single frame * Unreal would keep these transitions and blends playing back over multiple frames (i.e. idle would be playing, blended with walk. The result of this would be blended with run) * Crowd will just skip out walk in the middle, and blend idle with run * Cross Mark Functions * Cross Mark Tag ## Conduit

Conduit Properties

#### Supported Properties * Check Mark Graph Node * Fully supported