 |
Spartacus
Wanderer
Joined: 23 Apr 2001
Posts: 53
Location: USA
|
 Posted: Mon Mar 07, 2005 10:56 pm
#WAIT
|
In order to earn the pathetic newbie title that I seem to have here, I created a system to assist fishing on Achaea, and since precise timing is desireable in thie endeavor, I used #wait followed by a variable containing the number of miliseconds to wait.
Then I started seeing zMud stop responding firing triggers completely sometimes, which was bad. So I read the docs and observed that this behavior is documented - shame on me for not reading the docs closer at the beginning... 
Now I have two related questions;
First - Will #WAIT without an argument cause the same behavior.
Second - Will #ALARM recognize intervals smaller than 1 second (i.e. when I do #ALARM {+2.3} will it fire in 2 seconds, 2.3 seconds, 3 seconds or something undefined?)
Thanks! |
|
_________________
Spartacus
rm -rf .* |
 |
|
|
Dharkael
Enchanter
Joined: 05 Mar 2003
Posts: 593
Location: Canada
|
Posted: Mon Mar 07, 2005 11:02 pm
|
#ALARM does recognize values smaller than a second #ALARM {+2.3} will fire in 2.3 seconds
check out the %alarm function, which can be used to see how long until an alarm fires
You'll see that the values it returns are in milliseconds |
|
_________________
-Dharkael-
"No matter how subtle the wizard, a knife between the shoulder blades will seriously cramp his style." |
|
|
|
MattLofton
GURU
Joined: 23 Dec 2000
Posts: 4834
Location: USA
|
Posted: Mon Mar 07, 2005 11:35 pm
|
yes, #wait without parameters will cause the same behavior. It stops trigger processing for the specified time; if you do not specify a time it defaults to "whenever a new line comes through" which could be anywhere from .01 to 1000 seconds from now.
If you need a wait, use either an #ALARM or a wait-state trigger (one of the states available in #CONDITION). |
|
_________________
EDIT: I didn't like my old signature |
|
|
|
|
|
|
