ECS and finite state machine

[rudiHammad]

Hello,
I've been reading about finite state machines and it seems that's the way to go when it comes to handle the player. In essence each state is a class and the player can only be in state at the time. Also, you can define transitions between states. This looks pretty nice.
But this is not really ECS, it is more OOP approach. When making game it's probably a bad idea to try to have everything be in the ECS paradigm. So is FSM one of those exception where it is okey to mix OOP with ECS, or is there a better approach with Entt?
Thx

[skypjack]

It doesn't depend on EnTT. It's more a matter of tastes when using entities and components.
One way to do that is to define your states as components, attach and remove them as needed, and have different systems for different states.
Otherwise, you can have a component that stores all data along with a state identifier, then use an fsm system to update this state representation.
Of course, you can also have a pointer to a more OOP-ish data structure that gets the job done and stay more on the OOP side.
None of these solutions is more right or more wrong than the others. 🤷‍♂️