 |
chris1285
Newbie
Joined: 21 Aug 2004
Posts: 3
|
 Posted: Thu Aug 26, 2004 3:48 pm
help with #SLOW/#pause
|
i wrote a simple combat bot for my mud, the layout is as follows:
#class {autokill}
#TRIGGER {Chris killed *.} {#T+ akill;#TS 4;#TIMER on}
#class 0
this is the part to stop and kill the mob
#class {akill}
#TRIGGER {A Monster} {#PAUSE;#TIMER OFF;#TS 4;kill swampling;#T- akill}
#class 0
to walk the area, i have an alias that does the following:
#T+ 'akill'
#T+ 'autokiller'
#slow .3es2ws3hsh2nk2nl2lj
#pause
#ts 3
the command the timer sends are: #STEP;#PAUSE
the idea is that after the slow walk path is set, it will pause it, meaning only 1 direction was sent, then if there is no mob present, the timer will send another direction, however, if a mob is present, the timer is disabled, set back to 3 seconds, then the mob is killed. When the mob dies, the timer is once again enabled and it starts walking.
the problem is, itll enter the room, see the mob, those triggers will fire, the timer will stop, and it will send the attack mob command, then it'll just start sending in directions that i can't control, i try spamming #PAUSE and #STOP but it never stops sending the dirs until i close zmud and get error codes. so essentially what i want to fix is #SLOW or #STEP from sending multiple directions at once instead of one by one like it should.
also, to try and fix this i changed my speedwalk delay to 500, still didnt work |
|
|
|
|
Falan
Wanderer
Joined: 17 Aug 2004
Posts: 98
Location: OK, USA
|
Posted: Mon Aug 30, 2004 11:19 am
|
If your mapper is open while autokilling, then it will read the MUD's exit lines during combat and register an #OK each time. The #OKs confirm the pending slow walk directions. Make sure the mapper is closed when autokilling. Or, use a variable list of directions instead. It's a little more complicated, but saves the headache and allows continued use of the mapper. I'm not sure, but you might be able to simply auto-disable the Mapper while autokilling via the #MENU command.
| Quote: |
OK
Syntax: #OK
Related: #SLOW #STOP #STEP #PAUSE
Confirms the currently pending slow walk direction. This command is typically triggered by a macro to indicate that the previous movement was successful. When the mapper is properly configured an #OK trigger is automatically created that will confirm room movement.
Normally, when a direction is confirmed by #OK and the Mapper is being used, the next step will be sent to the MUD when the MUD Prompt is received. |
|
|
_________________
zMUD 7.05a |
 |
|
|
nexela
Wizard
Joined: 15 Jan 2002
Posts: 1644
Location: USA
|
|
|
|
|
|
|
|
|
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
|
|
