Zugg Software :: View topic

Newbie Joined: 05 Oct 2005 Posts: 8

How can I go back step by step in a current path !

SubAdmin Joined: 18 Nov 2001 Posts: 5182

#BACKUP

Newbie Joined: 05 Oct 2005 Posts: 8

#backup dosen't work

#sl .nsew
n,s,e,w

#4 #backup
e,e,e,e

why??

SubAdmin Joined: 18 Nov 2001 Posts: 5182

Because the reverse to the 'w' is 'e'. Until that movement is confirmed #BACKUP will continue to think that reverse has yet to happen. You want #RETRACE to go bak the entire path, or you should build a series of triggers that preform #BACKUP at the appropiate times for a count of times you want.

GURU Joined: 23 Dec 2000 Posts: 4834 Location: USA

The easiest method is probably going to be %pathreverse() on the saved path. A similar concept can be employed on the mapper by using %pathfrom(), though you will have to have some way of calling up the room info (ie, vnum).

Newbie Joined: 24 Nov 2006 Posts: 3

TO Vijilante,

Could you explain how to build a series of triggers that preform #BACKUP at the appropiate times for a count of times you want???

SubAdmin Joined: 18 Nov 2001 Posts: 5182

Wow this is a really old thread, I can't really remember what I was thinking about a year ago. Creating a series of triggers to do that sort of thing is a very specific task, so I can't actually give a general answer. With a bunch of details about what you want to do and some information from the MUD I might be able to suggest the right way to go.

Newbie Joined: 24 Nov 2006 Posts: 3

assume that: there is a monster in the area, but i don't know the exact position. so i need to walk a path to find it. these all can be done by #sl .path and a trigger consisted of #stop and kill the monster.

i set walk speed 1 second, but if my network is blocked, i could not receive the echo message in time. several seconds later, messages not received comes to the screen all of a lump, the triggers may be inspired by some words thereinto, of course, in most cases, the monster is not in the current place but previous, so i need to go back step by step.

how can i carry it out using #backup?

thanks.

SubAdmin Joined: 18 Nov 2001 Posts: 5182

For bot type situations I really reccommend writing your own walker. Using #SLOW is often an interface nightmare compared to your own walker. The basic items needed for the walker is a trigger that detects completion of a step and a counter to use as an index into the path.

In order to handle botting as part of the walker you then need a control variable to determine whether to move on or not. This will often involve some more triggers and a little bit of parsing make the decisions. A properly written bot should never actually need to back up.

Newbie Joined: 24 Nov 2006 Posts: 3

that sounds working.

i have been working with zmud 4.62 before, and #slow works convenient and efficient.

it seems that i should come to adopt a new way now.

anyway, thanks a lot.