I wanted to consolidate this into a proper feature request thread, rather than it continuing to hang around in some erroneous bug reports. Consider this a "
twin request"
that also applies to regular DROD.
Here's the main problem:
Certain events under the "wait for event" command have restricted compatibility with other commands that normally work with "wait for..." commands. Examples include "
bomb exploded"
and "
tar/gel/mud baby formed"
. I don't even know whether there are others or not because I haven't tested every single event. There's a pretty good reason for this incompatibility that has to do with turn processing order, but the end result is confusion and irritation when trying to use the "
wait for event"
command to actually do things in any remotely complicated script. So, I have two branches to this request:
1) Address the fact that these commands don't work in an "if" statement.
As things currently stand, "
wait for event"
has special processing that allows a character using the command "
naked"
to do things
after the normal processing of characters. This allows for a workaround where a "
helper"
character runs that command, and sets a flag variable whenever the event happens that will be read by the main character in the following turn. So my first proposal is to have the scripting engine do this itself instead of making the architect do it every time. That is:
If...wait for event [whatever] should be "true" on the turn AFTER the event happens. This is slightly unintuitive, but it's much better than it never doing anything at all. I'm imagining the flag that makes the command behave like "
true"
inside of an if condition to be a separate thing from whatever characters using the command "
naked"
would read from, to avoid any issues with that.
Failing my first proposal,
it should be made very clear that if...wait for event [whatever] DOES NOT WORK. I'd like an "
error asterisk"
like the one that shows up next to an invalid "
set var"
command, and maybe something in the help docs clarifying that these things don't work. It'd be a lot better than being ambushed by something not working, and having to learn the hard way that it's due to turn processing order sorcery.
2) Make these work with "wait for any/all/one".
If I want to know whether a bomb exploded OR a tarstuff baby if any kind formed, as things are right now I need 4 (FOUR!) helper characters for that. It would at least alleviate the problem quite a bit if those events worked with the "
wait for any"
. And...them working in "
wait for all"
and "
wait for exactly one"
groups would also be nice. Previously posted replies to some related threads give me the impression that this is possible, but if not, then at least making it clear that they don't work here in the same ways as above would be helpful.
____________________________
109th Skywatcher
Here are some links to Things!
Click here to view the secret text
[Last edited by Xindaris at 09-12-2025 10:40 PM]
