|
Vitae Enchanter
Joined: 17 Jun 2005 Posts: 673 Location: New York
|
Posted: Tue Aug 09, 2005 7:50 pm
#walk & #recall |
K, so, I'm sitting at recall (which is set as #recall).
I type #walk 12021 and i go es like i should.
Then i go somewhere else random spot which is recall-able.
Then i type #walk 12021 and i got thru a hell of a long walk to get there.
Since #walk uses the shortest path (as far as I know) then why does it not issue a recall and then go es?
How can i set this up?
Would i need to set up recall as a portal as well?
I have one portal set up as a test for something else and issuing the #walk to a room just beyond that will send the portal command.
I just naturally assumed recall worked the same way.
Thx |
|
|
|
Vijilante SubAdmin
Joined: 18 Nov 2001 Posts: 5182
|
Posted: Tue Aug 09, 2005 9:24 pm |
Issuing a 'recall' has never really been setup as part of walking. You will likely have to do your own script that test whether the 'recall' is shorter then #ALARM for the proper #WALK.
|
|
_________________ The only good questions are the ones we have never answered before.
Search the Forums |
|
|
|
Vitae Enchanter
Joined: 17 Jun 2005 Posts: 673 Location: New York
|
Posted: Wed Aug 10, 2005 1:13 am |
ummm...#alarm?...what's that got to do with it?
i'm talking path lenght.
recall es is WAY shorter than getting to the same room with ennnnneeeeeessssssssssswwwwwwww;enter trap;sssssssseeeeee etc... |
|
|
|
Vitae Enchanter
Joined: 17 Jun 2005 Posts: 673 Location: New York
|
Posted: Mon Aug 15, 2005 5:24 pm |
still hoping for an answer
|
|
|
|
MattLofton GURU
Joined: 23 Dec 2000 Posts: 4834 Location: USA
|
Posted: Mon Aug 15, 2005 8:26 pm |
Well, what you basically have to do is use %pathfrom() twice. The first %pathfrom() will be from the current room to the room you want to go to:
#var OptionA %pathfrom(,destination-vnum)
The second %pathfrom() will be from the recall room to the destination room:
#var OptionB %pathfrom(recall-vnum,destination-vnum)
At this point, you need to do a comparison. I do not know if or how speedwalk paths can be compared directly, so you will probably have to use %pathexpand() to convert the speedwalk paths into stringlists. Once this is done, it's a simple matter of comparing the %numitems() of each stringlist (for a true comparison, don't forget to add one to the OptionB value to account for the recall step). If OptionA is shorter, then you use that one; if OptionB is shorter, you use that one. |
|
_________________ EDIT: I didn't like my old signature |
|
|
|
Vijilante SubAdmin
Joined: 18 Nov 2001 Posts: 5182
|
Posted: Mon Aug 15, 2005 9:06 pm |
At this point is where the #ALARM will likely come in. When the recalled path is shorter you must issue a recall, then wait until it is confirmed to issue your #WALK. I didn't explain it all that clearly before becayuse I know you have been around a while, and thought you could figure it out.
|
|
_________________ The only good questions are the ones we have never answered before.
Search the Forums |
|
|
|
Vitae Enchanter
Joined: 17 Jun 2005 Posts: 673 Location: New York
|
Posted: Mon Aug 15, 2005 9:19 pm |
confirmed recall?
I use fastwalk.
i pretty much just need:
recall;.es
No alarm needed for me.
Besides, even tho i been around a while, you shoulda noticed i still ask the stupid questions. :-)
EDIT: Never mind. Decided to just set recall as a portal.
So far, seems to work fine. |
|
|
|
|
|