|
broadnax Beginner
Joined: 15 Oct 2000 Posts: 29 Location: USA
|
Posted: Thu Mar 04, 2004 7:38 am
#walk bug with 7.03 |
This problem is a bit intermittent, but it's happened a few times.
When I type #walk <roomname> 9 times out of 10, I go there correctly,
and the blue dot on the map is in the correct location. However,
occassionally when i use #walk, i will walk to the correct room, but
the blue dot showing my location will actually be a room or two off.
It's been hard to duplicate, I can go away from the room at varying
distances and it works fine, then suddenly it might miss once. |
|
|
|
nexela Wizard
Joined: 15 Jan 2002 Posts: 1644 Location: USA
|
Posted: Thu Mar 04, 2004 7:37 pm |
If you are using Safe mode speed walking chances are that one of the rooms you walked into isn't matching one of the lines in the mapper either first line of desc or room name depending on speedwalk prefs as this is a real pain if your mud has changing room descs/names and therefore isn't Generating a #ok Trigger. Go back to where the blue dot got stuck then step one room forward and see if the room matches whats stored in the properties for the room. If it doesn't match turn on map mode and do a #LOOK.
|
|
|
|
broadnax Beginner
Joined: 15 Oct 2000 Posts: 29 Location: USA
|
Posted: Wed Mar 10, 2004 1:14 am |
Nah i use fast mode, it didn't do it again for a week, and just did it. I can return to the start room and #walk again to the same destination and it doesnt do it. I still end up in the correct room with the blue dot off by a dot, but like I said, it doesnt happen very often, nothing I cant live with. Oh, and the blue dot actually overshoots... it goes one farther than the path I took usually, so the dot ends up in a room my path never took me on.
|
|
|
|
nexela Wizard
Joined: 15 Jan 2002 Posts: 1644 Location: USA
|
Posted: Wed Mar 10, 2004 10:38 pm |
*another waking up post*
Check for a #STEP or #OK Trigger firing off somewhere along your path |
|
|
|
|
|