also, i've noticed that if you let the program sit for a while, even if you haven't added any new commands the input buffer seems to flush itself and the next local wait command works properly. then the followup wait command does not work. if i make a trig that does not use the wait command, it works without fail.

i have a question about this. i've been using savitar for a little bit and want to keep using it, but this wait command problem really is a problem. i have a similar setup, trying to use it as part of a trigger by doing:

##wait 1 arma

to cast armageddon, a spell, in a mud i play. i've even tried it on the command line and it does not work properly. it displays it in the output window as if it's sent it, but it's only when i hit return does it actually send the command. and it doesn't matter whether the input box is empty or has a command sitting in it, the command does not execute. the mud gets jibberish essentially, a command it doesn't know what to do with. my question is, are you clearing the program's input buffer before and after executing the trigger and/or the local command? and also, can you add the option to have the input buffer cleared at so many interval, down to millisecond units at least for debugging purposes? that might help some. thanks.