Zugg Software :: View topic

Posted: Sat Sep 08, 2007 1:12 pm

I did no change to the map, it just stopped following.

I tried reconfiguring, and it moved for that one room, then stopped. Even in mapping mode.

Wizard Joined: 14 Aug 2004 Posts: 1269

Maybe you should provide some more details of how your mapper config works...

Do you MXP? XML? ANSI? ATCP? as part of how the mapper tracks your movements? Do you use the #TAG feature manually within triggers? When it stops following do you see a movement direction at the top of the mapper queue?

Posted: Sat Sep 08, 2007 3:25 pm

Eh.. this issue seems to have resolved itself.. odd, but fixed.

Posted: Sun Sep 09, 2007 6:10 am

And now it started to not follow again.
I'm not sure but this MAY be related to the unresponsive bug, as it didn't start acting up again till after i had to force it to close from unresponsiveness.
It went unresponsive when i attemted to use the 'who long' command in the mud, which now works fine, it got about 7 lines into the display before freezing.

As for how the mapper is set... all i did was let the auto configuration run and it goes off of that.
I use no special mapper commands or triggers for it.
Yes, the mapper queue shows the direction I am supposed to have moved in the lower right corner of the mapper window, which I have set up to display on my second monitor.

I just went ahead and added an #OK trigger to force it to follow for now.

Enchanter Joined: 11 Feb 2003 Posts: 511 Location: USA

What are you basing your speedwalk on, room description or room name? I would check that configuration setting to be sure it is the one you want. For example, the IRE MUDs run off the room name almost exclusively (and definitely with ATCP). I find that sometimes, especially after crashes, that this setting sometimes changes back to room description as what it is trying to match and therefore it never gets the internal #OK.

Enchanter Joined: 09 Sep 2007 Posts: 605

Try to switch mapper in Fast mode. For me it is the only mode where it somehow managed to handle room descriptions and exits information. In other modes I see that mapper understand directions and correctly display the room number it should move in but it fails...

Wizard Joined: 14 Aug 2004 Posts: 1269

Well Fast mode doesn't use #OK triggers. It is very crude and assumes you always move in the direction you entered. Making your own #OK trigger should at least be a bit more reliable.

Shalimar, do you have triggers and scripts that process the 'who long' command output?

Apprentice Joined: 13 Aug 2007 Posts: 166

Nothing will prolly be done about this now anyways since the mapper will be completely rewritten.

Wizard Joined: 14 Aug 2004 Posts: 1269

Well, I think it may still be useful to track down the bug, so at least we know what causes it and when or why.

Magician Joined: 17 Apr 2005 Posts: 496

Check your prompt, make sure it's matching that. Also make sure in the mapper config: Speedwalking > Automatic Step Confirmation > Match Room Name.

Posted: Mon Sep 10, 2007 9:43 pm

prompt matches fine, no triggers for it
no triggers for the 'who long' output
mapper config was set to match the first line of the room description

i am NOT using the mapper for speedwalks, so speedwalk settings should not matter

and now the issue has resolved itself again... this is annoyingly sporatic

Wizard Joined: 14 Aug 2004 Posts: 1269

Whether or not you use the mapper for speedwalks is irrelevant. Your speedwalk settings still DO matter. Read the "Speedwalking with the Map" helpfile and experiment.

Wizard Joined: 14 Aug 2004 Posts: 1269

For example, in Fast mode, all your #NODIR are ignored (because the movement is already assumed to have succeeded).