Features:

The definition of a state machine is done entirely in the blueprint editor and can coexist and mix with “normal” blueprint logic. GC FSM does not rely on the behaviour tree or the animation editor, so blueprint logic stays where it should be.
You can create re-usable state classes for recurrent tasks both in blueprint and in C++. Blueprint state classes can run state machines too, allowing a natural hierarchical structure.
Transitions between states are triggered by events, allowing you to de-couple the logic and complexity of the state machine from the higher-level game logic.
Any object can run state machines, not just actors. You don’t need to jump through hoops to create a state machine in non-actors, such as actor components. An object can run multiple state machines at the same time.
You can debug state machines within the blueprint editor itself and monitor the flow of events in the Unreal Visual Logger.

Network Replicated: Yes

Supported Platforms: All. (Mac and iOS support requires Unreal 4.20 or later)

Gamecentric

Product types