The error again and again and again....

Hello engine developers and power users.(Ashley Tom)

👀You may have also noticed this global error that occurs again and again for newcomers. I believe it turns away a fairly large percentage of newcomers from a successful start on Construct3.

I don't want to say that this particular screenshot is unique, but this problem is so frequent that we need to do something about it.

👍For some reason, newbies don't have any problems with the trigger condition (green in the screenshot).

👎And for some reason, they always have a problem with regular conditions, they don't realize that such conditions are executed more than 60 times per second and add time-consuming events to them. And then, of course, it doesn't work for them (red screenshot)

🧠Perhaps you can somehow warn the user about this every time they create such a condition and warn or somehow mark it.

The team is fighting a daily battle to improve and develop Construct3, but such cases are very dangerous because among the thousands of new people who choose the engine every day, only hundreds choose Construct3 and 50% of these newcomers get broken code because of such event loops.

🙄And they just leave and don't come back.

I agree that a warning could be helpful for some new users, but I'm worried most people would ignore it and keep making the same mistake.

I think the way the event system works tends to encourage beginners to put every action in a new top-level event. The result is the same messy code which I keep seeing almost every day: