Help with Elem Shaman Macro

Hi there. I have an issue where the last line of the Elem Shaman macro is not firing in my macro. It never casts the Lightning Bolt part but everything else works fine. Am I missing something here? Thank for any help.

/run SetCVar("Sound_EnableSFX","0")

/use 10
/use 13
/cast Blood Fury
/cast elemental mastery

/click sdf__DPS1
/click sdf__DPS2
/click sdf__DPS3
/click sdf__DPS4

/run SetCVar("Sound_EnableSFX","1")
/script UIErrorsFrame:Clear()

The actual lines are

/castsequence reset=combat flame shock,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,, ,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
/castsequence reset=combat lava burst,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
/castsequence reset=combat chain lightning,,,,,,,,,,,,,,,,,,,,,,,,,
/cast lightning bolt

Put the lightning bolt line as the last line of your main macro instead of its own /click macro.

Quote:

---

Originally Posted by Maxion

Put the lightning bolt line as the last line of your main macro instead of its own /click macro.

---

Ah thank you for the help. So instead of /click sdf__DPS4 I would just do /cast lightning bolt?

Well just tried it on my lead shaman and it only sometimes fires off Lightning Bolt. Most cycles he just stands there till macro resets.

What impact would this change have in the macro? :)

Quote:

---

Originally Posted by Hellektro

Ah thank you for the help. So instead of /click sdf__DPS4 I would just do /cast lightning bolt?

Well just tried it on my lead shaman and it only sometimes fires off Lightning Bolt. Most cycles he just stands there till macro resets.

---

Make sure you have enough commas in your other ones that they do not get back to the spells until they are off cooldown/need recasting.

Quote:

---

Originally Posted by crowdx

What impact would this change have in the macro? :)

---

This lets it cast lightning bolt whenever the others are on commas. It is the most reliable way to do the fallthrough part of the macro, and I believe the /clicked macros can only do castsequences of normal spells rather than /cast. Thus putting it in the main macro.
Either way, having the fallthrough in the main macro is how everyone else has been doing it.

Wow, cool, I lifted most of my clicks from the macro compendium page which always had the fall through in a click macro, i think I will try this and see what difference it makes :)

MIght be the " /cast elemental mastery" line, but I don't remember how I have mine placed in my macro (@ work now).

Well I tried this one and it casts Lightning Bolt once and never again :

/run SetCVar("Sound_EnableSFX","0")


/use 10
/use 13
/cast Blood Fury


/click sdf__DPS1
/click sdf__DPS2
/click sdf__DPS3
/cast Lightning Bolt

/run SetCVar("Sound_EnableSFX","1")
/script UIErrorsFrame:Clear()

Gotta be honest here, my elemental shaman click macro is good enough that I use it when solo raiding with my shaman. Yeah, purist raider may take a shot at me but I have yet to raid with my 5k GS shaman and not pull more than my share of damage done/DPS. Its nice to be able to watch for other events other than spell refreshes (i.e., using purge, situational totems, etc.)

Good stuff.

Quote:

---

Originally Posted by Greythan

Gotta be honest here, my elemental shaman click macro is good enough that I use it when solo raiding with my shaman. Yeah, purist raider may take a shot at me but I have yet to raid with my 5k GS shaman and not pull more than my share of damage done/DPS. Its nice to be able to watch for other events other than spell refreshes (i.e., using purge, situational totems, etc.)

Good stuff.

---

Would you mind linking it as I can't seem to get this working?

My comma's assume a click every half second, and I have extra duration on Flame Shock for the Tier set bonus.

#show Lava Burst
/Cast Elemental Mastery
/Click MultiBarBottomRightButton7
/Click MultiBarBottomRightButton8
/Click MultiBarBottomRightButton9
/Click MultiBarBottomRightButton10
/use Endless Mana Potion
/use 13
/use 14

#show Flame Shock
/castsequence reset=combat Flame Shock,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,, ,,,,,,,,

#show Lava Burst
/castsequence reset=combat Lava Burst,,,,,,,,,,,,,,,

#show Chain Lightning
/castsequence reset=combat Chain Lightning,,,,,,

And Lightning Bolt, from the spell book.




*Edit*
There is no space between groups of commas.
The forum adds that, for some reason.

Quote:

---

Originally Posted by Ualaa

