fiendish / aardwolfclientpackage

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

Custom exits should have weights (path costs) #182

Closed fiendish closed 10 years ago

fiendish commented 10 years ago

From aard...@gmail.com on May 07, 2012 02:52:03

Your username on Aardwolf so I can contact you if more information is necessary? Cizra What operating system are you using? Linux of Some Sort 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. r1580 snapshot Now explain your request. Every custom exit should have its weight or path-finding cost, defaulting to 1 (maybe 2? doors are gotta be more common than regular custom exits).

This would make very long custom exits more comfortable: for example, in Knossos, it takes a couple of steps to go down the stairs, or just one custom exit to use the portal and buy all the silver and whatnot.

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

fiendish commented 10 years ago

From Fiendi...@gmail.com on May 11, 2012 19:22:05

I don't understand what the problem is.

fiendish commented 10 years ago

From aard...@gmail.com on May 23, 2012 12:14:46

The problem is that some exits are preferred over others even if they're suboptimal. There are two examples:

fiendish commented 10 years ago

From Fiendi...@gmail.com on May 26, 2012 14:45:12

In the first case you can probably trick the mapper to walk by making a cexit where the length of the exit commandis longer than that of your portal command because it prioritizes longer exit commands when choosing how to get between rooms. That's how it always uses cexits to open doors.

In the second case it sounds to me like you should be using "mapper walkto".