GC FSM - Event-driven, hierarchical finite state machines in blueprint

[miko1a]

@DsyD

Just an idea for save/reload: Some kind of functionality that makes it possible to go directly to a state only when the FSM is launched might work? So in order to use it again, the FSM must be stopped and restarted. That might be enough of a deterrent to prevent bypassing the graph structure willy-nilly…

My two cents If your SM has a chain of states each of which changes game state somehow it can be incorrect to just skip to the last one when game is loaded (assuming the game state is complex). Or you will need to carefully duplicate logic in each state somehow (thinking about which state game is allowed to be saved in etc.). I would just trigger events in the same way both during the game and when game is loaded to ensure game state consistency.