Zugg Software :: View topic

Newbie Joined: 12 Jun 2003 Posts: 3 Location: Australia

Hi.

I'm pretty much a noob to zMud so advanced apologies for any stupid questions.

2 questions :

1. Having gotten speedwalking to work in slow mode by setting the "Strings to determine successful slowwalk" to the beginning of my prompt (which is the last line in my mud), I was wondering if there's a better way to do it.
2. Secondly how do I chain commands serially? I have an alias called ww which consists of :
brief
#WALK %1
brief off
which does all the right things except it executes the "brief off" before the #WALK has finished. How do I make it wait for the #WALK?

Magician Joined: 23 Apr 2003 Posts: 358 Location: USA

Answer to question 1 depends on your MUD. If you use the automatical Reconfigure option in the Mapper, that's probably your best bet. That failing, you can read in the Help file under "Introduction to Mapping."

Question 2 is easier and harder at the same time. You can string commands together by setting a multistate trigger, which is detailed in the Help Library on this site.

In your specific case, you may want to simply use the special alias "onwalkend" which executes whenever a walk path is complete: #ALIAS {walk} {brief on;#WALK %1;#ALIAS onwalkend {brief off}}

Newbie Joined: 12 Jun 2003 Posts: 3 Location: Australia

Thanks for that, point 2 worked a treat.

As for point 1, what I'm really after is behaviour similar to that in v 6.53 of zMud, where even in FAST speedwalk mode I could hit the escape key and stop.

In essence I want SLOW to ignore mud output. Is there a way to achieve that?

Thanks again.

GURU Joined: 10 Oct 2000 Posts: 4379 Location: USA

If it ignores MUD output then it is not longer a slowwalk but a speedwalk.

Kjata

Newbie Joined: 12 Jun 2003 Posts: 3 Location: Australia

True enough, but as I said, the behaviour I'm tryng to emulate is that of v6.53 whereby even in fast walk, which ignores mud output, I could interrupt the travel. That is, it did NOT send all the commands to the mud, it sent them a few at the time (or so it appeared to be), thus enabling me to break the travel if need be.

GURU Joined: 10 Oct 2000 Posts: 4379 Location: USA

It would seem then that you can't. The behavior you describe was not supposed to happen as speedwalk is just supposed to send all of the commands at once.

You could probably use a slowwalk and have an alarm that sends #OK every second or maybe less. Then the commands would not be sent all at once, but since the alarm is sending the #OK's, it sends the directions at the pace dictated by the alarm. Disabling the alarm would then stop the walk.

Kjata