This is not okay, sounds more like a bug. Then it might skip the "Wait 0" action too, lol. There's nothing in the manual or tutorials about skipped actions because of a framerate or anything else.
No it cant since "wait 0" action is delayed, as the post you shared says, to the end of event sheet and then performs it.
But when you have 10-20 actions under a condition or is a very cluttered area of conditions and actions in your event sheet and you dont have the "wait 0" between them,and based on your computer performance or browser performance there are some times slow downs of performance.
Maybe because of browser plugins/framework maybe because of your computers outdated drivers, sometimes we have high usage resources and the browser may slow down even for 1 second or less ... at that moment since C2 system is directly responding to how well our computers can run HTML5 and this sort of issues might happen.
This issue was also mentioned many times by Ashley and other developers over the years in the forum posts. The skipping is not directly mentioned in the manual but the performance and optimization is, and its suggesting the slow downs might skip 1 action or the actions might not perform as well as they should. And thats why Wait 0 was implemented. At least thats how i see it and understand it so far from testings and the course of C2 development announcements.
But its not something that C2 can fix. Its more of a Hardware, Software(not only C2 but all dependencies that C2 has), and user usage mix problems.
Which C2 is developed and patch so often to avoid bad performances like this.
Another example that is based on performance and the limits of HTML5 are the jitters that always pops up around forum, that are caused by the html5 platform and how well the Math is made in the Core's Engine.
But this pushes the topic back to the eternal conflict between developers on having to choose from HTML5 or flash. Since immediately flash is/was a bit faster but still has more problems then HTML5 itself.
In a few more years maybe all this will be behind, with the technologies and the software that is continuously updated. Till then we(the normal inexperienced flock of users) cant do nothing but wait. And submit bug reports or performance issues.
And then another short note on user usage of software ... most C2 developers tend to not have a clean code... keeping their event sheet all unoptimized and having blank conditions under blank conditions under functions over functions that basically do nothing just delaying the system and then as mentioned above issues pop up.
And the unoptimization of a code it can bring performance down quite visible in some cases even close to unusability of an app.
Because 1 condition in blank its another maybe 0.001 % tick delay based on the amount of conditions and actions we have in our event sheet, and on large scale games that 0.001% can get pretty high stacking.
I'ved seen capx's that where like the above example ... having 10 functions under 10 blank conditions and at the end 1 action that was calling another cluttered useless function that was basically repeating same hierarchy just calling another action or condition ... which did not make sense at all.. and the app at that moment tested was performing really bad maybe 1% of what it should have been.
So it all comes down to all this things that combined kills performance, on a newly platform called HTML5 that still has years to be developed in order to get perfect and fast enough. Even though, i personal consider it fast enough at this point for what most people use it for on the side of C2.
I could go on... but im way off-topic and this kind of talking wold be better discussed in open topic then C2 General.
Im not sure if you still understand now why "action skipping" might happen. And why "wait 0" wont be skipped. But you already shouldve noticed all this by now ... since your not a new C2 user lol ... have a great day all