 |
gamesover
Novice
Joined: 06 Jun 2007
Posts: 30
|
 Posted: Fri Apr 30, 2010 8:07 pm
how to build such a busy test function
|
In my mud, there is a busy check command "busycheck", when you input "busycheck" command to mud, the mud system will feedback you the status like "you are in busy" or "you are not in busy".
I wan to build such a function to test whether my status is in busy or not-busy;if my status is in busy, continue to input "checkbusy" command until my status becomes not in busy
#function busy()
{
#execute checkbusy;
#trigger {you are in busy} {#return 0;#alarm -1 {#execute checkbusy}}
#trigger {you are not in busy} {#return 1}
}
however, it seems this function is not worked, what's the problem with it? |
|
|
|
|
Rahab
Wizard
Joined: 22 Mar 2007
Posts: 2320
|
Posted: Fri Apr 30, 2010 8:44 pm
|
The reason is because the #trigger commands _create_ a new trigger. The function will create the trigger, say "Done that line", and continue on to th e next line. It does not wait around for the trigger to fire. And the #RETURN commands in the triggers don't go back to the function, because the triggers are sitting around on their own, in the main thread.
Another problem with your logic is that, even if the first trigger _did_ send the #RETURN to the function, the function would then end. The #alarm would try to do another checkbusy, but the function has already completed and returned a 0.
I think what you are trying to do is create a function which will wait until it gets a "you are not in busy", and then returns so that the calling script can do something? What you probably want is the #WAITFOR command. Have the function start an alarm, which will continue to execute checkbusy until some variable has a value of 0. Then have the function execute a #WAITFOR for the not in busy line. Then have the function change the variable to 0 to stop the alarm, and #RETURN. |
|
|
|
|
gamesover
Novice
Joined: 06 Jun 2007
Posts: 30
|
Posted: Fri Apr 30, 2010 9:44 pm
|
| Rahab wrote: |
The reason is because the #trigger commands _create_ a new trigger. The function will create the trigger, say "Done that line", and continue on to th e next line. It does not wait around for the trigger to fire. And the #RETURN commands in the triggers don't go back to the function, because the triggers are sitting around on their own, in the main thread.
Another problem with your logic is that, even if the first trigger _did_ send the #RETURN to the function, the function would then end. The #alarm would try to do another checkbusy, but the function has already completed and returned a 0.
I think what you are trying to do is create a function which will wait until it gets a "you are not in busy", and then returns so that the calling script can do something? What you probably want is the #WAITFOR command. Have the function start an alarm, which will continue to execute checkbusy until some variable has a value of 0. Then have the function execute a #WAITFOR for the not in busy line. Then have the function change the variable to 0 to stop the alarm, and #RETURN. |
I try to re-write like the following, but it does not work either
#function busy()
{
#result 0;
#alarm -1 {#execute checkbusy};
#waitfor {you are not in busy} {#return 1} {}
}
I want to do the following thing:
1. At the first, the fuction initial value is 0
2. the function do "checkbusy" command again and again(interval one second) until the system feeback "you are not in busy"
3. The function set the value to 1 |
|
|
|
|
MattLofton
GURU
Joined: 23 Dec 2000
Posts: 4834
Location: USA
|
Posted: Fri Apr 30, 2010 10:46 pm
|
Does the game tell you when the busy state changes without you having to use the checkbusy command? If it does, you won't really need a function. Just one trigger to handle those messages, and raise the appropriate events:
| Code: |
#trigger {({busy start message|busy end message})} {
#if (%1 = "busy start message") {
busy = 1
#raise onBusyStart
} {
busy = 0
#raise onBusyEnd
}
} |
You could also extend this to the checkbusy command messages to do the same thing. Also, if checkbusy is a command to send to the game you should more properly use #SEND (first expand and then send to the game) or #SENDRAW (send to the game as-is). |
|
_________________
EDIT: I didn't like my old signature |
 |
|
|
gamesover
Novice
Joined: 06 Jun 2007
Posts: 30
|
Posted: Fri Apr 30, 2010 11:57 pm
|
| MattLofton wrote: |
Does the game tell you when the busy state changes without you having to use the checkbusy command? If it does, you won't really need a function. Just one trigger to handle those messages, and raise the appropriate events:
| Code: |
#trigger {({busy start message|busy end message})} {
#if (%1 = "busy start message") {
busy = 1
#raise onBusyStart
} {
busy = 0
#raise onBusyEnd
}
} |
You could also extend this to the checkbusy command messages to do the same thing. Also, if checkbusy is a command to send to the game you should more properly use #SEND (first expand and then send to the game) or #SENDRAW (send to the game as-is). |
I am sorry. But no such "busy start message" or "busy end message" would show in my mud. In fact, it won't tell you now it is in busy status until you find you cannot do any action
However, you can use a command "checkbusy" to check whether you are in busy status. Feedback is only two kinds: "you are in busy" or "you are not in busy"
Therefore, the trigger given by you is not worked. |
|
|
|
|
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
