 |
Ashur
Novice
Joined: 25 Jul 2011
Posts: 39
|
 Posted: Thu Sep 15, 2011 2:49 pm
Mapper acting up
|
Yesterday I was running around trying to map an area and I ran into an interesting situation.
Assume the following room structure:
| Code: |
C
|
A - B - D - F
|
E
|
If I was in room B, and moved to room D, the mapper would draw room B where D should be. Then, if I moved to F (from D), it would render D. It seemed like the mapper was always 1 room behind and I couldn't make it catch up. Anyone know what's up with this? |
|
|
|
|
mikeC130
Apprentice
Joined: 03 Jul 2006
Posts: 110
|
Posted: Thu Sep 15, 2011 4:43 pm
|
If you had a failed movement command (tried to walk through a wall, etc.), that you haven't trapped via trigger and killed via #NODIR, then the mapper will have an extra movement command queued up and will exhibit this type of behavior.
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
|
|
