 |
TonDiening
GURU
Joined: 26 Jul 2001
Posts: 1958
Location: Canada
|
 Posted: Fri Mar 22, 2002 4:40 am
Problem with #ABORT
|
Try:
#ABORT 1
The abort command takes a flag which should kill the queued up commands..
TonDiening
Beta Upgrading to 6.26 |
|
|
|
|
iljhar
GURU
Joined: 10 Oct 2000
Posts: 1116
Location: USA
|
Posted: Sat Mar 23, 2002 10:25 pm
|
Try clearing the queue first, then using #abort 1:
#alias stop {#30 {nodir};#abort 1}
See if that does anything for ya.
Iljhar |
|
|
|
|
LightBulb
MASTER
Joined: 28 Nov 2000
Posts: 4817
Location: USA
|
Posted: Sun Mar 24, 2002 1:12 am
|
According to the helpfile on Speedwalking with the Map, "With Fast speedwalking selected, the movement commands to get to the destination room are sent all at once to the MUD." Since all the commands are immediately sent to the MUD, there's nothing to abort. #ABORT can only work when you have pending commands that have NOT been sent to the MUD.
LightBulb
All scripts untested unless otherwise noted |
|
|
|
|
LightBulb
MASTER
Joined: 28 Nov 2000
Posts: 4817
Location: USA
|
Posted: Mon Mar 25, 2002 4:43 am
|
That explains why you can use #ABORT from the command line. However, I would guess that the output from your triggers, including #ABORT, ends up in the same send-queue as the directions waiting until enough time has passed before it's sent.
At any rate, what you have isn't working. So, the solution should be obvious -- change to Safe- or Slow-walk mode.
LightBulb
All scripts untested unless otherwise noted |
|
|
|
|
|
|
|
