OneMoreNameless
Level: Master Delver
Rank Points: 131
Registered: 07-31-2010
IP: Logged

Simple enough suggestion. Right now 'wait for event' (I think?) only triggers the first time the relevant event occurs, which kind of reduces a lot of their potential. What I'd suggest is adding another option to side, between 'has occurred' (eg. any trapdoor has been dropped) and 'next occurrence' (eg. wait for another trapdoor to drop).

Unrelated note, and knowing this has been suggested before, required target should not imply vulnerability. It's not strictly true and kind of nixes my plan for custom enemies only killable after / while X.

Jatopian
Level: Smitemaster
Rank Points: 1842
Registered: 07-31-2005
IP: Logged

I'm not sure I understand your first request, but I agree with your second.

____________________________
DROD has some really great music.
Make your pressure plates 3.0 style!
DROD architecture idea generator

Someone Else
Level: Smitemaster

Rank Points: 1306
Registered: 06-14-2005
IP: Logged

I quite agree with the second one. Basically, the first one is to check whether the event has happened up to this point, but not wait until it happens. For instance, you could check to see whether the player has entered a certain area yet, or struck any orb.
The second one is better done by using two characters, using variables that are changed by one of them at certain points. The way that you suggested, OneMoreNameless, would have issues with having to check the entire demo, and be really slow.