Another example of the above bug that happens to me:
- create an FSM template that has no global events,
- put it on an object, test, works, no problem,
- then modify the FSM template by adding a global event to it,
- now when you go to another FSM and try to send an event by using the "Send Event" action you can't because the newly added global event does not appear in the drop down list.
- You can of course use a "Send Event By Name" and specify the global event with it's name, then when running and testing it will work.
But similarly to the previous example if the object with this modified FSM template is disabled at start, then you can observe that at first, in the playmaker editor you can see the previous version (the one you created the template FSM with) of the template FSM there. Then when the object becomes activated and the global event is called, the new up to date version of the FSM appears, messing up the playmaker editor a bit.
I hate this uncertainty! Not being sure that I can trust the tool that it will do what I specified. ARGH!!!!