fiendish / aardwolfclientpackage

Get the Aardwolf MUSHclient Package installer at
https://fiendish.github.io/aardwolfclientpackage/
Other
85 stars 33 forks source link

have the mapper use portals as priority over recall paths if the lengths are the same #168

Closed fiendish closed 10 years ago

fiendish commented 10 years ago

From javan...@netzero.com on November 15, 2011 16:07:55

BEFORE YOU FILL OUT AN ISSUE, DOWNLOAD THE LATEST DEVELOPMENT SNAPSHOT FROM THE DOWNLOADS TAB ABOVE. IS THERE STILL A PROBLEM? OK, PROCEED. DO NOT SKIP ANY QUESTIONS BELOW WHEN FILING BUG REPORTS! Your username on Aardwolf so I can contact you if more information is necessary? Jaxas What operating system are you using? Win 7 sp1 Open the file AardwolfPackageChanges.txt and find the topmost (highest number) snapshot 'r' number. It should be on the third line of the file and say something like " r386 snapshot". Paste that line here. If you don't have this file, you're using a ridiculously old version. Upgrade. r1431 snapshot Now explain your request. I setup two "portals" in the mapper, one uses a real portal, the other uses a "recall", both to the same destination room. I flagged the recall one in the mapper so it now shows up red. I then set one to bounceportal and the other to bouncerecall.

Now whenever the mapper calculates a path and wants to go through these portals, it always uses the recall one even if the portal one can be used. This is not ideal because the game recall command takes half my moves (over 10k for me) and 'word of recall' has a few second lag. Neither recall option is ideal and should only be used when absolutely necessary.

What I suggest is change the mapper so it only uses a recall flagged portal if it is the single shortest calculated path or you are in a bounce portal, recall friendly room.

Original issue: http://code.google.com/p/aardwolfclientpackage/issues/detail?id=168

fiendish commented 10 years ago

From Fiendi...@gmail.com on November 15, 2011 14:14:30

should be fixed in r1478

Status: Fixed