Ok, that's a big one. I could not reproduce outside of my current project and I obviously cannot share it here.
I observed other bugs related to events at runtime, I'll have to do a complete check up later on, but for now I'm reporting this and I will return to it with further tests.
For some reason, events that always managed to send the data they got associated with suddenly decided not to work anymore. The process of setting the data in an event was not altered, nor were the targeted FSMs receiving said events and their respective data.
Luckily for me, set/get properties for events still worked. So today, I would not know how to reproduce this issue and it still puzzles me, it might be due to the complexity of the exchanges of events between FSMs.
Hopefully I will be able to identify the cause of this problem that appeared out nowhere.
