Hunter Spreadsheets -- In development - Page 93

Lactose · 02/06/08, 12:55 PM

1:1 priority is having 1 special between each Auto Shot, but giving e.g. Arcane Shot priority over Steady Shot. So, if Arcane Shot is ready, you would use that instead of Steady Shot.

In most cases, this leads to higher DPS (due to Arcane Shot dealing more damage than Steady Shot on average). It does, however, also increase mana usage.

wyldbill · 02/06/08, 1:24 PM

Originally Posted by Cheeky

In reality all the new macro results in is a Steady Shot spam. Most of it is just garbage, but what it tries to do is cast Steady Shot as often as possible, and let Auto Shots fire when they can in between chains. A lot of people see the pattern Auto, Steady, Steady, Auto, Steady (repeat), yielding 3 Steady Shots for every 2 Auto Shots.

In pouring over logs I think this only really works because latency isn't constant, and anytime it increases you have a greater chance of getting an Auto Shot through. The GCD on the client prevents lowering latency spikes from providing much of an effect.

I can generate more data (and share it) if you'd like, but I'm seeing the same thing. A guy on the official-wow hunter forums tried to insist that this is better DPS but it appears to be 100% steady shot spam and auto shots only when the user fails to spam it hard enough or, as you say, latency intervenes.

With low latency and a high rate of spam, this macro:

/cast !Auto Shot
/cast [target=pettarget,exists] Kill Command
/cast Steady Shot

Totally under-performs the sequence of Steady,!Auto:

/castsequence reset=2/combat Steady Shot,!Auto Shot
/cast [target=pettarget,exists] Kill Command

With regards to sharing more data, if it's even needed at this point, I can offer a couple of things:

- I am currently 41/20/0 for the week
- I have the [Bristleblitz Striker]
- I also happen to have the [Barrel-Blade Longrifle]

If there's more testing to do, please let me know if I can be of help; I'm happy to make a visit to Dr. Boom.

Glaurong · 02/06/08, 3:05 PM

Originally Posted by wyldbill

I can generate more data (and share it) if you'd like, but I'm seeing the same thing. A guy on the official-wow hunter forums tried to insist that this is better DPS but it appears to be 100% steady shot spam and auto shots only when the user fails to spam it hard enough or, as you say, latency intervenes.

With low latency and a high rate of spam, this macro:

/cast !Auto Shot
/cast [target=pettarget,exists] Kill Command
/cast Steady Shot

Totally under-performs the sequence of Steady,!Auto:

/castsequence reset=2/combat Steady Shot,!Auto Shot
/cast [target=pettarget,exists] Kill Command

With regards to sharing more data, if it's even needed at this point, I can offer a couple of things:

- I am currently 41/20/0 for the week
- I have the [Bristleblitz Striker]
- I also happen to have the [Barrel-Blade Longrifle]

If there's more testing to do, please let me know if I can be of help; I'm happy to make a visit to Dr. Boom.

It all depends on your hasted weapon speed. For the macro to really shine your steady shot has to finish casting in the 0.5s auto shot window, or pretty well near it.

In my case it looks like I'm able to tune my weapon speed so I fire about 1.16 Steady Shots per Auto. I've been able to increase my rate of fire to 1.25 shots per second (up from 1.1).

Also a larger proportion of my shots are steady shots, which overall do much more damage (T6) and increase the value of my Ashtongue Talisman.

Guran · 02/06/08, 8:09 PM

I was just looking through the calculations tab and it shows that the 'Proc Duration' on [Band of the Eternal Champion] is 15. Tooltip shows it as being 10 seconds. Was wondering if the 15 is referring to something else, or just a mistake?

Midnight · 02/07/08, 5:33 AM

Originally Posted by Cheeky

I haven't done testing myself, but going with 0/5 Serpent's Swiftness and no quiver is the next logical step. In PMs Lactose suggested the range to mob (i.e. flight time) may be being applied to one shot and not the other, this would also complicate things, as well as make it completely un-modelable.

