|
Thinjon100 Apprentice
Joined: 12 Jul 2004 Posts: 190 Location: Canada
|
Posted: Mon Aug 27, 2007 7:24 pm
[2.01] New %walk path syntax? |
I looked through the version history, but can't find anything referencing this.
In v1.34, if you used %walk(<vnum>) you received a path, somewhat like this: .un2esw;.(open north;n)u2w;
I had a function that parsed this out into appropriate movement commands... however it seems the new syntax comes out:
un2esw; (open n;n)u2w
The dots have been replaced with spaces (or at least they look like spaces... copying them into Editpad and trying to match with \s fails). This makes the path infinitely more difficult to parse out (I've spent an hour now on the regular-expression.info site learning about conditionals and lookarounds trying to make a %subregex that'll work with this). Is there a particular reason this was changed? I liked the old syntax... it made sense. Is this a bug, an intentional change, or is the new character there something I should be able to match with a different escape code? |
|
_________________ If you're ever around Aardwolf, I'm that invisible guy you can never see. Wizi ftw! :) |
|
|
|
Zugg MASTER
Joined: 25 Sep 2000 Posts: 23379 Location: Colorado, USA
|
Posted: Mon Aug 27, 2007 7:29 pm |
I cannot reproduce this one. Maybe you can send me your *.MDB map database as an email attachment and tell me where to set the starting location and exactly what %walk command to try.
Have you changed your Movement Character in your Special Character preferences? Nothing was changed on purpose in this version, and it still shows the dots when I try it on my own map here. |
|
|
|
Thinjon100 Apprentice
Joined: 12 Jul 2004 Posts: 190 Location: Canada
|
Posted: Mon Aug 27, 2007 7:32 pm |
Heh... ok, that's weird. I've been using that same replacement function for months now, and it's been working fine, and I haven't looked at the movement character entry in Prefs since before then. Looking now, I have the character disabled. Looks like this was a bug and oversight on my part in v1.3x. Have re-enabled the "." movement character in 2.01 and it looks to be working fine now.
Thanks for the help :) |
|
_________________ If you're ever around Aardwolf, I'm that invisible guy you can never see. Wizi ftw! :) |
|
|
|
Fang Xianfu GURU
Joined: 26 Jan 2004 Posts: 5155 Location: United Kingdom
|
Posted: Mon Aug 27, 2007 7:35 pm |
Does %pathexpand still work with this bugged format? You might find that makes your parsing problems easier.
EDIT: Belated, but possibly still relevant. |
|
|
|
Thinjon100 Apprentice
Joined: 12 Jul 2004 Posts: 190 Location: Canada
|
Posted: Mon Aug 27, 2007 7:35 pm |
On the plus side, I can now do some really cool things with regex conditionals and lookarounds I never knew before :P
|
|
_________________ If you're ever around Aardwolf, I'm that invisible guy you can never see. Wizi ftw! :) |
|
|
|
|
|