 |
chris-74269
Magician
Joined: 23 Nov 2004
Posts: 364
|
|
|
|
|
wrym
Magician
Joined: 06 Jul 2007
Posts: 349
Location: The big palace, My own lil world
|
 Posted: Thu May 14, 2009 2:17 pm
|
I routinely use #walk and #teleport, without problem.
Are these pre-define (named) speedwalks or nameless speedwalks in triggers and what not?
And are you precedign the speedwalks with a period? Periods mark items as a speed walk. otherwise they will be sent verbatim. |
|
_________________
"To the engineer, all matter in the universe can be placed into one of two categories: (1) things that need to be fixed, and (2) things that will need to be fixed after you've had a few minutes to play with them" - Scott Adams, The Dilbert Principle |
 |
|
|
chris-74269
Magician
Joined: 23 Nov 2004
Posts: 364
|
Posted: Fri May 15, 2009 7:48 pm
|
Yeah this particular setup has been working for me until I decided to give the beta a try. I need to parse down what's happening to a separate reproducible session, but it appears what it causing it is a speedwalk through a room with a room script like this: #if (%nextdir = "@d2diff") {#tele 29001}. Which means if my next direction on the queue I'll be set to room 29001, then the speedwalk will continue normally. I do this because there are plenty of difficulties I can choose for the same area, so I make the room exit a variable which I can change to the difficulty based on an alias I do to get in there. So after the #tele, the first direction of the speedwalk is sent then the directions are sent verbatim. After this if I try to speedwalk anywhere else, the first 2 directions get sent then "3e4n...." or whatever those dirs may be, even if I try .12n, it'll send 2 north then "10n"
|
|
|
|
|
|
|
|
