Zugg Software :: View topic - paths do not seem to work the same in v7.01

Beginner Joined: 23 Dec 2003 Posts: 19 Location: USA

I just upgraded to v 7.01, and my paths are not working

In many of my paths, I have extra commands, including even wait statements. These I have added as I debug and fix my paths over time in different circumstances.

Now once I hit a #WA statement in a path, it seems to just bail and think it is done.

Beginner Joined: 23 Dec 2003 Posts: 19 Location: USA

I upgraded from 6.6.7, btw, in case this is important in figuring out when the problem started in code

Posted: Wed Feb 18, 2004 7:33 pm

You need to post the EXACT path command that is causing a problem. Using the #WAIT command in general is a bad idea and you should read the article in the Support Library on the "Alarms, Delays, and the #WAIT command" to understand the bad side effects that #WAIT can have.

You also need to tell us whether you are using these paths with the mapper on or off.

Beginner Joined: 23 Dec 2003 Posts: 19 Location: USA

Exact path command:
6e3j2l3j`.(#WA 2000)`.e4j3n2h`.(enter mine)

The mapper is off/closed.

Beginner Joined: 23 Dec 2003 Posts: 19 Location: USA

it isn't just about wait commands.
nw`.(2 s)`.(5 w)`.(2 s)`.(2 sw)`.(psionicist)
this just went n, w, s, s and stopped

Beginner Joined: 23 Dec 2003 Posts: 19 Location: USA

maybe this is a larger problem here.
I did:
#mark
(the whole sequence above, step by step, including "psionicist"
#path newpsi

I get this message: .nw assigned to newpsi

that's only the first 2 moves!

Beginner Joined: 23 Dec 2003 Posts: 19 Location: USA

I realize one more clarification might help - I use the backtick, "`", as a separator character

Beginner Joined: 23 Dec 2003 Posts: 19 Location: USA

I have gone so far as to
1) move my zmud directory
2) reinstall zmud
3) connect again
4) #path
5) type in a somewhat complex path (like:
n
w
2 s
5 w
2 s
2 sw
psionicist
6) #path homepsi
I get:
.nw assigned to homepsi

that is not what it used to do - it seems very broken indeed. I can't use paths anymore?

Beginner Joined: 23 Dec 2003 Posts: 19 Location: USA

in the last example, I did #mark to start the path, not #path...

when I do individual directional commands: n w s s w w w w w s s sw sw
that still works
however, 1) my old paths are all broken 2) without bits like added special directional commands and so forth (like "enter hole", for example) paths are severely hobbled for me...

Beginner Joined: 23 Dec 2003 Posts: 19 Location: USA

I went ahead and filed a bug since no one else has said anything.
However, if you read this, I am interested to know if others are having the same problem!

Posted: Fri Feb 20, 2004 1:09 am

First, I assume when you say:
2 s
you really mean that you typed:
.2s
You should really be more specific about *exactly* what you are typing. It matters a lot.

In any case, I found a bug where using the . while recording a path (using #mark) resets the path and seems to be causing part of this problem. I've added it to the bug list.

But I still cannot reproduce your problem with #WAIT. I just typed:

.6e3j2l3j;.(#WA 2000);.e4j3n2h;.(enter mine)

into my command line here (using the normal ; instead of `) and it worked fine. It sent the first part, waited for 2 seconds, then sent the rest without any problem.

Beginner Joined: 23 Dec 2003 Posts: 19 Location: USA

in my mud (AoD), i type "2 s" meaning the MUD interprets 2 space s as "move two south". The interface used to take that and put it in parenthesis, like this, (2 s)
or `.(2 s).

My old paths almost all have constructs such at this, created just by using the #mark and #path commands
I added the #WA commands later, as an alternative to slow stepping. If I had to work around that, I would/will. But the mud can take (15 s) and go 15 moves south smoothly. However 15s is s s s s s (and so on) and the mud chokes quick moves...

Am I being unclear. No, I didn't type .2s, I typed 2 s with a space.

I'm sorry if I sound unlike I feel - I am simply trying to be clear, and appreciate your examination of the issue.

Beginner Joined: 23 Dec 2003 Posts: 19 Location: USA

To make it one step clearer: At no time did I type a period "." during the path that I marked. my typing a period cannot have had anything to do with the behavior

Beginner Joined: 23 Dec 2003 Posts: 19 Location: USA

OK, so, if I delete the periods from my existing paths, they work. Cool. Workaround. Yeah.

However, if I use commands that are not known to zmud to be directions, like "2 s" or "enter hole", then the path is truncated.

I have a slightly educated guess that the path thingy puts the period in (like it used to) but then truncates at that point. Maybe it should stop puting the period in, if that is indeed what it is doing.

I never knew why it put the period in in the first place.

Posted: Fri Feb 20, 2004 4:48 am

No, the fact that zMUD was recording non-direction commands like "enter hole" or "2 s" in previous versions was a bug. The #MARK/#PATH and the Record Path commands are only supposed to record speedwalking characters. If you want to record all commands, use the Record Alias menu command.

However, these commands are not supposed to truncate the path...*that* is the bug.

So, if you do
#mark
n
n
enter hole
s
s
#path test

it is supposed to record .2n2s into the path. It will *not* put (enter hole) into the path. That was a bug and was messing up a lot of people who were killing monsters while recording and getting the "kill" commands added to their paths.

If you want to use zMUD paths, you should use the zMUD speedwalking syntax .2s to move to spaces south instead of sending the "2 s" command to the MUD. If you ever start using the mapper, the "2 s" commands will make a mess of your map. .2s has the same effect but allows zMUD to move twice and record two movements instead of thinking "2 s" is a single step when it's really not.

The period is zMUD "speedwalking" character. It tells zMUD to interpret everything following the dot as speedwalking shortcut characters. So, for example, doing .news will send
n
e
w
s
to the MUD.

Beginner Joined: 23 Dec 2003 Posts: 19 Location: USA

OK, well that explains a lot, then.
Thank you for helping me get to the bottom of this. Perhaps it will help some other folks as well.