My comma's assume a click every half second, and I have extra duration on Flame Shock for the Tier set bonus.

#show Lava Burst
/Cast Elemental Mastery
/Click MultiBarBottomRightButton7
/Click MultiBarBottomRightButton8
/Click MultiBarBottomRightButton9
/Click MultiBarBottomRightButton10
/use Endless Mana Potion
/use 13
/use 14

#show Flame Shock
/castsequence reset=combat Flame Shock,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,, ,,,,,,,,

#show Lava Burst
/castsequence reset=combat Lava Burst,,,,,,,,,,,,,,,

#show Chain Lightning
/castsequence reset=combat Chain Lightning,,,,,,

And Lightning Bolt, from the spell book.




*Edit*
There is no space between groups of commas.
The forum adds that, for some reason.

---

Thanks for the reply. I will play around with the setup you have.

Mine is a near mirror image of Ualaa's.

Make sure that you re check your flame shock duration. Since it's influenced now by haste. On my ele's I have 3 times a different amount of comma's.

How do you guys deal with the varying amount of haste like elemental mastery going off or heroism?
Set your macro for too long of a delay and flameshock goes off or too few and lava burst gets unused for a few sec.

too early and you'll be standing still and waiting for cool down.

I dont know the timings as I dont use this "maxdps" stuff myself but you can do this better with IsBoxer by checking the button "do not advance to the next step for X seconds" and just having one step per cast.

So IsBoxer - Keymaps - New Key Map - Mapped Keys - Step One - New WoW Macro - /cast flame shock

"Do not advance to the next step for 4 seoncds (or whatever the flame shock cast time and gcd is well 2.5 I guess)

Then for step 2 you do /cast Lava Burst and make the do not advance for Lave Burst cast time plus gcd (plus about .5 seconds I would guess to account for lag depending on your latency)


Step 3 would be /cast chain lightning with the "do not advance" set to cast time of CL and its gcd

Step 4 would be /cast lightning bolt with the "do not advance" set to cast time of LB and its gcd



