How to ensure a state machine runs before another?

[Sirmadeira]

Let say I have an animation state machine, and I want to check for a condition before hand if player is flying or landed. How can I estabilish run conditions between two state machines?

[Seldom-SE]

It is not currently possible. I'm open to it, though.

I've tried adding generics to StateMachine before, so that you'd put multiple on a single entity. The API ended up pretty terrible, though, so I scrapped it. Something along those lines could work for this, though. It could use a generic wrapper component, like struct AnotherStateMachine<T> { machine: StateMachine, _t: PhantomData }, and then you add an additional plugin for each additional AnotherStateMachine component you use, and you'd be able to configure the schedule/system ordering per-plugin. It's pretty jank, though.

Another idea is optional sort key components that you configure in the plugin. I think there's a function on Query that lets you iterate sorted. Maybe that's 0.16.

[Sirmadeira]

It is janky but I guess it could work. Ought curiosity, lets say you have an state for forward walking, backward walking and so on. How could you avoid reentering the same state, over and over again.

[Seldom-SE]

If you're transitioning from AnyState to ForwardWalk, you can instead transition from NotState<ForwardWalk> to ForwardWalk

[Seldom-SE]

I'd like to keep this open until I resolve it