Page 1 of 1

EQBC and /pause or /delay on /multiline

Posted: Mon Apr 21, 2014 5:01 pm
by Alulien
I'm having issues with creating custom hotkeys sending commands via BC: I can't seem to get /multiline to recognize when I put in a /pause or /delay. I have tried /pause XX, /pause Xs, /delay XX, and /delay Xs to see if it was a syntax issue in the way the game was recognizing the timings.

Hotkey examples:

Line 1: /memspellset Buffs
Line 2: /pause 75
Line 3: /multiline ; /cast 1; /pause 40; /cast 2; /pause 30; /cast 3

The spellset mems, the /pause 75 is followed, but on line 3 none of the /pauses are followed as the character attempts to cast all 3 spells at once.

Line 1: /memspellset Buffs
Line 2: /multiline ; /pause 75; /cast 1; /pause 40; /cast 2; /pause 30; /cast 3

Same as first ex: the spellset mems, the /pause 75 is followed, but on line 3 none of the /pauses are followed as the character attempts to cast all 3 spells at once.

Line 1: /multiline ; /memspellset Buffs; /pause 75
Line 2: /multiline ; /cast 1; /pause 40; /cast 2; /pause 30; /cast 3

This will result in memming the spellset only. No messages are given indicating that spells were attempted to be cast. It does not appear that the /pause is recognized, as if I replace Line 2 with a /itemnotify 11 rightmouseup it will clear spells, open spellbook, but then stand up to cast the clicky.

Re: EQBC and /pause or /delay on /multiline

Posted: Mon Apr 21, 2014 6:05 pm
by Dreos
Someone else can probably provide more info on how /timed works, but I do know from:

http://www.macroquest2.com/wiki/index.php/Multiline

That /delay etc works unreliably (or doesn't work at all) with multiline. From what I understand (I haven't used it much) /timed executes the command following it after the time is up.

http://www.macroquest2.com/wiki/index.php/Timed

Hope that helps, but I'm sure someone else can be more informative!

Re: EQBC and /pause or /delay on /multiline

Posted: Mon Apr 21, 2014 7:03 pm
by Noren
Dreos is correct. /timed is the tool to use for this particular job. While multiline does execute in order from left to right, it is safest to treat them as all executing at roughly the same time and thus to set all of your times relative to the start of the hot key.
Ex:
/multiline ; /memspellset Buffs;/timed 75 /cast 1; /timed 115 /cast 2; /timed 145 /cast 3

Now, I'd advise you to remember how perfect the timing must be. If you only allow 75 decaseconds, you better be sure it won't take any longer than that, otherwise your next command will probably fail.

Good luck!

Re: EQBC and /pause or /delay on /multiline

Posted: Mon Apr 21, 2014 8:45 pm
by Alulien
Thanks guys! I tried some Googling but couldn't locate the /timed command. The heads up on timing relative to start of hotkey vs. between commands is much appreciated!

Re: EQBC and /pause or /delay on /multiline

Posted: Tue Apr 22, 2014 7:20 am
by Alulien
/timed works perfectly - thanks guys!

I've now run into an issue with /keypress and /itemnotify:

Character 1 hotkey
L1: /bct Character2 //keypress 0

Character 2 hotkey "0"
L1: /itemnotify 4 rightmouseup
L2: /timed 5 /itemnotify 29 rightmouseup

Although the BC window shows the command being sent/received, Character 2 never does the keypress. Of course, pressing 0 while on Character 2 works just fine. Character 2 happens to be my Bard, and the keypress to activate /melody works just fine when sent from Character 1.

Re: EQBC and /pause or /delay on /multiline

Posted: Sun Apr 27, 2014 6:52 pm
by Grey
http://www.macroquest2.com/wiki/index.php/Main_Page

Lots of stuff in there but it can be hard to find. Lack of proper page tagging etc.
Otherwise reading this board or Titans will net you a lot of useful information.

Re: EQBC and /pause or /delay on /multiline

Posted: Sun Apr 27, 2014 8:19 pm
by Noren
Alulien wrote:I've now run into an issue with /keypress and /itemnotify:


Try putting your /keypress value in quotes. Ex: /bct PLAYERNAME //keypress "0"

I suspect it is being treated as a non-integer non-string value; perhaps NULL. Putting it in quotes will force it to be treated as a string, and thus the keypress will evaluate correctly (fingers crossed).