What happens is that the first key press causes step one to fire, the 2nd press of that key, if done before the set time will not do anything. ONly keypress after the set time will trigger anything (say you said "do not advance to the next step for 4 seconds" then after you press the key the first time if the 2nd press is before 4 seconds after the first press nothing happens. You then press again and if its after the 4 second "lock out" then the 2nd step fires, if not then again nothing happens. The fact that its not a delay (you must press the key again if you press it before the lock out time) but a "lock out" keeps it legal from what Lax explains and what seems resonable enough to me. You must always press the key for something to occur, this just lets you spam (like all the ,,,,,, above) and stops some key presses from doing anything.


If the gcd on LB makes the whole 4 steps over the cd on /flame shock then yur done! If not add in some LB's untill you are over the Flame shock cool down.


Now you can spam at any rate and assuming you spam at .25 seconds intervals you will be at close to single character dps (actually probabaly better lol). As the faster you spam the more dps you do (well maybe like 4 percent mroe by spamming twice as fast or something). I am sure this is more dps then one person controling a single toon and mouse moving / clicking on icons for each spell cast.

I've never used /click as its clear you have to press at some known rate so you know how many ,,,,, to insert. I just think that you can't always press at .5 second intervals or whatever you are planning on.


I know this explantion is hard to follow maybe our resident IsBoxer experts Lax or Ualaa can rephrase it with additional clarity.

Quote:

---

Originally Posted by Sam DeathWalker

"do not advance to the next step for X seconds"

What happens is that the first key press causes step one to fire, the 2nd press of that key, if done before the set time will not do anything. ONly keypress after the set time will trigger anything (say you said "do not advance to the next step for 4 seconds" then after you press the key the first time if the 2nd press is before 4 seconds after the first press nothing happens. You then press again and if its after the 4 second "lock out" then the 2nd step fires, if not then again nothing happens.

---

You can't create macros that work off of timed delays in game, and you can't have the game make decisions for you {if x amount of time has passed, allow this, otherwise...}. Using external programs to circumvent that would be against the rules.

Quote:

---

Originally Posted by Igg

How do you guys deal with the varying amount of haste like elemental mastery going off or heroism?
Set your macro for too long of a delay and flameshock goes off or too few and lava burst gets unused for a few sec.

too early and you'll be standing still and waiting for cool down.

---

If you want absolute maxdps you'll need to have another key with different timings, one set for no haste buffs, another set for when you have one hast buff, and other for whatever haste combos you can think might be on you.

Its not easy thats why its taken me like another 3 months to redo my hardware and software but .....

Still if you are just playing shaman and you are talented and glyphed for the FS/LB/CL (LB?) rotation and thats always your maxdps haveing extra keys dependant on haste isnt all that hard.

You can't create macros that work off of timed delays in game, and you can't have the game make decisions for you {if x amount of time has passed, allow this, otherwise...}. Using external programs to circumvent that would be against the rules.



I had that concern at first but becuase its a lock out, not a delay it seems OK to me. You are correct if it was a Delay it would be illegal for sure. But again exactly what rule does this violate?



... I thought it was illegal also at the first but after Lax explained it to me it seems ok. It follows the one action one press rule. And remember, if you press once it fires, if you press the 2nd time inside the time limit it does nothing you STILL have to press after the time limit for anything to be done.

Its the same as the ,,,,,, are they not telling you that the key press is to do nothing if the press is done at a time interval known to you (i.e. your press rate). You are inserting a delay based upon your click interval (which I assume you know what your click interval is), how is this different?


Or if you spam a single spell and its cool down is not up the press does nothing .... again how is this different then that?

Yet antoher way to look at it is if you have 4 different keys, one for each step/macro. If you spam 1-2-3-4 what happens? Well if you hit key 1 then pressed key 2 before the gcd was up from the spell on key one nothing would happen. You could press key 2 many many times and if the gcd on key 1 was not expired then nothing happens. Surely if its clearly legal with 4 keys then its legal with one key (and again with 4 keys its better cause the game will adjust for haste effects for you instead of you have to miss out a bit).

Quote:

---

Originally Posted by Sam DeathWalker

I had that concern at first but becuase its a lock out, not a delay it seems OK to me. You are correct if it was a Delay it would be illegal for sure. But again exactly what rule does this violate?

---

And how do you do this in game? /castsequence spell, null is how lockouts are created with ingame macros. No matter how you create that macro, you cannot use ingame means to tell that macro to progress to another macro after exactly x seconds and not before. You are using a delay to interfere with the game.

Quote:

---

... I thought it was illegal also at the first but after Lax explained it to me it seems ok. It follows the one action one press rule. And remember, if you press once it fires, if you press the 2nd time inside the time limit it does nothing you STILL have to press after the time limit for anything to be done.

Its the same as the ,,,,,, are they not telling you that the key press is to do nothing if the press is done at a time interval known to you (i.e. your press rate). You are inserting a delay based upon your click interval (which I assume you know what your click interval is), how is this different?

---

It also only takes action based on timed actions that can only be processed via an external program. There is no way for you to use ingame macros to mirror the same actions. Innerspace is deciding what spells you cast and when, not you. People using /click macros have to guesstimate based on averages for DPS. If their click rate is not steady, or they have to go "off script", their DPS will be altered. Your method, however, removes all that tradeoff and allows you to basically say "cast this until I can cast this other spell". Your means does not care if you press the button or not, only how long your cooldowns have been ticking.

Quote:

---

Or if you spam a single spell and its cool down is not up the press does nothing .... again how is this different then that?

---

We aren't talking about 1 spell, we are talking about an entire sequence.

Quote:

---

Yet antoher way to look at it is if you have 4 different keys, one for each step/macro. If you spam 1-2-3-4 what happens? Well if you hit key 1 then pressed key 2 before the gcd was up from the spell on key one nothing would happen. You could press key 2 many many times and if the gcd on key 1 was not expired then nothing happens. Surely if its clearly legal with 4 keys then its legal with one key (and again with 4 keys its better cause the game will adjust for haste effects for you instead of you have to miss out a bit).

---

No, what you're doing is pressing 1234 and Innerspace is saying "at 0.0sec allow 1. at 0.1 seconds, allow 1.......at 1.5sec allow 2. at 2.5 allow 2. at 4.0sec allow 3...." If I spam 1234, what I get depends wholly on what key was actually pressed first. I press 1, it's going to be 1 that is received and processed by the server. Not 1 unless 2 is availiable.

Quote:

---

If their click rate is not steady, or they have to go "off script", their DPS will be altered

---

And the same is with IsBoxer, lets say you program step one not to advance to step two untill a 4 second lock out. If you press at 3.9 nothing happens, lets say then you dont press agaoin untill 6.4, your dps will go WAY WAY DOWN. Your max dps is if you press just after the 4 second lock out ends at by pressin at 4.1. For every 1/10th of a second you dont press after the lockdown is over (i.e. the cooldown is expired) you lose dps just like the ,,,,,,, system.

Quote:

---

ou cannot use ingame means to tell that macro to progress to another macro after exactly x seconds and not before. You are using a delay to interfere with the game.

---

If you can use ingame means to progress to a spell after exactly x seconds (and take into account haste which IsBoxer cannot do with one key) legally why would it suddenly be illegal to progress to a macro instead of a spell? Keep in mind what you say is not exactly what it does it "Will not progress to another macro no matter how many times you press the key until after exactly x seconds and not before" its a negaitve not a postive. Your statement makes it sound like it automatically progressed to another macro without a key press, that is not the case.

Quote:

---

We aren't talking about 1 spell, we are talking about an entire sequence

---

True and what rules says a spell is legal and a macro is illegal? In fact the way its being used here is a macro that actually is only one spell ..... Clearly there is no difference between casting a spell or casting a spell with a single line macro .... But what you say is true you cannot, with a single key, ingame, advance to another macro with a lock out. Unless there is an addon which lets you reassign a key to another macro in battle on the fly. Still I am not aware of a rule that is violated if you do for a macro what you do for a spell. But you can do so with 2 keys .... makeing one key act as two or more is the whole point of macros ....

Quote:

---

No, what you're doing is pressing 1234 and Innerspace is saying "at 0.0sec allow 1. at 0.1 seconds, allow 1.......at 1.5sec allow 2. at 2.5 allow 2. at 4.0sec allow 3...." If I spam 1234, what I get depends wholly on what key was actually pressed first. I press 1, it's going to be 1 that is received and processed by the server. Not 1 unless 2 is availiable.

---

When you press "1" one fires THEN you move to key 2. Key 2 will NOT FIRE if gcd is not expires on the spell cast by the first key. That is EXACTLY what IsBox does, the next spell will not fire unless the cgd is up on the prior "step" or in this case key. You have to press key 2 as soon as key 1 expires its gcd to get max dps. Then as soon as key 2 fires you move to key 3, no matter how fast you press key 3 the game locks you out from casting the spell (or macro) on key (step) 3 untill the gcd is expired on the spell cast by key 2.

To get max dps you have to press 1 (Flame shock) then 2 (Lava Burst) then 3 (Chain Lightningh) then 4 (Lightning bolt) then back to key 1. If you press the lava burst key before flame shock gcd is expires the game locks you out. This is exactly what IsBoxer does with one key instead of 4 and IsBoxer cannot take into accout haste, like this 4 key combo will.

If its legal with 4 keys each pressed one time then how could it be illegal with one key pressed 4 times?


Like I say I havn't used this yet cause with 22 shaman I dont care about maxdps. I just use chain lightning mostly, not even talented for max Lava Burst. But I do have it programed for thunderstorm round robin so I can't cast then to close together (i.e. my delay is the 45 seconds cooldown (if that what it is) divided by 22 so that when I cast the last one the first one is available again), but I havnt used it yet as not all my guys are high enough to even have thunderstorm. I guess "use with cation" would be the advise. Again it looked to me to be illegal cause I thought that if you press the key first time and then press then key again it would fire off the 2nd step after the set time automatically, and that would be illegal. Thats not how it works though you still have to press the key a 2nd time after the gcd is over if you pressed it the first time while the gcd was not expired, and all presses before the gcd is expired will be null, in the same manner you progamed in a number of nulls with the ,,,,,,, system.

Quote:

---

Originally Posted by Khatovar

And how do you do this in game? /castsequence spell, null is how lockouts are created with ingame macros. No matter how you create that macro, you cannot use ingame means to tell that macro to progress to another macro after exactly x seconds and not before. You are using a delay to interfere with the game.

---

Yep, that's because the game knows exactly when the spell has fired. With a "/castsequence Spell A, Spell B", the game will not progress to Spell B until spell A has cast. Whether you are using the timing mechanisms in ISBoxer or in other software (Logitech, X-Keys, nostromo, pinnacle, etc) there is no way to tell when the spell has fired. Suggesting that this is "using a delay to interfere with the game" is quite silly and I'd suggest you don't understand what you're talking about. Neither "delay" or "interfere" accurately describe what the feature does.

If you're going to make the argument that "because X feature is not built into the game, X feature is illegal" then you might as well throw key/mouse broadcasting right out the window, because it's not built into the game.

Quote:

---

Your means does not care if you press the button or not, only how long your cooldowns have been ticking.

---

It has no clue how long your cooldowns have been ticking. This feature is not magical and ISBoxer knows nothing about the game environment.

Regardless of what you all think is right or wrong, the rules are actually pretty clear to me. What you all read as "1 key = 1 action" really means that you can't press 1 key and walk away while it continues casting your dps sequence for you. They don't want you to be botting -- they don't give 2 shits if you're pressing 1 key and at that instant it spams 2 keys, that has nothing to do with botting. The quote about 1 key needs to be taken in the context of the thread it was in, where the GM was clearly getting frustrated about people asking about the difference between being a bot and not being a bot. It's almost like the "keyclone is fine" post. You guys read way too much into everything any GM ever says, and the words get twisted into whatever the hell you want them to mean instead of the original meaning.

There was a recent discussion on "the other site" where someone had a 24 hour ban for an unknown reason and my competitor suggested it must be ISBoxer. After a week of people whining about how it's possible to hit 2 keys at the same time while only pressing 1 key, the person who got banned found out it was about a naming policy violation and completely unrelated to multiboxing at all. Then that person asked a GM about the 2 keys thing, and the GM said spamming keys doesn't matter (but don't go overboard either), they don't want you to e.g. press 1 key and have it jump, spin around, shoot someone, spin back around etc.

There's numerous methods to achieve essentially the same thing, whether it's in WoW itself, from ISBoxer, from other software, from a WoW Addon, from hardware, etc. Don't get all up in arms when one of them works slightly different from another. If they were all exactly the same, what's the point? It doesn't mean you're "interfering" or "breaking the rules". Relax and play, we're all multiboxing here, and we're all within the rules. A year and a half ago, people were saying ISBoxer is against the rules. Today, people still are saying that. And yet nobody has been banned for using ISBoxer, and if you ask Blizzard about it, they're not concerned about it. In fact, the person I mentioned previously says when they called in to phone billing, they asked BILLING about it and apparently a bunch of people in that dept happen to use ISBoxer and love it.

Hell, Blizzard knowingly and purposefully activated my SC2 beta the other night.

Whatever you guys want to believe is whatever you want to believe, but I'd recommend just going back to playing and forget all of these arguments about X feature. As I said before, these kinds of discussions are not helpful, it's just flame wars and trolling between people who are all following the rules.

I'm sorry Lax, but you aren't Blizzard. You are a guy selling a subscription product that is fast becoming the "top dog" of boxing because of it's ability to 'creatively solve' problems and limitations boxers come across.

Now, I go to the wow forums and say "Hey! I'm ret and I want a macro or a mod that will allow me to use my normal sequence, but every 15.5 seconds, as soon as Exorcism is up {giving me half a second for latency}, I want that to go off instead. But only if it's instant, so the game needs to trigger a separate macro at exactly 15.5 second intervals so the /stopcasting doesn't kill my swing timer. I don't want to have to think about pressing another key, either, so I don't want an alert, I just want it to work off the same macro." What kind of answer you think I'm gonna get?

Yet, you seem to think it's perfectly fine to program it in ISBoxer so that I can do just that, because if I create "steps" I can sit there spamming my 2 key and ISBoxer says it's 2 for 15.5 seconds, then says it's 3, but not a second before that. Then says it's 2 again for exactly 15.5 seconds.

I don't care about 1 key being multiple things, that's pretty much exactly what /click accomplishes. What I take issue with is the explicit timing that allows you to do something until an exact predetermined time, at which point something else happens, or rather is allowed to happen.

I would tend to say...

Even if you have the option to:
a) Press 1 = Flame Shock, do not advance for 2.0 seconds.
b) Press 2 = Lava Burst, do not advance for 3.0 seconds.
c) Press 3 = Chain Lightning, do not advance for 3.0 seconds.
d) Press 4 = Lightning Bolt, do not advance for 3.0 seconds.

