A rather complex state machine.

A rather complex state machine.

The State machine will let you create your own interaction rules to do realtime control of all your system. As the name says, it's a state machine, which means you can create different states, each one being a group of rules that you can activate or deactivate as you wish. You can also create transitions between them, allowing to create evolving interactions.

When creating an interaction, you will first have to create a state that will contains the rules.

<aside> 💡 **SHORTCUTS

</aside>

States

States are containers that will contains different interaction rules. They can be activated and deactivate manually or automatically, and you can create transition between them.

Currently, you can 2 type of rules : Actions and **Mappings.**

When creating an interaction, you will want either punctual control to trigger commands : these are **Actions,** or continuous control to link input values to parameters : those are **Mappings.**

<aside> 💡 Special processors : There are 2 indirect processors : **Multiplex** and **Conductor.** These are "meta" processors, as they don't have direct action, but are specials containers for Actions and Mappings. Check out the dedicated pages to know more.

</aside>

Transitions and State network

Transitions have multiple use cases :

<aside> 💡 At all time, there is only 1 active state inside a state network. This is why creating transitions between multiple states is helpful when you want to ensure that there is only one active state at a time in a group of states.

By not linking them altogether, you can have as many state networks as you want, meaning you still can have multiple active states at the same time.

</aside>