Ah oki,
so there is no special logic behind this i'm missing. I guess the setup this way, because there is no "clean" register/unregister mechanic in place. So PM can't really implement something like "SendMessageOptions".
Was just curious, i actually try to "fix" this for us, by only allowing the use of known events from a enum, instead of a user defined string. The reason is, that if u can send "lala Event" to a FSM via script code/action and there is actually no "lala Event" locally/globally at all, it's always a setup error, we want to prevent.
Thx for the clarification.
bye Andy