Page 1 of 1
Pause in key binds
Posted: Mon Mar 29, 2004 3:48 pm
by Digitalxero
I tied making a social
Social::Pause wrote:
line1: /pause 120
line2: /3 testing123
then I tried
/multiline ; /dosocial "Pause";/3 testing456
I get can not parse /pause 120 but if I click the social normaly it works
Posted: Mon Mar 29, 2004 4:16 pm
by Lax
Ahh i know why, forget i said you could do that. You would have to hit the hotkey

Posted: Mon Mar 29, 2004 9:20 pm
by ionsf
So there is no way to use /pause or /delay in side of a bind command?
Would there be any harm in doing
as many times as needed to delay the next operation?
edit: Found this to not be much of a slow down... Apparently macroquest is fast lol.. I did a quick bind of
Code: Select all
down=/multiline ; /echo Start ; /squelch /skills x10; /echo Stop
*note cleaned up the post 10 /squelch /skills made it scroll way to the right.
the start/stop is pretty much instantaneous. Back to the drawing board.
Posted: Tue Mar 30, 2004 4:40 pm
by Digitalxero
Edited since I know about the /timed thing now
Posted: Tue Mar 30, 2004 4:53 pm
by Lax
no dont do that, use the new /timed
Posted: Tue Mar 30, 2004 7:37 pm
by Digitalxero
Thanks Lax, didnt see the /timed command untill today, thats what I get for not fully reading the change log, just a note though /timed will not work with variabled
ie /timed @castdelay does not use the value for @castdelay UNLESS you use /docommand /timed @castdelay /<some command>
Code: Select all
/declare nextcleric global
/declare castdelay global
/custombind add cch
/custombind set cch /multiline ; /cast "complete healing";/3 *** %t is getting Healed *** [@nextcleric get ready] (@castdelay);/docommand /timed @castdelay /3 *** @nextcleric GO NOW ***;/docommand /timed @castdelay /3 *** @nextcleric GO NOW ***
/bind cch p
Posted: Tue Mar 30, 2004 7:45 pm
by Lax
Hmmm... Yeah.. see, the problem is if the variables are parsed immediately there and in the command, someone is bound to say they wanted the new value of the variable.. and if the variables are parsed later when the command is executed, someone is bound to say they wanted the old value

I'll see what I can do, might involve 2 separate /timed commands.
Posted: Tue Mar 30, 2004 9:40 pm
by ionsf
Oo oo I'm going to have to play with /timed. I totally missed it in the docs.