construct caps 0.1

guide was lost forever.

Looks like it'll be a good article! Going to put it on the wiki?

+ On "Punch" control down

->Trigger Once

This event looks confusing, you probably don't want to use it as an example. 'On punch down' looks like a trigger (ie. on key pressed) and therefore adding Trigger Once has no effect. You could have 'Is key down' and 'Trigger once', but why would you do that instead of 'On key pressed'?

You could have 'Is key down' and 'Trigger once', but why would you do that instead of 'On key pressed'?

meant "Punch is down", I'll edit it next time. The reason I use key down and not pressed is because I had problems with it, just using the key down with custom press always seems to fix it though. I like it better anyway because it's more consistent when you are using it for all three states; press, down, and released. And I don't know I've never posted on a wiki before.

I use 'key is down' and 'trigger once' together because of the triggered events not running in the normal order of the event sheet.

Why is that, btw? What's the point of having triggered events not run in the normal order of the event sheet? All it seems to do is screw up the order, which messes up the code sometimes, since the order the events are checked/run is important - why reorder them?

For that matter, why are some conditions 'triggered' and some not? What's really the difference between 'on click' and 'key is pressed'? What makes an event a 'triggered' one instead of a regular one?

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.