Hello, about the new macro, I've found 3 different versions of it - which is the right and correct one?

#showtooltip
/assist [help, combat]
/stopmacro [help]
/castsequence reset=target/3 Steady Shot, !Auto Shot


/cast !Auto Shot
/cast [target=pettarget, exists] Kill command
/cast Steady Shot
/script UIErrorsFrame:Clear()


#showtooltip Steady Shot
/assist [help, combat]
/stopmacro [help]
/script UIErrorsFrame:Hide()
/cast [exists,target=pettarget] Kill Command
/castsequence reset=target/3 Steady Shot, !Auto Shot
/script UIErrorsFrame:Clear(); UIErrorsFrame:Show()


Thanks in advance~

These are the macro's I use.
1:1 rotation with KC in as well. (Better mana efficiency)

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

3:2 rotation with KC. (Better DPS)

/cast !Auto shot
/cast [target=pettarget, exists] Kill command
/cast Steady shot
/script UIErrorsFrame:Clear()

Thanks, I'll use that one since it seems to be more suited for slower bows then the Wolfslayer.

Also I would like to confirm something. Is the Vengefull Waraxe really better then Legacy?

It is indeed.

You can use the "spam macro" for 1:1 rotations aswell.
:
/cast !Auto shot
/cast [target=pettarget, exists] Kill command
/cast Steady shot
/script UIErrorsFrame:Clear()
:

What you need to do is simply tap the macro three times fast, and then let your shot go off, and then tap three times again. Rinse and repeat.

Ok, not sure if this has been answered already, but I really don't have time to go through 100+ pages to find out.

I'm a BM hunter and my guild has Kara and ZA on farm. We've just started TK.

I have the Sunfury Bow of the Phoenix and the Wolfslayer Sniper Rifle finally dropped for me. I'll probably never get the rifle off Doomwalker and I don't plan on shedding 2k+ gold for the rifle once it becomes BoE in 2.4

SO, my question is this. When does it become viable, as a BM hunter to use Sunfury Bow of the Phoenix over Wolfslayer Sniper Rifle ? How much +haste do I need to stack bascially ? I don't feel like spending 250-300g on the +28crit scope for the rifle if all I need is 1-2 more haste pieces.

Thanks for the info. This site has almost doubled my DPS since I started reading it about 2-3 weeks ago.

Try using conditionals in your Kill Command line.

[target=pettarget,exists] Kill Command

When you recall your pet that should clear his target. This will cause the kill command to not fire in the macro because the target=pettarget,exists conditional fails.

Honestly this varies for everyone depending on their gear, latency, server lag, and play style. The best thing to do is spend some quality time with Dr. Boom and see what works for you. As for *me*, I found that using the new macro with no haste gear and a latency of 230 (on average) the Sunfury out performs the Wolfslayer by about 100 dps on static tests with Dr. Boom, and about 50 dps in normal boss fights.

Is it time to start a new BM hunter thread.

I've just spent a few very interesting days reading through the thread and I have to say that there is a great wealth of information in there. However, the trend is that we are starting to get more and more, which weapon is good for me posts, or which shot rotation should I use.

What I would be prepared to do, as lets face it is much more interesting that work at the moment is start a new thread which would attempt to cover the basic, how do I play questions, leaving the rest of the thread to more theory crafting.

Do any of the more established posters here think this is necessary? If so the sort of topics I think should be covered would include:

• shot rotation;
• macro's;
• weapon speed;
• gear;
• type of pet;
• pet skills;
• cheekys;
• cookie cutter specs; and
• pet's on bosses

I'm sure that there are others that people would come up with. The idea would simply be to make a linking page, for example shot rotation questions see this particulary good post.

First off
yes i think 0/31/30 is an awesome spec, you can get about 1900 AP and about 30 crit with decent gear, S1 gear t4 w/e
and x/41/x isnt a bad spec either.
but the thing is, BM / MM or 41/20/0 is THE dps raid spec now.
your pet depending on whether its a cat / scorpid / ravager will have around 150 base dps
and in t4 the hunter will have around 360 base dps
with around 27% crit
with a 15% speed quiver and 2.8 speed bow your attack speed will be at 2.08 with BM spec
that is the key to shot rotation
because your pets dps is improved, your auto shot is also improved, giving you less wasted time during a shot rotation.
ofcourse a terrible hunter can screw that up.
but BM will become THE range raid dps, in the hands of a skilled hunter
in my guild the top 5 dps is me and another BM hunter
but full epic etc etc
the other dps is a deep fire mage as well as a shadow priest
all of us have t4 pieces and are experienced

