Hi,
ok:
the global event "TRIGGER 2D EVENT" is a global event that my system fires everytime it detects that a 2d collider entered. This is exactly the same as the global system event build in PlayMaker "TRIGGER EVENT".
So, you should NEVER use global events that are fired from frameworks within an action ( within any actions), because then it's not just your action that can fire this event, it's anything since it's a global event, it can be fired from anywhere by anyone!
so, rule of thumbs, ALWAYS create a local event to use in your actions, and so in your "Trigger 2d event" action, only use local events, and you will never get mixed up. "trigger 2d event" does filter by tag, and does a lot more work then just firing an event everytime something triggered that collider.
Does that make more sense?
a typical error as well would be to use a global mouse event such as "MOUSE DOWN" in your action. you may be tempted to do so in a mouse input action, but you understand that then how do you know if it's the action or the system that fired this event? do a test with a cube and an fsm with a bool test action ( that runs everyframe) with the "Is True" firing a "MOUSE DOWN" global system event, leave the bool to false and click your mouse on the cube, the event from the bool test will be fired... oups.... the same confusion goes one on the trigger 2d event and action.
Bye,
Jean