After re-reading a section of this post it has occured to me that I in fact read it wrong. (Don't read/post when tired lol)





Since I do not have the recall orb I had not added it to my GoArrow. After Adding it I found that it was not always

the first" location to pop up. By clicking on next longer a few times I did indeed find it to work.


Example:


Atlas>Route From "Here" To Qalaba'r (Here is my house in Northfire Estates in this case)


First starting location: Abandoned Mines (2.16km)

Next: Glendon Wood (2.37km)

Next: Facility Hub (3.40km)

Next: Secondary Portal Tie (3.91km)

Next: Whispering Blade Chapterhouse (4.33km)

Next: Lifestone Bind (5.57km)


So GoArrow tries to find the absolute closest "distance" to the target, and all the Recalls come first in settings, so it goes through them first which is why Whispering Blade is not the "first" location picked.

 

-----signature-----

I just looked at Darktorizo's data_cod.xml, and it looks like the "Whispering Blade Chapterhouse to ________" portals don't have exit coordinates listed (arrival_latitude and arrival_longitude are 0), which means that GoArrow can't use them for route-finding. The database needs to be updated with exit coords for you to be able to use them in route finding. If you want, you can manually add the exit coordinates by modifying the portals on the Atlas > Details > Modify/Add Location tab, but it'd probably be best to have Darktorizo update his data_cod.xml with the coordinates, so everyone can take advantage of it.




I'm not sure what you mean here? GoArrow finds the shortest route based on the combined straight-line distance between portals along the route (in other words, the distance you have to run). The order of the start locations in the settings list has nothing to do with which one it picks.

 

-----signature-----

Learned something new about the program. =)


Not the order per se, but can you just add a new start location anywhere below <startLocations> in the settings file? Or does it matter?


I will update the end locations on the chapterhouse portals, as apparently they got overlooked =/. But on mine even with the end locations not added it will still route via the chapterhouse properly.


Thanl you for making me aware of them being 0.0 though. =)

 

-----signature-----

You can add start locations as any child node of the <startLocations> node. The order doesn't matter -- the plugin sorts them by name when it loads them.

The route that it found from the chapterhouse recall before you fixed the portals most likely involved recalling to the chapterhouse, then running to a nearby portal that's not in the chapterhouse, and going from there. That's *a* route, but not the shortest one.

The "Next Longer" button cycles through the start locations in order of the length of the shortest route between that start location and the destination. It'll eventually use up all the start locations unless there is no possible route under ~50km run-distance between a given start location and your destination -- the most likely reason for which is if the destination is on an island, since you can't run through the ocean.

 

-----signature-----