Doing this also breaks the ToS, so while yes this would work fine, I don't think most people would advocate doing it.

How would this break the ToS (I assume you are referring to Terms of Service) if he is using an ingame macro and spams it? The code to do this doesn't have to be macroed from his G15, it's just a simple /cast on 3 lines

Can we drop this discussion of macros? Take it to the UI subforum. It's adding all of jack and shit to this discussion.

For those situations in which paying very close attention to your cooldowns is less important than giving that attention to your surroundings, I have a solution that works much better for me than a macro. I simply "chord" (think piano) my SS, ES, and LL buttons -- they're all right next to each other on my keyboard -- and then use PowerAuras and ShockAndAwe for cues to hit LB or CL. If you are spamming all three buttons, it will always use whatever comes off cooldown first. 90% of the time you can pay attention to priorities and using them in the proper order, but it makes it very easy to switch back and forth between the two methods.

A bit of anecdote:
1.
Tried a bunch of things last night at the training dummy, including two castrandoms. The second one was basically a summation of all the ideas posted yesterday:
- It worked surprisingly well
- Have to press the button up to four times every cooldown; difficult to tell if all abilities are on cooldown and you're just pressing it for no reason. I can't imagine hammering the thing for a ten minute fight
- No dps time is lost via the stopcasting; however, player animations do very strange things
- Less than 100 dps lost (did short tests so I can't say exactly how bad it was)
- I really don't enjoy it.
2.
While I was there, I did a little testing of WF/WF vs WF/FT. There wasn't a huge variation between the two (less than 50 dps), but WF/FT was definitely more consistent. WF/WF started out low, and raised up as I got more big MH procs (other tests might be the reverse). I took WF/FT to the raid that night and basically hung around 2000 dps on each boss fight. Counter this with last week, where I had a fight at 2200 and a second at 1700.
3.
There was an enhancer from our server's most successful Sunwell guild as well...he mentioned that after 200 million damage worth of tests, he'd chosen WF/FT and the Grip of Mannoroth over Mounting Vengeance (claiming a 20 dps increase). He was expertise capped, had around 7% passive haste and had a "second shaman" spec (3/3 S. Shock, 3/3 Imp Shields, no UR). I don't argue with empiricism -- so let me just say that I'm considering that the fast/slow question for offhands with flametongue might be unresolvable. It will depend on the weapon, the shaman and the raid.
4.
Finally: I adapted my standard LB button with a /stopcasting. I'd say I prevented myself from casting early five or six times; and about as many times I stopped myself from casting when I really wanted to (against a fleeing mob and when in the trench for Gurtogg). Allover I think it's a win if only as a "trainer" for MW -- I have a feeling in two months none of us will need it.

I tried running my normal 2.6/2.5 set up and then tried it with 3/3SS and 3/3 Imp S., and a 1.5 OH. It came to a 91DPS upgrade. 95DPS upgrade if I stuck with the 2.5 Speed OH. Afraid I cannot bribe any hunters to spec marksman though, so I'll be stuck with UR duty till DK's are around.

For your lightning bolt issue, would adding a modifier to the macro help?

would that let you get one off with a cast time if needed?

Fixed your macro.

I think more Hunters will be willing to play MM then you realize. The dps is pretty amazing and there is less pet management involved.

Well that option is there now as well. The former spellcrit gem is now crit for all. So it looks like there is a possble change there.

Long time reader, first time poster.

As to the random macro, I'm fairly sure you can put more than one instance of an ability in it to increase the probability of it happening. My warrior buddy does this for his spamming, and I've used it too. In mine I've got more stormstrikes and earth shocks than lava lash, in case both are up when the button is pressed. And as for hitting the button for 10 minutes straight, it helps a lot to just bind it to your mouse wheel in both directions and spin it. You get the most button 'presses' in the shortest time in case the macro selects things on CD repeatedly.

is there any word on whether or not the orc racial Command (5% bonus pet damage) applies to Feral Spirit?
I couldn't find anything on the 3.0.2 compilation page, and i searched this thread with the search function, so i'm sorry if it has already been answered.

I can't seem to find or successfully build a working WF/FT imbue macro that kills the "do you want to replace" pop up we see when we don't have dual WF/WF.

Has anyone come up with one that kills the popup and cast finger, but doesn't error when you don't have the imbues yet?

This seems like a tool that could be handy if WF/FT truly becomes THE thing, as it seems to be.

I found this on the official WoW-Forums courtesy of Lunessa (Kirin'Tor)
It just removes the current imbue and applies a new one. 1click cast, no popup.
Works fine for me, just change the offhand enchant to Flametongue Weapon if you're using it.

This also works (I bind weapon refresh to numpad3):
You can use /castsequence or /castrandom on a slot #

Ah!! that one looks promising, I was digging for something like /usesequence or some way to sequence though sets of commands but if you can use the slot numbers in /castsequence that is cool.

the /click StaticPopup1Button1 doesn't cause an error when there is no current imbue?

will have to try this when i get a chance later! Thanks

I apologize for the useless post but that seriously is the nicest macro I have seen yet, really nice job. No errors unless you press it too fast since if the GCD is active it will move forward on the chain but the spell won't cast due to the GCD. It corrects itself when you let the macro reset itself but did stick FT on my mainhand when I clicked it too fast. Then I just waited the 5 seconds and clicked a bit slower and it was fine.

I'm actually starting to think about how valuable, if valuable at all, MP5 or spirit would be, not much but not nothing.

Blood Fury now has a GCD. Occurred when they removed the MS component so not sure if intended or not.

I apologize very much if this has been addressed in the thread, but I couldn't find it here or in any of the other threads on the board, searching 'heroic presence' and 'draenei racial'.

The Draenei racial, Heroic Presence, which is now a unified 1% spell and phys hit - does anyone know if it still stacks such that two Draenei in a group will get both their own and another's as it did pre 3.0? I'm having real trouble hitting my spell hit cap (well, I have a plan for it, but it involves 55 more badges than I have right now) and hoping I just might be there already, functionally. The chance of NOT being in a group with another draenei at any point in time, given my guild composition, is slim. We have draenei in tank, melee, ranged, and heals, so I can pretty much count on them.

So do I need 16% from gear+food, or 15%, before the value drops?

hit rating values are in Toot's 3.0 pocked guide in the think tank thread...

Shaman: Enhancement post number 8

I was never under the impression it stacked at anypoint

I think the only stacking was how a casting class would have the 1% apply to spells and a melee class would have the 1% apply to melee so if grouped with a melee and a caster Draenai in the same group you would get 1% melee as well as 1% spell hit instead of just one or the other. I don't think it ever stacked higher then that 1% though no matter how many you had in that single group.

The 2 different buffs stacked. Caster draeneis(mage, priest, shaman maybe) had a spell hit buff, and melee draeneis(warrior, hunter, paladin maybe) had a melee hit buff. In early beta I believe they were still stacking depending on the original buff(so you'd actually get 2%hit from having 2 different draeneis archetypes in your group), but I somewhat remember reading in some patch notes/undocumented changes it was fixed.