Such a thread would realy help a lot. Some parts are covered in Hunter - Help me Please, but I think we should realy have a new Summary thread like "BM Raiding Hunters in 2.3 Theorycrafting" which is kept up to date. This could realy save a lot of common questions answered multiple times in this thread.

It would be a lot of copy/paste work and credits should be given to people like glaurong, cheeky, ....
which pushed armies of hunters (including myself) to a whole other level of gameplay.

As a start I'd like to post one of the topics listed above, to see how such a ultimate BM Raiding Hunter post could look like.

[*]shot rotation macro's;

Introduction:
At the moment there exist several shot rotation macros with Steady shot and Auto Shot. It is considered the most efficient Rotation for BM Hunters because of their high attackspeed. Kill Command is included into those macros for an additional DPS boost at low mana costs.

If mana is none of a problem (f.e. with SP in your group), Beastmasters can also run what I'd like to call "Full out Rotations" with aditional Arcane Shot and Multi Shot.


Spammable Makros:

Beast Mastery Steady Shot Shot Rotation (Higher Mana Usage, Higher DPS)

#showtooltip Steady Shot
/cast !Auto Shot
/cast [target=pettarget, exists] Kill command
/cast Steady Shot
/script UIErrorsFrame:Clear()

Explanation: With the new "weird" shot mechanics (you can cast specials during the hidden autoshot casttime), this macro pulls off more steadyshots than autoshots. The result is a higher amount of shots per second, higher manausage per second, higher DPS. 3:2 rotation.


Beast Mastery Steady Shot Shot Rotation (Lower Mana Usage, Lower DPS)

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

Explanation: This makro always waits for autoshot to !go off! until the next steady shot is cast. Result: True 1:1 rota, becomes more efficient with increasing amount of haste.


Beast Mastery Steady, Arcane, Multi Rotation (Ridiculously High Mana Usage, Very High DPS) Especialy good on trash with no active CC.

...placeholder.....should be some castsequence makro..... unfortunately can't recreate it as I'm currently not at my WoW Computer


Non Spammable Makros:

...placeholder ...


Sources:

link xy


Credits(at the end of the whole post):

True masters of the Beast are: ......

----------------------------------------------------
Alle the info has been taken from this thread so far. Feel free to copy paste, improve and correct the bad language ;-). This should just be an impression of how it could look like.

I'm sorry, I don't want to seem lazy as I haven't checked all previous posts and so on but I'm slightly confused by this macro.

I know there was macros like this circulating for a while a few weeks(?) ago when it seemed auto-shot could not be "delayed", thus firing 3 steady shots in a row would give you 2 consecutive auto shots. I might have gotten this wrong, but I thought this was hot fixed as it also produced double special shots if abused.

I could go back and read, but Im not sure which posts are from this time, and which posts are after the hot-fix.

So, question is really - is it still possible to do 3:2 rotations, how do they work? (have I misunderstood the concept)

And, can you really cast specials during the hidden auto shot casttime without delaying auto shot?

Best regards
Griffen
Argent Dawn, EU.

What I am going to do is start work on the original OP post of this thread and create a culmination of the information in the 100's of pages of this mega-post. The thread will hopefully be renamed and be a focus point for BM hunters. There is too much great information here that can benefit lots of people. So, by stuffing all important information in the very 1st post, we can hopefully squash a lot of simple questions that get asked in this post over and over again. Give me a week or two to do it.

So far, it seems that with 2.7 weapon speed there is some debate as to which macro yields more DPS.

The main problem with testing Don Santos is that it has its own proc as well, and if it stacks with Quick Shots, it increases DPS at a multiplicative rate. Because of this it may have some fluctuations in DPS returns, especially if your sample is not large enough.

I suggest you run tests with each macro that covers at least 1000 shots fired, in order the reduce the variations in critical hits and procs. Also note the final critical hit rate at the end of each test run, as any large variation in this will effect the final result outside of the behavior of the macro. Did you average out all 10 runs, or did you compare them individually?

Also, if you happen to have a WWS stats account available to you or your guild, see if they will allow you to post the combat logs for each test run to compare, as with this you can use the report filters to see how many times you got a proc from each ability.

