Zugg Software :: View topic

Beginner Joined: 07 Jan 2009 Posts: 14

I believe I found a bug with #RETRACE. If you #RETRACE a stored #PATH that has commands in it, like (say friend), it stops. I tested this a couple times with the same results each time, the retrace would stop when it hit the (say friend) or (open gate) command.

Is this an actual bug or am I doing something wrong?

--Robert

Posted: Sat Feb 07, 2009 1:06 am

That's correct. When you add custom commands to a path, there is no way for CMUD to know how to "reverse" the command. For example, consider the path:

Beginner Joined: 07 Jan 2009 Posts: 14

Too bad there wasn't a way to mark a custom command as optional? For example, some of my scripts have things exactly like (open gate) in them to be safe, but I'd like to be able to retrace and just skip that command. Just stinks not being able to get back from a long, long path because of a custom command near the very end of it! :) I suppose it would be possible to script something to take the path, remove the custom commands and pass it to #RETRACE... now if I can remember how to go about something like that...

Posted: Sat Feb 07, 2009 7:13 am

If you just use doors in the mapper itself and set the correct open and lock/unlock commands, then you can just use the #WALK command to walk wherever you want (or double-click the map) and CMUD will insert all of the needed "open" commands automatically. That's really the best way to solve the problem. Using #RETRACE just isn't going to work with custom commands.

Beginner Joined: 07 Jan 2009 Posts: 14

Unfortunately I have not been able to get the mapper working at all in CMUD. I also am not up to trying to map everywhere I go as it gets pretty complex fast, heh. I just wanted some quick shortcuts to get to/from some common places.

Thanks for your help!