Save a state in a FSM

[Domus]

Problem: I have a very simple game manager in my game (see attachment)

Each time a player clicks on a defined object, an event is sent to the game manager that says that this object "it was clicked". Game finish when you have clicked all the object.

I'd like to save the "state" of this FSM when the player exit the game.

Question: Is possible to let the player load the game and start this fsm with another state as a start state?
Hope what I'm saying makes sense.
I'm also experimenting with easy save to achieve that!

Thanks!

[djaydino]

Hi.
You can use the system event "APPLICATION QUIT" on a separate fsm

then in that fsm use 'Get Fsm State' to get the state name.

Then when you restart the game use 'Go To State By Name' (Ecosystem)

On the fsms that you want to start from a different state you might want to change the start state.
As on enable it will already start from there.

So you could have a start state not connected to anything
and use the 'Go To State By Name' with a default value (Idle)

[Domus]

Oh.. WOW. It works! Easy and straight to the point! Thanks!

[Broken Stylus]

That's a very good case of the use of GOTO and that reminds me that Playmaker's Graph View should really provide more clues and tracking regarding the use of GOTO actions, like for example the fact that a state is actually targeted by a GOTO action, somewhere.

[djaydino]

Hi.
The Go To State By Name is a custom action and 'kind of a hack'

In the backend of a fsm it uses a 'Set State' which you also can used on animator events btw.
It can't really be tracked as it just uses strings

[Broken Stylus]

Indeed many things in Playmaker use strings which does prevent the tool from being self aware. Now, a global file or some proxy component of some kind that mirrors those string entries and does the linking, acting like a little database, might solve this.