You will also have to divide the total time spent in combat by the number of procs for each, as each macro consumes different amounts of mana, and thus the length of time changes. This is primarily the reason i suggest doing your test according to the amount of shots fired, as opposed to the amount of mana consumed (the result of a 10 bars each test), because it will eliminate this last step.

This way, you will come up with both a DPS comparison, and a procs per minute comparison.

Howitzer, I wish you had decided to do this three weeks ago when as a noob hunter I read through all of the pages. I could have helped you. In any case things you should mention:

1) Shot rotation
2) Bow weapon speed
3) Scorpids how they got nurfed (mostly because there is about 20 pages worth of tests and ideas tossed around only to be nurfed)
4) Best BM pet
5) Your posts about what resists to have per raid

Those are the questions that come up a lot as I was reading all the posts.

oh and
6) New shot rotation (!Autoshot) vs old shot rotation (1:1 vs 1:2)

I wanted to try to figure out a way to test the 3:2 macro to find out if kill command is blocking auto shots. I spent some quality time with Dr. Boom to get a baseline then went to fight against a Servant of Sevine in The Blasted Lands (unkillable unless you destroy the crystal they walk around).

My pet was able to hold aggro with me using [Well Crafted Long Bow] and [Rough Arrow] allowing me to test using my full mana bar.

Macro used
#showtooltip
/script UIErrorsFrame:Hide()
/console Sound_EnableSFX 0
/cast !Auto Shot
/cast [target=pettarget, exists] Kill command
/cast Steady Shot
/console Sound_EnableSFX 1

No haste gear other than quiver (15%), no trinkets and pet was put away for Dr. Boom test.
Aspect of the Viper, Superior Mana Oil and Elixir of Major Mage Blood.
Latency was around 80 for for both tests.


Dr. Boom 1000 shots fired

Ignored the opening shots after each feign. They were always Auto > Steady and then a 3:2 cycle
Ignored the ending shots before a feign which were usually just an extra auto.
Feign and drink 6 times

Results:
186 clean cycles - full 3:2 rotation. Longest streak was 25
7 2:1 strings - steady > auto > steady between clean cycles.
3 3:1 strings - steady > steady > auto > steady between clean cycles.
7 1:0 strings - An extra steady shot between clean cycles.

Final ratio (Steady:Auto)
591:384
Or
3.07:2

I believe the break down in the rotation can be attributed to lag.


Servant of Sevine 1000 shots fired

Ignored the opening shots after each feign. They were always Auto > Steady
Feign and drink 9 times

Results:
Only 20 clean rotations (3:2) were observed in the log.
Kill Command fired 158 times during the test.
The average number of steady shots following a kill command before the next auto shot was fired was 1.85 and only 4 kill commands were immediately followed by an auto shot. The breakdown was as follows:

# Count
0 4
1 55
2 70
3 22
4 7

# is the number of steady shots that fired after kill command before the next auto shot was fired. #0 means the kill command was immediately followed by an auto shot (this happened 4 times). #4 means there were 4 steady shots fired before the next auto shot was fired (this happened 7 times).

Final ratio (Steady:Auto)
688:294
Or
2.34:1



I was using a script to fire the macro every .05 seconds.

Dr Boom (3 second sample)
2/7 20:02:53.001 You fail to perform Steady Shot: Not yet recovered.
2/7 20:02:53.047 You fail to perform Steady Shot: Not yet recovered.
2/7 20:02:53.126 You fail to perform Steady Shot: Not yet recovered.
2/7 20:02:53.204 You fail to perform Steady Shot: Not yet recovered.
2/7 20:02:53.579 Your Steady Shot crits Dr. Boom for 686.
2/7 20:02:53.891 Your Auto Shot hits Dr. Boom for 187.
2/7 20:02:54.501 You fail to perform Steady Shot: Not yet recovered.
2/7 20:02:54.547 You fail to perform Steady Shot: Not yet recovered.
2/7 20:02:54.657 You fail to perform Steady Shot: Not yet recovered.
2/7 20:02:54.704 You fail to perform Steady Shot: Not yet recovered.
2/7 20:02:55.032 Your Steady Shot hits Dr. Boom for 295.
2/7 20:02:55.844 Your Auto Shot hits Dr. Boom for 190.