Or whatever the specific timing you desire...
This is far sub-optimal, compared to a click castsequence.

With a click system, we are essentially setting up a priority system.
Where spell 1 will fire off every "x" seconds, determined by our commas.
And spell 2 fires off every "x" seconds, also determined by the commas.
Ditto for as many other spells as we want to include.
With a fall-through which fires off when everything else is on a comma stage (cooldown or dot ticking).

With fixed delays, you are still stuck with:
- A >> B >> C >> D..... Repeat.
But what happens when you want your actual order to be:
- A >> B >> C >> D >> D >> C >> B >> D >> C >> D >> B >> A...
IE, variable cooldowns, not a perfect sequence of 1234, 1234, 1234....

A click castsequence is good any time your spells have variable durations or recast delays.
The only time the fixed sequence is optimal, is when every spell is an instant cast, such as a Pally's 96969 sequence.

There isn't much difference in game effects, between a delay caused by the number of commas in a macro and a fixed software option, where the next step cannot occur for "x" seconds.
However, the game effect forces us to click at a consistent speed, while the software option hard codes it, no matter how quickly or slowly we click our keys.
I'm personally not comfortable with fixed duration delays, no matter what my spam speed is, but some are comfortable with that; consequently even if fixed delays were as strong as a click castsequence, I wouldn't go this route.
It will come down to a preference for a given user.

