This project is read-only.

Hunter Spreadsheet and Haste

Topics: Retired
Jun 18, 2008 at 4:52 PM
First of all I want to say great job so far on the Hunter portion of Rawr.  Just a few things.

Right now the module is set that when a 3:2 rotation is selected it changes on the fly to a 1:1 rotation when aspect of the hawk procs.  This is actually very cool.

The issue with doing this is that it is not always accurate.  Depending on shot speed when hawk procs it might not lower attack speed enough for a 1:1 rotation to result.

I am not sure if this is possible but under normal ping conditions (200ms or less) most Hunters using the 3:2 macro will change to a 1:1 rotation when shot speed drops below 1.9 and the 3:2 macro will produce a 2:1 rotation when above 2.1 shot speed.  The sweet spot to actually gain a 3:2 rotation is between 1.9 and 2.1 attack speed.  2.0 is actually the shot speed to be aimming for.

My suggestion would be that when the option is selected that the player is going to be using the 3:2 shot macro that the hunter module detects shot speed to determine which shot rotation to model.  Right now when it detects an imp hawk proc it changes to a 1:1 rotation, how hard would it be instead of detected hawk procs for changing the rotation to use shot speed instead? 

A large number of survial spec hunters use the 3:2 macro to produce a 2:1 rotation that changes to a 3:2 rotation when under the effects of haste like imp hawk procs.  Also when using a very slow bow as beast spec with no haste, for example a 3.0 bow the 3:2 macro will produce a 2:1 shot ratio and not the 3:2 ratio that is being modeled right now.

For example when attack speed is less than 1.9 then a 1:1 steady to auto shot ratio is selected.
Or if attack speed is greater than 2.1 then the macro normally produces a 2:1 steady to auto shot ratio.
If attack speed is between 1.9 and 2.1 then the 3:2 macro actually produces a 3:2 steady to auto shot ratio.

A 2:1 rotation looks like:

Also remember that only auto shots can proc imp hawk.  So when using a 2:1 rotation because of shot speed, hawk will not proc as often.

For more information on how the 3:2 macro works in relation to shot speed please check out this thread:
Jun 18, 2008 at 5:27 PM
I just took the time to look at the source code and it seems like this is already being taken into account.  It is actually modeling a 2:1 rotation at 2.15 attack speed.  Very nice.
Jun 19, 2008 at 5:19 AM
Just to clarify for others that might be curious how the model works, there are currently 3 shot models: Auto Shot Only (obvious), 1:1, and 3:2.

1:1 is built on the assumption that you are hand weaving shots so that server side latency doesn't play into the dps as would happen with the cast sequence macro (unless that has changed).

3:2 is built on variations of the following

/cast !AutoShot
/cast SteadyShot

If you analyze what that is doing, its basically saying:

If you can cast an auto shot, do it,  then, either way, cast a steady shot, so that is how the 3:2 algorithm was designed, with that same basic logic (checking for GCD conditions and what not as well).  I wanted to make sure I didn't artificially force a 3:2 condition since thats not what the 3:2 macros that are flying around lately are really doing.

All of the shot rotation modes take into account the shots per second based on haste, weapon speed, etc.  Quick Shots is modeled as a percent uptime based on auto shot speed as well as how many points are in the talent and then applies the quick shots haste to the shot speed and gets its own run through the same simulation, for the very reasons you mention, you can't just apply a static haste buff, you have to treat that as a separate condition with its own variation on whats being fired when.  (DST will be modeled the same way eventually).  When I said (I'm assuming I said it somewhere) that the 3:2 model would start acting more like a 1:1 on Quick Shots proc, I more meant that the above macro would act like one when run through the simulation.  The model doesn't actually change the shot rotation algorithm used.

To your suggestion that the model suggest a shot rotation based on gear, this is something that is on the board for phase 2 of the model.  For phase one, I'm just trying to get all the moving parts in place with the calculations and output making sense to everyone. 

Definitely thank you for the feedback, keep it coming!!