Servant of Sevine (3 second sample)
2/7 22:17:22.079 You fail to cast Kill Command: You can't do that yet.
2/7 22:17:22.079 Concussive Shot fades from Servant of Sevine.
2/7 22:17:22.126 You fail to cast Kill Command: You can't do that yet.
2/7 22:17:22.126 Your Steady Shot hits Servant of Sevine for 508.
2/7 22:17:22.126 Servant of Sevine attacks. Baconbit blocks.
2/7 22:17:22.204 You fail to cast Kill Command: You can't do that yet.
2/7 22:17:22.266 You fail to cast Kill Command: You can't do that yet.
2/7 22:17:22.360 You fail to cast Kill Command: You can't do that yet.
2/7 22:17:22.422 You fail to cast Kill Command: You can't do that yet.
2/7 22:17:22.501 You fail to cast Kill Command: You can't do that yet.
2/7 22:17:22.547 Your Auto Shot hits Servant of Sevine for 236.
2/7 22:17:22.579 You fail to cast Kill Command: You can't do that yet.
2/7 22:17:22.657 You fail to cast Kill Command: You can't do that yet.
2/7 22:17:22.719 You fail to cast Kill Command: You can't do that yet.
2/7 22:17:22.813 You fail to cast Kill Command: You can't do that yet.
2/7 22:17:22.876 You fail to cast Kill Command: You can't do that yet.
2/7 22:17:22.922 Baconbit hits Servant of Sevine for 128.
2/7 22:17:22.954 You fail to cast Kill Command: You can't do that yet.
2/7 22:17:23.032 You fail to cast Kill Command: You can't do that yet.
2/7 22:17:23.110 You fail to cast Kill Command: You can't do that yet.
2/7 22:17:23.172 You fail to cast Kill Command: You can't do that yet.
2/7 22:17:23.266 You fail to cast Kill Command: You can't do that yet.
2/7 22:17:23.329 You fail to cast Kill Command: You can't do that yet.
2/7 22:17:23.360 Baconbit 's Gore crits Servant of Sevine for 105.
2/7 22:17:23.407 You fail to cast Kill Command: You can't do that yet.
2/7 22:17:23.469 You fail to cast Kill Command: You can't do that yet.
2/7 22:17:23.563 You fail to cast Kill Command: You can't do that yet.
2/7 22:17:23.626 You fail to cast Kill Command: You can't do that yet.
2/7 22:17:23.704 You fail to cast Kill Command: You can't do that yet.
2/7 22:17:23.735 Baconbit casts Growl on Servant of Sevine.
2/7 22:17:23.751 Your Steady Shot crits Servant of Sevine for 873.
2/7 22:17:23.782 You fail to cast Kill Command: You can't do that yet.
2/7 22:17:23.860 You fail to cast Kill Command: You can't do that yet.
2/7 22:17:23.907 Baconbit hits Servant of Sevine for 131.
2/7 22:17:23.922 You fail to cast Kill Command: You can't do that yet.
2/7 22:17:24.016 You fail to cast Kill Command: You can't do that yet.
2/7 22:17:24.079 You fail to cast Kill Command: You can't do that yet.
2/7 22:17:24.141 You fail to cast Kill Command: You can't do that yet.
2/7 22:17:24.235 You fail to cast Kill Command: You can't do that yet.
2/7 22:17:24.297 You fail to cast Kill Command: You can't do that yet.
2/7 22:17:24.376 You fail to cast Kill Command: You can't do that yet.
2/7 22:17:24.454 You fail to cast Kill Command: You can't do that yet.
2/7 22:17:24.532 You fail to cast Kill Command: You can't do that yet.
2/7 22:17:24.563 Baconbit gains 50 Focus from Go for the Throat.
2/7 22:17:24.563 Baconbit 's Gore hits Servant of Sevine for 98.
2/7 22:17:24.688 You fail to perform Steady Shot: Not yet recovered.
2/7 22:17:24.751 You fail to perform Steady Shot: Not yet recovered.
2/7 22:17:24.797 You fail to cast Kill Command: Another action is in progress.
2/7 22:17:24.829 You fail to cast Kill Command: Not yet recovered.
2/7 22:17:24.829 You fail to perform Steady Shot: Not yet recovered.
2/7 22:17:24.907 You fail to cast Kill Command: Not yet recovered.
2/7 22:17:24.907 You fail to perform Steady Shot: Not yet recovered.
2/7 22:17:24.938 Baconbit hits Servant of Sevine for 131.
2/7 22:17:24.985 You fail to cast Kill Command: Not yet recovered.


It would appear it is the failure of the Kill Command that is stopping the auto shots and it may be that using the script to spam the macro so quickly actually magnified the problem. I can provide the raw combat logs to anyone that would like to see them.

