UniState for character states

[yukey123456]

I read the section about performance, and according to the documentation UniState seems to be much faster than a typical state implementation using MonoBehaviour. However, in my case I want to use UniState to manage the Player's state in Unity (Idle, Moving, Attack,..). Would using the regular Update() loop be more optimal, or using UniState instead?

From some discussions I found online, it seems that continuously updating states in Update() might perform better than using UniTask.Yield() for state updates. Is that correct?

[bazyleu]

Yes, UniState is a better choice than a MonoBehaviour-based state machine, but if your player FSM is very small and can live in one Update() with a simple switch, that will still be the cheapest option in raw performance.
For something like Idle / Move / Attack, I would keep plain Update() if the logic is small. But if you expect the state machine to grow, I would use UniState, because the overhead stays small while the code becomes much easier to scale and maintain.

If you go with UniState here, I suggest bind states as singletons and disable history on state machine for your case.

[yukey123456]

Thanks for the explanation and the suggestions! In that case, I’ll probably go with UniState for my player FSM, since I expect it to grow and need more features later on.