 |
drayde
Newbie
Joined: 25 Feb 2006
Posts: 3
|
 Posted: Sat Feb 25, 2006 9:07 am
alias which worked perfectly before now kaput
|
Ok, I have no idea what changed in it, but I had an alias which would start a command sequence. all it did was perform one act, wait until I can perform the next, then do the next on the list. basically in was several commands all with #wait inbetween each. Worked for a few months, but now, for some reason, it will only perform the first command on the list and fail to deliver the rest. I don't know why, and I recieved no error message. Anyone have something similar happen?
|
|
|
|
|
drayde
Newbie
Joined: 25 Feb 2006
Posts: 3
|
Posted: Sat Feb 25, 2006 9:28 am
|
checked in there and it seems alot of aliases which use #wait suddenly aren't working. Is there perhaps something I might have switched which killed #wait? 
|
|
|
|
|
drayde
Newbie
Joined: 25 Feb 2006
Posts: 3
|
Posted: Sat Feb 25, 2006 9:46 am
|
ok, I'll see if I can the alias itself, just to see if anyone can see an obvious error (though since it worked all this time before, I don't see why there would be one)
this is one to tether steeds
tethsteed
tether @steed
#wa 1000
tether @eagle1
#wa 1000
tether @eagle2
#wa 1000
tether @eagle3
#wa 1000
tether @eagle4 |
|
|
|
|
mr_kent
Enchanter
Joined: 10 Oct 2000
Posts: 698
|
Posted: Sun Feb 26, 2006 6:17 am
|
What does the tethsteed alias do?
|
|
|
|
|
MattLofton
GURU
Joined: 23 Dec 2000
Posts: 4834
Location: USA
|
Posted: Sun Feb 26, 2006 6:26 am
|
There's no command or preference setting which affects #WAIT in an alias. Do you use #WAIT in triggers as well? If so, one of them is probably firing when the tethsteed alias gets called. The #WAIT in the trigger is what stops the alias, as #WAIT in triggers stops everything from processing (a more appropriate name would be #LAG).
|
|
_________________
EDIT: I didn't like my old signature |
 |
|
|
|
|
|
