Button Mashing

[ICdeadppl]

Hi I have used Keyclone to lvl characters to 60, but was wondering if I have set it up correctly, casue I'm about to do it again.

I lvl'd a Mage and Shammy together, but had to mash the attack button (press once the main attacks, press again and second char attacks) to get it to send the keys to both windows. Is this how it's supposed to work, casue looks like from the guides that I should only have to press the Main's attack key once to get the second character to attack aslo. Can anyone shed some light on some settings I may have forgotten

[keyclone]

it would depend on your setup... assuming your macros are correct... it sounds like what you are experiencing is network lag

if you select a target and then click fire... but too quickly... your alts will not have received the new target information by the time they received the 'fire' command.

try clicking the target... waiting a split second (count to two)... then hitting fire and see if you still need to hit the fire button twice

let me know how it goes,

Rob

[Fizzler]

it would depend on your setup... assuming your macros are correct... it sounds like what you are experiencing is network lag

if you select a target and then click fire... but too quickly... your alts will not have received the new target information by the time they received the 'fire' command.

try clicking the target... waiting a split second (count to two)... then hitting fire and see if you still need to hit the fire button twice

let me know how it goes,

Rob

If the target was built into the first part of the macro I would imagine this would not be an issue?

[keyclone]

no, you still have the latency issue.

when you click on a new target, that information goes from wow1 up to the wow server... then down to you party members. this will take at least 2 * latency, or about 200ms on average... and remember, network latency is not fixed... it can fluctuate due to various network conditions

when you hit 'fire'.. it will go to your alts immediately, < 1ms (this won't fluctuate). if the information for your new target has not been received by your alts, then your alts would still be pointing at the old target... and would try to fire on that instead

[ChaoticMonk]

You dont have your 'mash' key set on round robin do you? ?(

[TheBigBB]

Listen to Mr. Keyclone. What he's saying is absolutely correct and probably is why you need to press the button 2 times sometimes.

[Rudi89]

Listen to Mr. Keyclone. What he's saying is absolutely correct and probably is why you need to press the button 2 times sometimes.

I have noticed this as well.

Mr. Keyclone: Is there any thought at allowing Keyclone to put in latency to the keystroke commands sent to the non-active WoW windows? I would be happy to put in a 300-500ms lag to commands to slaves if it means they always get the new target.

[Talos]

Listen to Mr. Keyclone. What he's saying is absolutely correct and probably is why you need to press the button 2 times sometimes.

I have noticed this as well.

Mr. Keyclone: Is there any thought at allowing Keyclone to put in latency to the keystroke commands sent to the non-active WoW windows? I would be happy to put in a 300-500ms lag to commands to slaves if it means they always get the new target.

Cant do that.. cause that would fall under automation..

and cause everyone using keyclone to risk getting banned
now we wouldnt want that would we

[keyclone]

Cant do that.. cause that would fall under automation..

exactly right.
think of it as keeping the 'battle clock' in your head from getting wound up. keep pace.. click... quick count 'one-two' in your head... then fire

this only matters for targeted spells.. non targeted spells have no lag issues

[Jheusse]

How hard would it be to add a visual latency indicator to keyclone? I'm thinking of the utility of Quartz as it applies to multiboxing.

Using quartz by itself does the job somewhat but hey can't hate me for feature requests