Interesting that these two comments below showed up next to each other... try this... make a new capx that does NOT use the solid behavior and code one yourself in C2 events that runs every tick which checks for overlapping rectangles and pushes any rectangle that crosses back out one pixel so it does not overlap... this will show you that it is just Logic and both code and C2 events are just Logic...and that you can either use Behaviors (code components) for speed or make your own with Logic if they do not have all the features you want.
[quote:1jj44w39]@megatronx
That's why instead of long events I break them in to smaller parts, put them in to separate event sheets and chain them with functions most of the time. Much easier to find an issue if there is one.
But what pisses me off about construct is that I just can not do certain things with events. Like the infamous solid behavior limitations.
[quote:1jj44w39]
Tokinsom
Far as I'm concerned, the behaviors and all the built in stuff are to blame. Most other engines have you make your own platform engines and such, as well as level editors, data tools, etc. With C2 you don't really learn much of anything...so if you start with C2 you'll likely always be a "noob". Not to say I don't appreciate behaviors and all, but ultimately we'd be better off with more features to make our own exactly how we want..