 |
Ryuichi
Beginner
Joined: 26 Oct 2004
Posts: 19
|
 Posted: Sun Jan 30, 2005 3:55 am
Path Recording configuration
|
When recording a path, sometimes you have to open doors/gates, and the path recorder doesn't pick up on this.
A path recorder configuration tab in preferences would be wonderful.
Also, when recording a path, I usually end up hitting at least one wrong direction, and then I have to use my mouse to get back to the recorder window to edit the text. Is there a function or command to get rid of the last direction? Also, is there a way to append text to the recorder? I could record a macro, but that's not quite what I'm looking for.. triggers could edit the line, but the utility is there, and it works well, but it can be better. |
|
|
|
|
Ryuichi
Beginner
Joined: 26 Oct 2004
Posts: 19
|
Posted: Sun Jan 30, 2005 4:34 am
|
Found the #backup command, so half the problem down.
|
|
|
|
|
MattLofton
GURU
Joined: 23 Dec 2000
Posts: 4834
Location: USA
|
Posted: Sun Jan 30, 2005 5:54 am
|
Check the Map Preferences. Under the Speedwalking category, there's a setting to "Add door commands to saved paths and %walk/%path functions". Dunno if it will work but you could try messing with it to see if the recorder behavior changes.
|
|
_________________
EDIT: I didn't like my old signature |
 |
|
|
Ryuichi
Beginner
Joined: 26 Oct 2004
Posts: 19
|
Posted: Sun Jan 30, 2005 10:34 pm
|
| MattLofton wrote: |
| Check the Map Preferences. Under the Speedwalking category, there's a setting to "Add door commands to saved paths and %walk/%path functions". Dunno if it will work but you could try messing with it to see if the recorder behavior changes. |
Didn't do anything for me. #path is supposed to do two things at once, save the current path to the variable named, and then assign the rest to the current path behind. I can't get it to properly assign a path.... at least containing "open gate" or the like. Any ideas? |
|
|
|
|
Ryuichi
Beginner
Joined: 26 Oct 2004
Posts: 19
|
Posted: Sun Jan 30, 2005 11:15 pm
|
okay, #step {open d} works, but it also sends the text to the mud. Fair enough :)
Hope it's of some use to somebody.
Okay, for making a path, say you're walking, and bump into a door
#trigger {the (%1) seems to be closed} {#nodir; #step {open %1}}
will open the door, and take the last direction off the path. voila. automated recording of paths :) |
|
|
|
|
Vorax
Apprentice
Joined: 29 Jun 2001
Posts: 198
Location: USA
|
Posted: Mon Jan 31, 2005 4:23 pm
|
You shouldn't use %1 in the trigger pattern. Instead, use one of the pre-defined wildcards for pattern matching.
#TRIGGER {the (%w) seems to be closed} {#NODIR;#STEP {open %1}}
#TRIGGER {the (*) seems to be closed} {#NODIR;#STEP {open %1}}
#TRIGGER {the (%x) seems to be closed} {#NODIR;#STEP {open %1}}
Any one of those should work. |
|
|
|
|
Ryuichi
Beginner
Joined: 26 Oct 2004
Posts: 19
|
Posted: Tue Feb 01, 2005 10:00 am
|
%1 is just a bit of an old school way of doing things in zmud. Before regex and stuff were put in :) It works fine.
|
|
|
|
|
Ryuichi
Beginner
Joined: 26 Oct 2004
Posts: 19
|
Posted: Tue Feb 01, 2005 10:10 am
|
Note that I wasn't trying to be rude.... when I'm trying to throw code together quickly, I just revert to using that. I know regex, but it takes me a while to make it fire properly.... so I don't use it too often.
|
|
|
|
|
|
|
|
