zyr17
commented
7 months ago Directly finish all existing actions introduce bugs. Maybe changing SkillEndAction etc. by filling EventArguments directly into frame can solve the problem?
And it will also effect history recording, need to change.
Currently we allow event triggering immediately after it is generated. A better logic may be: when an object gives multiple actions, we need to execute all actions then deal with events.
Currently there exists actions that purely describing events (e.g. SkillEndAction, only used to create a SkillEndEventArguments), and we cannot execute all of them directly (but maybe we can?).