Haste Effects will *reduce* our DPS.
by Azaranth | 02/03/2007 16:00:41![]() This is my chief complaint with the Hidden Windfury Cooldown Mechanic. I don't mind that the offhand would share the same timer, I'll use flametongue or something. At least the spell damage on my t4 gear will do something now. My complaint is that the mechanic is seriously flawed, and makes buffing effects actually detrimental. This affects all shaman who use windfury, not just the Enhancement shaman. I'll explain. First, let me establish how windfury scales with weapon speed. If not for the 3.0 second cooldown, Windfury would be in identical dps increase across all weapon speeds. However, because of the cooldown, windfury favors slower weapons. The rule of thumb was that "fast weapons would have lots of small procs, while big weapons would have less, large procs". This is not true because the "lots of small procs" that a fast weapon should have are limited by the Hidden Windfury Cooldown Mechanic. Let's assume that the Hidden Windfury Cooldown Mechanic is exactly a 3.00 second cooldown. In this scenario, I'll hypothetically use a 1.5 speed weapon. 1.5 speed weapon Time - Effect 0.00 - Weapon Swing - Windfury Proc 1.50 - Weapon Swing - Windfury cannot proc. 3.00 - Weapon Swing - Chance for Windfury Proc Now look at the same situation with a 3.0 speed weapon. 3.0 speed weapon Time - Effect 0.00 - Weapon Swing - Windfury Proc 3.00 - Weapon Swing - Chance for Windfury Proc Now, that's add +1 haste rating to the equation. 2.99 speed weapon Time - Effect 0.00 - Weapon Swing - Windfury Proc 2.99 - Weapon Swing - Windfury Cannot Proc 5.98 - Weapon Swing - Chance for Windfury Proc See what happened? The 1 point of haste rating turned the 3.0 second windfury cooldown into a 5.98 second windfury cooldown! Let me attach some numbers, to make this seem more quantative. Lets use a 1.5 speed weapon that hits for 250, and has Windfury Attacks for 400. We'll use a 3.0 speed weapon of the same dps, that hits for 500 and has Windfury Attacks for 800. 1.5 speed weapon Time - Effect 0.00 - Weapon Swing - 250, 400, 400 1.50 - Weapon Swing - 250 3.00 - Weapon Swing - 250, 400, 400 4.50 - Weapon Swing - 250 6.00 - Weapon Swing - 250, 400, 400 Total - 3650 3.0 speed weapon Time - Effect 0.00 - Weapon Swing - 500, 800, 800 3.00 - Weapon Swing - 500, 800, 800 6.00 - Weapon Swing - 500, 800, 800 Total - 6300 2.99 speed weapon Time - Effect 0.00 - Weapon Swing - 500, 800, 800 2.99 - Weapon Swing - 500 5.98 - Weapon Swing - 500, 800, 800 6.00 - Technically, the time passed between 5.98 and 6.00 is a percentage of a swing cooldown, which is approx 3 damage. (0.006 * 500 = 3) Total - 4703 See what a dramatic difference that is? 1 point of haste rating can significantly lower my dps. Keep in mind that many shaman pay talent points for an innate haste effect: Flurry, which could be actually lowering the shamans DPS, rather than improving it. For simplicity of math, I assumed 100% windfury procs. Obviously, Windfury only has a 20% proc rate, so the actual dps lost by 1 haste rating would be less pronounced than what you see here. Nonetheless, the loss would be significant, and I feel that this should be a major point of investigation by the development team. Haste is one of the most expensive stats in terms of itemization, and obviously it is a mechanic that is supposed to increase damage output, not reduce it. Coupled with the fact that Flurry procs could actually reduce my dps, rather than increasing it, this issue should be addressed as quickly as possible. Honestly, all we really would like to see is a blue response saying that this issue has been noted, and will be looked into. I'm fairly sure this is just an unintended side effect of the implementation of the Hidden Windfury Cooldown Mechanic. Please keep this thread bumped so Tseric and other CM's can add it to their meeting notes. Cheers! Az |
by Tseric | 02/03/2007 18:05:15![]() Let me just say outright, I would love for you to prove me wrong on this contention. I see an issue with a core statement made in the OP for a couple reasons.
If you mean that windfury adds the same amount of damage for each extra attack, that is one thing. To say the potential damage output of a fast weapon from a slow weapon with windfury is another. The OP focuses on how the 3 second cooldown affects proc'ing on slow and fast weapons, but doesn't really deal with what happens if the cooldown isn't there. Especially in a dual wield situation. Now granted, I haven't crunched numbers on this either, but I'm interested to see simple math where the max damage from a repeated crit from both a slow 2 hander and dual wield, fast main and off hand compare within a 6 second timeframe. Let's take as a given that all weapons proc on strike. That's what unmanagable burst damage is all about. The fast, dual wield weapons are procing every strike in 6 seconds, the slow 2 hander procs every strike in 6 seconds. How do these compare? Does that support everything that follows in the original argument? I ask, because I don't know what the hot enhancement Shaman weapons are, fast or slow, otherwise I'd do some math myself. :P |
by Tseric | 02/03/2007 18:12:55![]()
Please do. I am interested. |
by Tseric | 02/03/2007 18:25:29![]()
Thank you for getting that. I wanted to throw out some arbitrary numbers like that, but I felt it would be poor form in my position. ;) I still feel this doesn't address dual wielding and the procs from that, in a given timeline. You're still dealing with single weapons on a single timeframe. It doesn't touch on having dual-wielding weapons proc one after the other, or does it? I mean, situational line-of-sight is just another factor you could throw in, but at the base math of it, does slow hand proc'ing match dual wield proc'ing? |
by Tseric | 02/03/2007 18:27:56![]() Ok, I guess I'm just looking at it from the context of yesterday, where enhancement dual wield Shaman were the ones affected by this particular change more than anyone else. Just trying to establish first cause before moving into how spell haste 'nerfs' the whole business. |
by Tseric | 02/03/2007 19:52:07![]()
Sometimes just inciting a discussion and seeing the results later can make for a good thread. Flagging a thread blue has a lot of wierd, psychological incentives and this thread is full of good material for digestion. Whether it all goes as direct feedback is rather secondary. But, I might just forward this one in full. I do think the OP has an interesting point, even though the devs might consider it intended. |
by Tseric | 02/03/2007 19:58:01![]()
Word. See you there. :P |


Recent Blizzard Announcements