I never claimed to be Blizzard. You're not Blizzard either.

That's what has you so concerned? That you can set it up so that it can advance to the next step (or reset to the first step) the next time you hit the key after x amount of time? lol. I believe GCP also has this capability.

You know what I find that feature most useful for? I set it so that my round robins stick to the same step for at least 0.3-0.5 seconds, because I don't want to skip a guy in the rotation just because I hit the key 0.1 seconds before the global cooldown is up. So I can whack the key a couple times until it casts and not mess up the entire round robin rotation. I also tell it to reset after the amount of time of the cooldown, so it goes back to the first guy in the rotation.

But as far as exorcism every ~15.5 seconds (and no, there is no way you're going to get it at "an exact predetermined time"), how is that not "pretty much exactly what /click accomplishes"? They're both timing mechanisms that allow you to spam 1 key to make different things happen at different "exact predetermined" times.

You don't like ISBoxer. We get it. If you don't like it, don't use it, it's as simple as that.

Quote:

---

With fixed delays, you are still stuck with:
- A >> B >> C >> D..... Repeat.
But what happens when you want your actual order to be:
- A >> B >> C >> D >> D >> C >> B >> D >> C >> D >> B >> A...
IE, variable cooldowns, not a perfect sequence of 1234, 1234, 1234....

---

Im not up on maxdps but my understanding is that the 1234 is always the maxdps rotation. Expically if you have talented and glyphed just for that rotation. I dosnt change unless you get hasted maybe. Why would you ever want to do less them maxdps? If the maxdps sequence is ABCDDCBDCDBA then you just add more steps untill you have the maxdps. Like the one minute cooldown on umm something of doom warlock(?) spell? You can add enough steps untill you use up your one minute and the sequence repreats again.

Quote:

---

Even if you have the option to:
a) Press 1 = Flame Shock, do not advance for 2.0 seconds.
b) Press 2 = Lava Burst, do not advance for 3.0 seconds.
c) Press 3 = Chain Lightning, do not advance for 3.0 seconds.
d) Press 4 = Lightning Bolt, do not advance for 3.0 seconds.

Or whatever the specific timing you desire...
This is far sub-optimal, compared to a click castsequence

---

Assuming 12341234 is in fact the maxdps rotation I don't see this as suboptimal to a system that requries you to click at spicific intervals. If you can click infinatly fast then the IsBoxer method is maximuly optimal. My opinion if would be easyer to approch clicking infinatly fast then clicking infinatly accuratly at say 1/2 second intervals ....

But millage will vary by individual I suppose if you set up a metradome and practiced a few hours a day your click would be pretty close. Or if you played with a metradome going while you play heh.... We may not be bots but if you want optimal play you have to become one lol ....

Sry for spelinz erors