Nabith

I've been delving through the hunter posts, trying to find the ideal speeds to use the different shot rotations. (I'm looking for "In a perfect world x.x attack speed would be perfect, but slightly higher is okay too.)

The most information I've found has been on the 3:2 macro, where it says to be no faster than 2.10 attack speed, and that around 1.90 the macro auto adjusts into 1:1.

For a 2:1 macro I saw a 2.2 attack speed is recommended.

For 1:1 it said faster than 1.9, but I couldn't find what speed is "ideal".

And I didn't see anything on the 1:1.5 macro, though I'm currently using it with a 2.28 attack speed. (Survival)

Any insight would be helpful.

 

Female Tauren

How does latency affect this? My auto is at 2.17 speed but I also have a ~250 ping, would bringing auto down to 2.10 make a huge difference for me?

 

Manito

2.10 with 250 ping would probably result in 2:1 instead of 3:2 about 30% of the time, give or take. You would want to get your auto attack speed to the 2.00-2.05 range most likely.

Manito
Manito's Modified 3:2 Macro
Separated macro that reduces KC lockup issues.

 

Female Tauren

So I switched the illidan bow to the badge xbow, now my auto speed is 2.03, however I'm noticing a lot more clips than before...hmm so confused.

 

Mr Tazza

What would you suggest then, while waiting for Shivering Felspine to drop?

I'm standing at the usual 2.17 speed with Bristleblitz Striker and using a 3:2 macro (which obviously isn't good at all), should I buy badges' crossbow? Should I switch to 1:1? Or should I just keep going like this hoping to get the necessary haste loot soon?

 

Rensho

Hi. I am using Sunfury Bow of the Pheonix, and being BM specced I end up at 2.10 weapon speed.
I tried the 3:2 macro and I managed to get it to a 2:1 ratio (SS/AS) 4 times in a row. Why?

My MS is usually around 150.

EDIT: I'm afraid of using my old 1:1 macro. It got stuck way too often
EDIT 2: I got 20 haste rating from Hauberk of the War Bringer, no problems now.

 

Manito

As you can see in the most recent post, it's really not an exact science - more haste, try and lower your latency, find the breakpoint that works best for you.

Badge crossbow is definitely worth it, but if you want to keep using Bristleblitz, you'll have to stack some more haste, and figure out what works for your latency.

Manito
Manito's Modified 3:2 Macro
Separated macro that reduces KC lockup issues.

 

Mephala

Hi all!

This is my first post here. First of all sorry for my bad english.

2 days ago i respecced to SV, and i cannot find a good macro nowhere..
so i went to Dr. Boom to make one.
I realized that i cannot compare the macros via damage done, because of the small sample taking time.So i realized that the efficiency of the macro depends on the "shot per second"-ratio. When i was BM i started with the simple /castsequence macro with 1:1, than i swiched to a more effective 3:2. This 3:2 delays auto, but make a bigger "shot per second"-ratio.

so i keep trying to make some similar for SV hunters. I find out this. i achieved with this macros the highest "shot-per -second" ratio. I'm not 100% sure what im done, because im not an expert in macros,but it works. Both macro uses the separeted KC-macro form Manito. You can attach the usual spam removing and sound removing lines.

Macro without Multi-Shot:
Macro with Multi-Shot
Please try out, and any comment would be appreciated.
regards

Mephala

 

Aiyakido

