 |
ArjenJ
Wanderer
Joined: 30 Jan 2006
Posts: 66
|
|
|
|
|
Tech
GURU
Joined: 18 Oct 2000
Posts: 2733
Location: Atlanta, USA
|
 Posted: Sun Mar 15, 2009 9:40 pm
|
Confirmed that it's setting the Mapper to mapping mode.
As for not setting the right spot, is it setting any location at all. Note that #find set's the current location to be the first room it finds that matches based on roomname / description (depending on your mapper configuration). |
|
_________________
Asati di tempari! |
 |
|
|
Zugg
MASTER
Joined: 25 Sep 2000
Posts: 23379
Location: Colorado, USA
|
Posted: Mon Mar 16, 2009 5:49 pm
|
Added to bug list.
|
|
|
|
|
mshirey
Newbie
Joined: 17 Mar 2009
Posts: 1
|
Posted: Tue Mar 17, 2009 2:17 am
|
I cannot confirm this. I use #find regularly using 3.05 and it works as desired and never sets the mapper to mapping mode.
|
|
|
|
|
hk2717
Newbie
Joined: 28 Mar 2009
Posts: 1
|
Posted: Sat Mar 28, 2009 5:33 am
|
The #FIND command does not work when the map is loaded but the map window isn't open. I think it should work in such circumstances?
|
|
|
|
|
Zugg
MASTER
Joined: 25 Sep 2000
Posts: 23379
Location: Colorado, USA
|
Posted: Fri Apr 17, 2009 8:34 pm
|
I have fixed #FIND in 3.06 so it should work when the map window isn't open.
Regarding it setting map mode, yes it does, but only temporarily. It needs to enable the map configuration parser to parse the incoming data from the MUD and determine the name and description to find. If your mapper isn't configured properly (or if you are offline), then #find never completes, and never switches the mode back to normal tracking. However, when online and when #find successfully sees a room name/desc/exit block, then it will switch back to tracking mode normally. So this isn't a bug. |
|
|
|
|
|
|
|