I've seen a little of the 2.4 combat log changes, but I don't remember hearing if the timestamps will all be server side (which is what we'll need.)

I did some testing yesterday, but didn´t have the time to look closer at the logs yet.
What I did was buying 1000 cheap Arrows/Bullets. I wrote a very simple macro.

/cast !Auto Shot
/cast Steady Shot

I then proceeded to spam this macro at Dr. Boom until either he died or I run oom. I repeated this until I´ve used up all my ammo so I should have a sample size of exactly 1000 shots. I did this with a 3.0 weapon as well as with a 2.6 weapon both with and without quiver haste. I´m planning on doing the same again with 5/5 SS. I used my G15 keyboard to spam the macro in 50ms intervals. My latency should have always been well below 100ms on an average 50ms too.

I´ll post the results as well as the logs here as soon as I´m done with my testing.

Quarath · 02/07/08, 6:30 AM

Would it be possible to add one more list to the spreadsheet which would show table similar to Shadowpanthers rogue armor chart (http://shadowpanther.net/armor.htm)?
It should be pretty easy considering you got all items in the sheet already...it would be even better then then the Shadowpanthers one, because you can sort the armor chart (based on the "weigth" of each attribute) each time you change gear.

Vasilii · 02/07/08, 12:56 PM

Hello,

When I'm trying to use the 1:1.X Option in the spreadsheet for my Survival 1:1.5 (both arcane & multi) rotation the behavior is strange. It starts out as a 1:1.5 but then in places it will use 2 sequences of Auto/Steady in a row without weaving in a multi/arcane. The result is the rotation comes out to be a 1:1.4 or something like that and I have to manually correct the mistakes.

Is this behavior intended or is there something I am overlooking? I am using version 42.

Cheeky · 02/07/08, 1:47 PM

Originally Posted by Vasilii

Hello,

When I'm trying to use the 1:1.X Option in the spreadsheet for my Survival 1:1.5 (both arcane & multi) rotation the behavior is strange. It starts out as a 1:1.5 but then in places it will use 2 sequences of Auto/Steady in a row without weaving in a multi/arcane. The result is the rotation comes out to be a 1:1.4 or something like that and I have to manually correct the mistakes.

Is this behavior intended or is there something I am overlooking? I am using version 42.

If you look at the cooldown-readiness of the Arcane/Multi shots is it possible that using them would lead to clipping? The rotation builder for 1:1.X attempts to avoid clipping issues as much as possible.

Vasilii · 02/07/08, 1:55 PM

Originally Posted by Cheeky

If you look at the cooldown-readiness of the Arcane/Multi shots is it possible that using them would lead to clipping? The rotation builder for 1:1.X attempts to avoid clipping issues as much as possible.

Yes you are exactly right, keeping up 1:1.5 is impossible without clipping. Cycle Time increases when I manually put it in but DPS jumps by a considerable amount.

Thanks for the clarification.

Cheeky · 02/07/08, 2:04 PM

Originally Posted by Vasilii

Yes you are exactly right, keeping up 1:1.5 is impossible without clipping. Cycle Time increases when I manually put it in but DPS jumps by a considerable amount.

Thanks for the clarification.

No problem. I didn't build in enough intelligence to the rotation-generation code to weigh clip time vs. DPS increase. Always feel free to hand build rotations when you think you have a better pattern.

Khassandra · 02/07/08, 2:33 PM

FYI, raptors have been able to use Dash for awhile now, but the spreadsheet lists it as wrong family.

Sympa · 02/07/08, 4:50 PM

Originally Posted by Khassandra

FYI, raptors have been able to use Dash for awhile now, but the spreadsheet lists it as wrong family.

As it doesn't affect DPS I hardly see this as a needed fix.

• Intermission · 02/07/08, 5:51 PM

Once again to Cheeky (and whoever else helps him), this spreadsheet is amazing.

I was using the spreadsheet this morning at work for a while, and thought of a couple things that might be handy in future versions. I dont know how hard/easy this stuff is, just throwing the ideas out in the open incase they didnt cross your mind!

1) On the gear selection tab, have a cell next to each item that shows that particular items 'worth' in dps. Just something simple like:

worth = (total dps with the item equipped) minus (total dps without item equipped).

Sure its uses are a little limited, but I think it would be interesting seeing how different slots worth varies. And also for comparing rings/trinkets on the fly.

2) When I make gear changes and compare the hunter/total dps, it would be great to be able to undo and redo (ctrl-z ctrl-shift-z). Maybe it's just my version of excel (2007), but I have trouble undoing changes to gear tabs.

3) Now this is just pure laziness on my part: how hard is it to have auto-complete for typing in gear slots? The style where the dropdown list pops down and selects the closest thing to what you're typing. Scrolling up and down from Band of Eternal Champion to Stormrage Ring/Signet Ring of Primal to compare dps with different hit values ftl! This situation would also be nice with the undo/redo feature. Again, this might just be an Excel version issue (or a user issue).

4) The spreadsheet needs to make me a coffee in the morning and bring me drinks to my PC while raiding.

Ebonleaf · 02/07/08, 6:42 PM

Hi Cheeky and Lactose,

I've been a long time reader on this thread. The spreadsheet is amazing. Keep up the great work! I did have a question. From version 40 to 42 somehow i lost, misplaced, however you'd like to call it.. about 50 overall DPS. I have everything imported properly. I checked all my settings, and re-checked them. I have my target set to Gruul most times for max armor and resilience. Feel free to check my armory profile. I'm just wondering if the dps loss was purely from the 2 roll change or if i missed something new?

Tsook · 02/07/08, 6:49 PM

If I had to guess I'd say the two-roll change (since you're below hit cap, at least on armory) is the main reason. Also, pet FI uptime decreased across the board in these versions because of that bug fix.