Oke, specced back to BM (I just pump out loads more of DPS in BM then surv, guess im not a surv palyer ) and im walking around with the Shivering felspine and Badge bow. Now having this awsome AS of 1.9 or something this works really great. (should just stik with the 1:1 right). Anyway. My biggest question atm (cant seem to get the calculation's right myself so) is how much more haste rating do i want before i can just forget about haste items.

 

wilfbrimer

SV is more about increaseing overall raid dps than individual DPS. It provides a non stacking debuff on the boss which increase all physicaly damage raid wide to the boss. If your raid has alot of physicaly damage, IE rogues, fury warriors, Ret Palies and hunters then you should have one sv in it, note one only as the debuff doesn't stack.

 

Thereos

well what i am wondering about with all the shot rotation things and +haste stuff ...
can someone tell/explain me how much hasti need with the legendary bow of KJ
and a macro timed rotation with a latency of like 90 ms ???

 

Borsch

OK, i've read pretty much hunter stuff today and now i wonder about several things.

My hunter has an attack speed of 2,17.
Hes a BM.

After running Cheeky's i've come to the conclusion that a 1:1,5 rotation does the most dps.

For longer fights, a 3:2 rotation would be best.

But running a
/cast Auto Shot!
/cast Steady Shot
makro results in a 4:2 rotation (due to lag, fps or whatever)

Now what should i do?
Use a /castsequence AS, SS, SS, AS, SS makro?
Time it by hand (which is anoying )?
Use something totaly else?

Getting some haste would solve the problem, but i cant get it atm :/

Any suggestions?

 

Manito

Since you are running at 2.17 attack speed, 3:2 definitely won't work well for you, and will result in a 2:1 most of the time. With a little increase in haste (get to the 2.00-2.05 range) you can run a 3:2 with great results, otherwise, you'll have to stick to a 1.5:1 rotation most likely. I'd say go for the haste, and run the macro in my signature, see how it treats you.

Manito
Manito's Modified 3:2 Macro
Separated macro that reduces KC lockup issues.

 

mokki

Looking for opinions on shot rotations for my current set up. The World of Warcraft Armory theres a link to my armory it should be pretty up to date. should i be using the 3:2 or the 1:1 ? or maybe starting with one and switching to the other at a given time?

PS. im prolly playing with medium lag.

 

Mercuri

Hi,

some personal stats:
Attack speed: 2,01
crit: 27.86% (around 35% raid buffed)
hit: 130 (but always boomkin in raid)
gear is: 4/5 T5 (End SSC/TK gear

Ive been using the 3:2 macro for a while:
#showtooltip Steady Shot
/cast !Auto Shot
/cast [target=pettarget, exists] Kill command
/cast Steady Shot
/script UIErrorsFrame:Clear()

Now yesterday we where doing MH upto Azgalor and i saw that my auto-shot was clipping now and then.
i have been trying to find out what is the best macro at my current gear/speed, should i be switching to the 1:1 macro?

1:1
#showtooltip Steady Shot
/castsequence reset=2.01 Steady Shot, !Auto Shot
/cast [exists,target=pettarget] Kill Command
/script UIErrorsFrame:Clear()

Also a question for hunters raiding Mount Hyjal what is your DPS there and where do you end up in the DPS list on bosses? ive found that when in MH ill mostly end up around the 5/6 spot on dps while in other instances (beginning BT, full SSC/TK) ill be on top 2/3.
Is this because the ammount of AOE other classes put out?

Mercuri

 

KraxisSingular

Don't even think you can match Mages/Warlocks on DPS for the entire time. Instead if you want to flex a bit look at the bossfights themselves. I'm sure you will be back at your usual spot. But all that AoE is crazy. You can't hope to match mages and Warlocks that put out 3-4k DPS.

 

Bikiniwax

Clipping is fine. You should never use the /castsequence 1:1 macro. It is terrible because of the client->server->client communication/latency requirements.

 

wilfbrimer

A spread sheet where you enter in an adjusted weapon (mabye just weapon speed, then passive haste and a check box for quiver) speed, average latency that spits out the shot rotation you should be going for would answer alot of these questions. Unfortunately this is not my forta.

 

Selway

OK, I have been doing some tests and Im a little frustrated. I cant seem to get to a 1:1 rotation. Here are my results with two slightly different macros. BTW, my hunter's name is Reecher is BM and using the badge xbow.

With my original 1:1 macro I was getting 65% SSs and 35% Auto shots. Here is the macro
#showtooltip Steady Shot
/cast !Auto Shot
/cast [target=pettarget, exists] Kill command
/cast Steady Shot
/script UIErrorsFrame:Clear()


With a slightly different one I was getting 58% SSs and 42% Auto shots. Better but still far off. My Ping was between 200-250 the entire time. Here is the macro.

#showtooltip Steady Shot
/cast !auto shot
/castsequence steady shot
/cast [target=pettarget,exists] Kill Command
/script UIErrorsFrame:Clear()


So why am I not getting a 1:1 ratio? Is it my mediocre latency? Should I be getting some haste? How much? Any better ideas? Thanks!

 

Shibam

I have 2.03 attack speed BM specced with badge xbow and i am getting 3 steadys in a row with 3:2 rotation. Is this because of latency or something, because i always thought my connection was pretty decent. According to cheekys sheet 1.1x still shows the best dmg for me but i get that lock up where it takes an auto shot. What rotation or what macro should i use?

EDIT: The macro i used was the one linked in Manitos sig for 3:2

 

KraxisSingular

Because both of those are 3:2 macros...
You want a /castsequence macro if you want 1:1.

 

Aiyakido

Been trying out some stuff and using the Maxdps.com for beastmastery.

I can be wrong but it's like this for a BM hunter. If you got less then 430 haste rating (who's EVER gonna get this amount) stick with the badge xbow. if you got 430 haste rating, stop collecting and switch to the bow from the Twins.
If you dont have twins bow stick with the Badge bow

The Legendary Bow always gives best DPS no matter you're AS.

With this you guys must be abel to calculate the AS wich is best for a 3.00 AS bow ;-)

 