The factor that affects this ratio the most, is the number and nature of the haste effects that you get in a fight. It doesn't get any simpler than this.
Take me as an example, when my attack speed drops below 1.85 (rough estimate), it auto-converts to 1:1. This might be a flat 1.85 for anyone (about that much) or a 1,5 + latency (as i usually play with 220-280ms), i don't know that.

The only thing that i and the rest can tell you is some general remarks, unless someone spends days testing taking into account a great deal of factors and what happens on different values of these factors. Better try for yourself and see, this has been my opinion since ever.

Fact1: This /cast steady-auto spamming is not a rotation, it's not even a sequence. It's a free style spam issuing of commands to fire steady and auto. So whichever is ready at any given moment that these commands are being issued, it fires.

Fact2: If your average steady does more damage than your average auto, if you use a heavy hitting 3.0 speed weapon (like Archimonde's), if you use the Ashtongue talisman of swiftness trinket, if you can afford the extra mana, then in my opinion it's better to follow this style of playing and try to be as often hasted as possible [exactly like you would do with the classic strict 1:1 style (concerning trying to be hasted as often as possible), haste is our friend (i am talking about haste effects and not haste gear)].

Fact3: What we (at least me) are trying to do is like dish out a bit more damage by favoring steady over auto, get more procs out of our Ashtongue trinket and try to be hasted as often as possible, because nothing can beat an about 1,5 speed 1:1 style in my opinion. Note that i have ceased to accept the 0,5sec secret auto cast time as valid, after the recent changes. At least this is what i observe to happen with me and with the play style i use at the moment, i don't care if the 0,5 cast time applies in other cases, it doesn't apply to the play style i describe above.

It's not like discovering electricity, it doesn't need much thought or researching in my opinion. Of course i may be wrong.

In the log you mention, you have 120-69 (it's not a 87-49 ike you mention, you didn't include Nb of crits), meaning a 1,74:1 ratio. The haste effects you had were 4x QS and 2x Rapid Fire.

Look at my log (click me), i have 110-81, meaning a 1,36:1 ratio.
A lot closer to 1:1 due to 6xQS, 4x Drums of Battle, 3x Haste 2x Berserking, 1x Rapid Fire and 1x Bloodlust.

In a few words, this new thing that we do is a variation of the strict 1:1, converting it to a free style non-strict 1.x:1, favoring steady shot and thus using it more than auto shot and trying to be hasted for the max possible duration, so as to use a fast and tight hasted 1:1 for as much as possible. And during being unhasted, we maintain a high amount of shots per sec (should be relatively close to 1/sec) trying to get more procs of our Ashtongue trinket and more DPS, due to favoring the harder hitting steady.

It might seem strange that while we don't want to use the classic 1:1 steady-auto style, we actually try to be hasted for the max possible amount of time and slide to a hasted 1:1 for the max duration possible. But it's not strange, as in my opinion it is like that (when the situtation concerning weapon speed, trinket use, steady dmg, is like i state above):

strict 1:1 hasted style > 1.x:1 new free style > strict 1:1 classic unhasted style

YES! I reported on this a week ago in two posts. Let me add that in these tests I used a Logitech MX Revolution mouse with unlocked wheel mapped to the macro for very fast spamming


http://elitistjerks.com/f31/t11420-h...ry_bible/p111/

http://elitistjerks.com/620136-post397.html

DPS may still increase with 2:1 over 1:1, not sure of that. But 3:2 with KC viable would be optimal. WTB macro that does this.

So would you be able to run the same tests again without the KC in the macro? Is it possible that removing KC would up DPS even further (even over the loss of KC damage)?

Yes, I can try again with the pet attacking but Kill Command removed but I wan't really testing DPS, just trying to see if KC is stopping Auto shots (which appears to be the case). Aggro may be a problem however. I was about 20% over my pet at the end of each mana bar when fighting the Servant of Sevine but the pet should be able to hold the mob long enough to get a good data set.

I would also like to try it using a /castrandom for Kill Command to see if that removes the You fail to cast Kill Command: You can't do that yet. which may clear up the problem.

Considering your KC is hindering auto shots in some cases I would automatically assume that removing its use would increase DPS since #1 - autoshots occur much more often than every 6 seconds and #2 - KC crits sometimes don't even exceed the damage of 1 non-crit autoshot.

I also need to test this firing the macro at 2 or 3 times a second rather than 20 times a second to find out if the speed I was sending the requests was magnifying the problem.