 |
emnaki
Wanderer
Joined: 12 May 2007
Posts: 59
|
 Posted: Mon Sep 03, 2007 3:30 am
Mapper #NODIR problem
|
There is a problem I'm currently experiencing with the mapper where #NODIR does not match up with the proper direction. Below is an example when the problem occurs:
| Code: |
<1021hp 809m 331mv .18hr>
n
n
n
A small forest trail
[Exits: north south]
<1021hp 809m 327mv .18hr>
n [color=red]<====Invalid Direction[/color]
n [color=red]<====Invalid Direction[/color]
w
A small forest trail
[Exits: north south]
<1021hp 809m 323mv .18hr>
The night has begun.
Timer now at 30 secs.
<1021hp 809m 348mv .19hr>
A small forest trail
[Exits: south west]
<1021hp 809m 344mv .19hr>
Alas, you cannot go that way. [color=red]<====Message triggering #NODIR[/color]
<1021hp 809m 344mv .19hr>
Alas, you cannot go that way. [color=red]<====Message triggering #NODIR[/color]
<1021hp 809m 344mv .19hr>
Before a clearing in the forest
[Exits: north east]
|
It seems What is happening is that #NODIR is being matched against the last two directions inputted before it (n,w), before the #NODIR command is inputed instead of the invalid directions (n,n). The result of this is that the mapper fails to update itself west. Does anyone have any clues as to how to solve this? |
|
|
|
|
mikeC130
Apprentice
Joined: 03 Jul 2006
Posts: 110
|
Posted: Mon Sep 03, 2007 7:02 pm
|
You seem to be entering directions too fast for the mapper to keep up. #NODIR removes the last direction from the queue, which means that if you put in more than one direction before getting a reply, the trigger will get the latest rather than first command entered. The best way to deal with this would be to slow down your direction entries and getting some type of reply before the next movement command, letting the mapper keep up.
Mike |
|
|
|
|
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