peteriong

I have a question about the "/cast !Auto Shot" command. What is its effect after autoshot has been toggle on?
I have performed some tests but I can't get a conclusion about this command.

Test enviroment
Bow Speed:2.8
Talnet:0/20/41
Haste Rating:61
Hasted Range Attack Speed:2.34
Haste Steady Cast Time:1.26
Latency:around 100ms
Spam speed:Manual spam about 5 times per second

Test 1
Method:
Toggle on autushot. Spam "/cast !Auto Shot" key.

Result: 171 Auto Shot in 6mins 42secs. Average 2.35 Secs per auto shot.


Test 2
Method:
Spam the macro
/cast !Auto Shot
/cast Steady Shot

Result: 128 Steady : 64 Auto Shot in 3mins 20secs. Average 1.56 Secs per steady shot. Average 3.13 Secs per auto shot.


Test 3
Method:
Spam the macro
/cast Steady Shot

Result: 125 Steady : 36 Auto Shot in 3mins 16secs. Average 1.57 Secs per steady shot. Average 5.44 Secs per auto shot.


Discussion
1) Test 1 shows the "/cast !autoshot" command has no appearant effect on auto shot only mode.
2) Test 2 shows an expected result. 2:1 rotation for a SV spec without IATOH or DST proc.
3) Test 3 shows the steady:auto ratio becoming 3.47:1. I am able to see a lot of 3 steady or 4 steady in a row during Test 3.

Casting a steady shot during an auto shot hidden cast will result in the steady shot cast being pushed back. The steady shot will cast after the auto shot hidden cast completes. But the client side GCD will start before the steady shot cast. But it seems this doesn't happen everytime in Test 3. Here is a piece of combatlog from Test 3.

03:50:46.360 Auto Shot Hit
03:50:46.360 Steady Shot Start Cast
03:50:47.443 Steady Shot Hit
03:50:47.716 Steady Shot Start Cast
03:50:48.717 Steady Shot Hit
03:50:49.248 Steady Shot Start Cast
03:50:50.510 Steady Shot Hit
03:50:51.092 Steady Shot Start Cast
03:50:51.732 Steady Shot Hit
03:50:52.516 Steady Shot Start Cast
03:50:53.397 Steady Shot Hit
03:50:54.445 Steady Shot Start Cast
03:50:54.869 Steady Shot Hit
03:50:55.743 Auto Shot Hit

Some of the timings between "Stedy Shot Start Cast" and "Steady Shot Hit" are quite strange. But the average 1.42 Secs per steady shot in 8.509 seconds is an acceptable result. Assuming the hidden auto shot cast time is 0.5 seconds. The second auto shot hidden cast should be beginning at 3:50:48.200. But a steady shot cast was performing at that moment. So the second auto shot hidden cast should be starting right after the steady shot cast, which finshed at 3:50:48.717. From 3:50:48.717 to 3:50:48.767, the auto shot hidden cast should be performing, every steady shot command received should be pushed back until the auto shot hidden cast finished. But this didn't happen, there was no auto shot cast and another steady shot cast performed at 3:50:49.248. 3:50:49.248 - 3:50:47.716 = 1.532 seconds, this is close to the 1.5 second GCD. It also means the client side could not send steady shot command from 3:50:48.717 to 3:50:49.216 due to GCD. There