Hi,
Due to the wrapped up nature of Fsm, states , actions and fsm variables, I don't think this kind of framework are suitable as is. because they actually go through the script itself to find what to serialize, and it won't be able to access a playmaker Fsm. It would require a specific implementation to understand and work with playmaker.
I would instead take level saving and loading in consideration right from the beginning of the thinking process to implement routines and patterns in each Fsm to account for this. that's a lot of work. IF Fsm could be saved as a xml, this would be trivial, I have been mentionning this several time actually, and this is actually going further, meaning saving a Fsm not just by its state during editing, but also taking a snapshot of it at runtime, and be able to load it back whenever and start from there. That would be quite good indeed, but would need to be something built in playmaker, not sure that it's possible to do that with the current playmaker api ( It might very well be tho)
bye,
Jean