We're in the process of completely rewriting the event sheet editor right now (every line must go) as it's in rather terrible shape.

Once that's done this is one of the first features on the list, along with many others we'll then be able to add as a result .

That's really peculiar, generally it's just a few which don't load.

I'll read more into DEP and try figure this out.

Another timely bump

Come on!

PICTURESSSS

Hmm, which plugins do this? And why precisely don't they load.. can you explain in a bit more detail?

Thanks for investigating .

I'm sure David wouldn't mind .

Have a go and see what you can make.

Wow, the graphics in the link you posted are stunning. I really hope someone here makes something out of some of these at some point..

I just played the third Construct entry in competition. Afterlife Consequences.

It's pretty bad. Even the creators admit that it's pretty bad. The person in charge of making the game apparently decided to start using Construct at the beginning of the competition, so he had no idea what he was doing. The results definitely reflect this fact.

What makes me a little sad is how he's constantly bagging on Construct the whole time, like it's Construct's fault he's made a bad game. He also states that Construct is just an "insane wall of bugs." He only mentions a couple of bugs in the thread, only one of which he posted about here in the Help forum, which was already a known issue and he actually found a fix for it anyway (the other is the IDE crashing when editing sprites... sounds like a hardware issue to me). The rest is just design issues... he's complaining about animation and hitbox problems that aren't actually bugs and are easily remedied, and all he had to do was ask. Hell, he didn't even have to ask... there are plenty of threads that talk about hitboxes and animation already.

Sigh. When scytos mentioned there was a third Construct entry, I had some higher hopes for it than this. Oh well.

Well.. I don't really mind that he calls Construct buggy, he did encounter an annoying bug. What would be better is transferring the criticism into bug reports - which he has done with one bug, and it got fixed. Hopefully with more of these reports we can change Construct from an 'insane wall of bugs' into a rose scented stallion.

Beautiful grass that

If triggered events just ran normally with evaluated conditions it'd be pretty silly: the point of a triggered condition is that it runs when the event happens, not after or in another order.

For example, hitting a key would call all triggered events which ran when that key was hit. Key is down would run in the normal order if the key happened to be down.

This is now fixed.. it was code from when event sheets weren't in the Project Bar messing up.

Whilst there's clearly an annoying bug here - which I'm looking into - you can just use names in your Go To Layout action, which is probably the better solution anyway (what if you wanted to re-order your levels/layouts after you'd added a lot of these events?).

Yeah, your cap file is fine .