|
solem Beginner
Joined: 16 Mar 2004 Posts: 20
|
Posted: Tue Mar 16, 2004 8:24 pm
Weird Slowwalk problem |
I’m currently trying to use slowwalk with zmud 7.04 and am getting some weird behavior.
1. I start a slowwalk with #SL .3n3en4w2s
2. Slowwalk goes along just fine for a while.
3. Then something happens and I get the Slow Walk Aborted message. Which is fine.
4. So I start to finish my walk manually.
5. As soon as I enter the next room, zmud starts to spam directions to the mud. (i.e. nnnwn)
6. I enter another room same thing. It just keeps happening, different spam direction every time. I have to quit zmud and reconnect to the mud to fix it
One other thing I don’t have a Trigger for the #OK, zmud seems to be picking this up from Exits: string on it’s own.
Thank you for your help. |
|
|
|
Kjata GURU
Joined: 10 Oct 2000 Posts: 4379 Location: USA
|
Posted: Tue Mar 16, 2004 9:10 pm |
Look into Preferences and in Slow Walking define some text that would let zMUD know that a step in the slow walk was succesful.
zMUD is trying to find out if you really did move before sending the next direction. I don't get the spamming of directions once the slow walk has been aborted, but you should be able to keep it from happening with a #STOP command.
Also, even though you say you do not have an #OK trig, do check thouroughly your settings in case there is one hidden somewhere. However, by setting the slow walking strings correctly in the Preferences, it should work. |
|
|
|
solem Beginner
Joined: 16 Mar 2004 Posts: 20
|
Posted: Tue Mar 16, 2004 9:22 pm |
The speed walk does work... But if it fails for some reason... like, Someone shuts a door and I don't have the door marked on map... Then I get the abort message. I then type in a new direction like north. When I enter the new room, zmud enters a bunch of directions and I speedwalk off to somewhere random. If enter the #STOP command manually and then type in a new direction the same weirdness happens.
|
|
|
|
Kjata GURU
Joined: 10 Oct 2000 Posts: 4379 Location: USA
|
Posted: Tue Mar 16, 2004 9:42 pm |
Are you using the mapper for the slow walk?
|
|
|
|
solem Beginner
Joined: 16 Mar 2004 Posts: 20
|
Posted: Tue Mar 16, 2004 10:14 pm |
Sorry, Bad example of why if might fail. I do keep the mapper open while slowwalking and watch my progress on it.
But
I'm typing in the command #SL .4ne4sw
Lets say I walk the 4n just fine and when I turn east there is no east exit and the #SL fails -- Abort message. When I type south to go back down, I move one south then the weirdness. |
|
|
|
solem Beginner
Joined: 16 Mar 2004 Posts: 20
|
Posted: Wed Mar 17, 2004 2:31 am |
Here is an examle.
Alas, you cannot go that way.
<133/133/100% 100 133 |1937 1100xp 0tell 885| A busy tree | NSW 18tq |dbl
Slow walking aborted
You hear something's death cry.
south <<--- me entering s
A brown pebble path
w[xx(] <<--zmud putting in additional direction |
|
|
|
Pega Magician
Joined: 08 Jan 2001 Posts: 341 Location: Singapore
|
Posted: Wed Mar 17, 2004 2:36 am |
Does that mean that the room name is triggering it?
|
|
|
|
|
|