Zugg Software :: View topic

Novice Joined: 27 Jul 2002 Posts: 38 Location: USA

I want to do a slow walk, but I also need to do other actions along the way (mainly to open doors, but sometimes other things).

What I want to do is:
#slow 2nwswsn;open door;#slow wen2wswnw2e;open strips;#SLOW nwudes3en2w2nesu;open door;
#slow ewdnesn2wn;open stone;#slow d2e2wu2wsds2wnesenueseses2e2s

With a test of: #slow 2nwswsn;open door
It sends a 'n', and then immediatly sends a 'open door', the rest of the slow walk then goes fine, but the open door is left in the first room, not at the end where I need it. Is there a way to put other commands in the middle of a slowwalk. I've heard about assigning other letters to different commands, but I don't think that will work, I've got a lot of other commands that I need to do, and wouldn't want them working like that all the time.

Thanks

SubAdmin Joined: 18 Nov 2001 Posts: 5182

Try this:
#slow {2nwswsn;open door;wen2wswnw2e;open strips;nwudes3en2w2nesu;open door;ewdnesn2wn;open stone;d2e2wu2wsds2wnesenueseses2e2s}

Novice Joined: 27 Jul 2002 Posts: 38 Location: USA

Took me a while to try this...

For a simple test I tried:
#slow {n;open door;w}
That has me step north, open the door and then abort the slowwalk

#slow {n~;open door~;w}
This has me step north, open the door and then abort

#slow {n~;open door;#OK;w}
Again, north, open and abort

Do I have to put an #OK trigger on everything I could do?

Also I want these in a room script, which seems to always turn ;'s into newlines, that doesn't seem to be a problem yet...

GURU Joined: 23 Dec 2000 Posts: 4834 Location: USA

quote:

Took me a while to try this...

For a simple test I tried:
#slow {n;open door;w}
That has me step north, open the door and then abort the slowwalk

#slow {n~;open door~;w}
This has me step north, open the door and then abort

#slow {n~;open door;#OK;w}
Again, north, open and abort

Do I have to put an #OK trigger on everything I could do?

Also I want these in a room script, which seems to always turn ;'s into newlines, that doesn't seem to be a problem yet...

You need only to create one trigger that matches a line in the room description (most often the exits line, but it can be anything unique to room descriptions but not to a particular room itself).

li'l shmoe of Dragon's Gate MUD

Novice Joined: 27 Jul 2002 Posts: 38 Location: USA

This doesn't seem to have any effect.
The problem is not that it's not finding the room I slow walk into, it's that it's aborting when I do other actions.

SubAdmin Joined: 18 Nov 2001 Posts: 5182

Go in the preferences. Under Slowwalking un check "Timeout aborts walk". Adjust the timeout to a lower number if you find the delay on other commands annoying.

If that is an unacceptable solution then rewrite the entire slow walk as a script...I did.

Novice Joined: 27 Jul 2002 Posts: 38 Location: USA

It's not a time problem.

It appears that zMUD wants the command "open door" to be #OK'ed. I put in triggers that send #OK whenever I open a door or whenever the door is already open and then it works. It would be nice if I could get all commands execpt directions to NOT require confirmation, but that's probably not possible.

When you rewrote it as a script, could you give me a short example of what you did? My first example is a very short snippet of what I need, and I need lots of them, probably several thousand moves in total, so setting triggers for every action is probably not a good idea, and would be a real pain to write it all...

Novice Joined: 14 Jul 2003 Posts: 31 Location: USA

What you do to add other commands in slowwalk is to do it like this
#slow {2nwswsn;.(open door)wen2wswnw2e;.(open strips)nwudes3en2w2nesu;.(open door)ewdnesn2wn;.(open stone)d2e2wu2wsds2wnesenueseses2e2s}