 |
emnaki
Wanderer
Joined: 12 May 2007
Posts: 59
|
 Posted: Mon Sep 10, 2007 11:58 am
SLOW walking strange behaviour
|
Whats happening for me with slow walk is that when I try to walk to a room with #WALK 150 say and I interupt the walk half way causing the the walk to be aborted with the message "Slow walking aborted". I then am unable to process any more directions, I mean by this that I enter the direction and press enter but the direction is not being send to the mud. Has anyone else experienced this?
|
|
|
|
|
Fang Xianfu
GURU
Joined: 26 Jan 2004
Posts: 5155
Location: United Kingdom
|
Posted: Mon Sep 10, 2007 12:11 pm
|
How are you interrupting the walk?
|
|
|
|
|
emnaki
Wanderer
Joined: 12 May 2007
Posts: 59
|
Posted: Mon Sep 10, 2007 12:37 pm
|
By doing a command during the walk which causes lag just enough for slow walk to timeout. what happens next is wierd. One second only like north and east will work and a few seconds later, only north will work.
|
|
|
|
|
gamma_ray
Magician
Joined: 17 Apr 2005
Posts: 496
|
Posted: Mon Sep 10, 2007 2:09 pm
|
Have you tried using #nodir repeatedly to clear the queue from the slowwalk? (Remember the next direction in the queue is displayed in the status bar in the lower right of the mapper--keep using #nodir until it shows Queue: <empty>.)
|
|
|
|
|
Tech
GURU
Joined: 18 Oct 2000
Posts: 2733
Location: Atlanta, USA
|
Posted: Mon Sep 10, 2007 4:40 pm
|
Are you looking to see where you are on the map? It's possible that the the map has not kept up with you and thinks you are in a different location that only as a north or north and east exits only. Changing to "Safe Walk" would help
I would start by checking that. If you don't want the slow walking to be aborted then increase the time (to 250 for example).
If you want to quickly clear the queue '#QUEUE 0' will do the trick. |
|
_________________
Asati di tempari! |
 |
|
|
Seb
Wizard
Joined: 14 Aug 2004
Posts: 1269
|
Posted: Mon Sep 10, 2007 6:29 pm Re: SLOW walking strange behaviour
|
| emnaki wrote: |
| Whats happening for me with slow walk is that when I try to walk to a room with #WALK 150 say and I interupt the walk half way causing the the walk to be aborted with the message "Slow walking aborted". I then am unable to process any more directions, I mean by this that I enter the direction and press enter but the direction is not being send to the mud. Has anyone else experienced this? |
I have experienced this in zMUD (it's almost certainly the same in CMUD), especially when spamming directions manually. I think it is caused by the mapper having lost track of where I am and then me having already given it several new directions since then. At this point, it seems to be telling me "Enough! I can't take any more! Tell me where you are first!". My solution for this to turn off the mapper. If I have time, I will then press the Find button to locate where I am. If that fails, I will keep the mapper off until I am in a known place.
So, then it comes down to why has the mapper lost track of where you are? Unfortunately, this is a bit harder to diagnose. Sample MUD output would help. |
|
|
|
|
|
|
|
