Mapper - handheld portals about aardwolfclientpackage HOT 6 CLOSED

From [email protected] on December 24, 2010 14:36:47

Ok - now I'm attaching the one that works. The match pattern in the mapper portal alias would not capture things like (114732), which is a valid portal keyword ;)

Attachment: aard_GMCP_mapper.xml

from aardwolfclientpackage.

From [email protected] on December 24, 2010 14:43:31

One more time - had made a change to my de-duping code and typo'ed a variable name...

Attachment: aard_GMCP_mapper.xml

from aardwolfclientpackage.

From [email protected] on December 26, 2010 21:16:29

Here's my idea on how to find a path... we start at the destination, and find the set of all exits to that room. The we find the set of all exits to the fromuids of those exits, and repeat until the returned set contains our starting room or * for a handheld portal. Then we work our way forward, using the newest exit from the current room to the next closest set to the destination... pseudo code attached.

Attachment: pathfinderPsuedoCode.txt

from aardwolfclientpackage.

From [email protected] on December 28, 2010 12:58:00

Another fix here for unmapped... This should be the last one...

It now formats correctly and it handles not knowing the current area correctly. Options:

mapper unmapped --> shows all unmapped exits in current area
--> if area unknown, summarize unmapped exits by area
mapper unmapped % --> summarize unmapped exits by area
mapper unmapped --> all unmapped exits in the named area - if it exists

typos are the user's worry... ;)

Attachment: aard_GMCP_mapper.xml

from aardwolfclientpackage.

From [email protected] on January 08, 2011 07:23:46

Let's declare this thread at an end... I'm going to start a new issue for pathfinder...

from aardwolfclientpackage.

From [email protected] on January 26, 2011 22:52:24

added in r292 and r294

Status: Fixed

from aardwolfclientpackage.