Zugg Software :: View topic

Posted: Tue Apr 06, 2004 3:29 pm

Slow-walking
I have the mapper set to slowwalk. Unfortunately slowwalking is a fraction of a second too quick for ironrealms muds. Every so often.. usually 3-4 rooms, it is too quick and I get a "You cannot move that fast, slow down!" message.

Problem is, this stops the slowwalk here. I've tried all manner of combination of #OK, STEP, #NODIR etc, but I cannot get it to register that the movement failed, and to retry from where it failed.

Does anyone know how I can solve this?

Wizard Joined: 15 Jan 2002 Posts: 1644 Location: USA

First you can open your mapper config settings and somewhere there is a option for Send Delay set it a little higher (its milliseconds I think) so 500=half second

Secondly read this (pertains(<-is that the word I want) to 7.05) http://www.zuggsoft.com/library/speedwalking.htm

And it should give you some ideas on what to do if you get that message

Apprentice Joined: 13 Feb 2004 Posts: 157 Location: USA

In addition to that, you might need a trigger like this:

#tr {^You cannot move that fast, slow down!$} {#gag;#nodir;#stop;#wait 700;#step}

(People will tell you not to use #wait, but this is the only way I can get it to work in Aetolia.)

Wizard Joined: 25 Mar 2003 Posts: 1113 Location: USA

Theradil, the alternative to wait is to use a separate trigger state. Your trigger could be modified as such:

#TRIGGER {^You cannot move that fast, slow down!$} {#gag;#nodir;#stop}
#COND {} {#step} {wait|param=700}

Posted: Wed Apr 07, 2004 12:44 pm

Thanks for all the replies. I found the sendline thingy, and its works quite well. I still wish to get Theragil's suggestion working, for the odd occasion when it still goes too quickly. Unfortunately, perhaps due to differing mapper configurations, or even due to slight differences between Imperian and Aetolia, it doesn't work.

I also question the accuracy of the speedwalking document. Was it ever updated? As it explains things, #STOP;#STEP should stop the slowalk, then resend the direction that failed. It does not.. it sends the next direction in the queue as though the #STOP command confirmed the failed direction as being successful.

Anyway, when I use #NODIR;#STOP;#STEP, is resends the next direction fine, but does not recognise the move as successful, and the slowwalk times out. Here is an example:

quote:
You see exits leading north and south.
H:223 M:194 E:1017 <eb db> s

You cannot move that fast, slow down!
Slow walking aborted
s
H:223 M:194 E:1017 <eb db>
Beginnings of the Temple gardens.
Large piles of rock and sand mark this busy building site. In the corner some
...etc etc etc...
You see exits leading north and south.
H:223 M:194 E:1017 <eb db> Slow walking aborted

The red lines result from the #STOP;#STEP commands.

Wizard Joined: 25 Mar 2003 Posts: 1113 Location: USA

I think that perhaps you want to use #PAUSE instead of #STOP. I use it, for example, when I go through a wormhole exit and need to recover equilibrium before moving on. When you're ready to move on (after a short delay or based on some pattern), just send the #STEP command.

Try adapting the trigger I posted, but replace the #STOP with the #PAUSE.