Looking for some help. Everyone knows that the windfury cooldown is 3 seconds the same way that we all knew that Patchwerk's hateful strike was completely determined by who had the most health. Blizzard has stated that there is a cooldown on Windfury but they have never said it is 3 seconds and I have never seen definitive proof from anywhere that it is exactly 3 seconds.

Why does this matter? There is a point where haste starts to have a very detrimental effect on your dps and that is right when you get your weapon speed to half the cooldown duration. But if the cooldown is actually shorter then 3 seconds then that point changes. This also has a large effect on our simulator since without the correct cooldown the Sim is inaccurate.

Here is a combatlog entry from the Sarth3-10man we did over the weekend.

16:35'36.750 Rouncer Windfury Attack hits Tenebron #9 for 1748 Physical.
16:35'36.750 Rouncer Windfury Attack hits Tenebron #9 for 3859 Physical. (Critical)
16:35'39.625 Rouncer Windfury Attack hits Tenebron #9 for 3314 Physical. (Critical)
16:35'39.625 Rouncer Windfury Attack hits Tenebron #9 for 1621 Physical.

That's 2.875 seconds between Windfury Attacks.

This is meant to be a short thread focusing purely on the Windfury cooldown. I'm looking for people to help me accurately determine the real cooldown. Easiest way would seem to 2 very fast weapons both imbued with Windfury and the targeting dummy, add as much haste and haste procs as possible and run a /combatlog. Then go through the log and find the smallest interval between windfury attacks.

Take the smallest interval you can find and copy/paste it into a reply on this thread along with where you did the testing, what speed weapons were used, passive haste and any active haste procs. So the reply should look like this.

Any lag or high latency while testing will invalidate the results.

Only post results if you find an interval below 3 seconds. Feel free to state how much time you spent testing and the smallest interval you personally encountered since that will be useful for comparison data.

Wouldn't a more effective approach involve using weapons of different speeds and varying haste to see which swing times can give back to back windfury?

For example if you have 3.05 seconds between swings and see back to back windfury, but 2.95 seconds between swings doesn't, you can conclude that the cooldown is 3 seconds. While the combatlog is pretty inaccurate, the tooltip for weapon speed should give correct time between swings.


A more difficult problem is figuring out what the FT cooldown is...

Aren't you guys in Australia and dealing with 300ms latency on good days? Also isn't that blog using the previous combat log system not the current one which seems to include a lot more information from the server.

I'll addendum the post to ask people to include their average latency while testing to see if it plays a role.

It might be worthwhile to at least confirm your results in a no-haste situation, in case for some reason haste applies to the internal CD of WF even though it doesn't generally affect internal CDs.

I can help you with this

It's 0. There is no FT cooldown. Why would you think there is?

Flametongue...cooldown?

There is some sort of cooldown between Flametongue procs. If you use the same rank of Flametongue with weapons of matched speed you will lose Flametongue procs. However if you change one weapon's imbue so it is a different rank then you get all the procs even with match speeds. So there is some cooldown inherent in the imbue that only applies to each specific rank of the imbue.

Since the proc is reported separately in the /combatlog isn't it simpler to just look for the interval between procs? Since the cooldown is also enforced by the server it shouldn't allow procs to occur inside that cooldown period, right?

Hmm, yes. Go test it for yourself if you are too lazy to search for a "citation". Matched weapons with 2xFT (same ranks) and you will lose FT procs. Matched weapons with 2xFT different ranks and you won't lose any procs.

(e) http://elitistjerks.com/1041416-post1150.html is the most recent post on the topic. We had a huge discussion on it back when it was looking like FT/FT with fast/fast ("lightning knives" aka "Malan's Bane") would be the way to go for maximum dps and that was when the cooldown was noted for the first time.

Keep in mind that PPM mechanics never use to scale with haste either. And despite any evidence to date to support it, Blizzard has been telling us (for years now) that they want to take a look at the Windfury mechanics. So it may be possible that they have at least allowed the WF-CD to scale with haste.

The proc itself isn't reported in the combat log. There's nothing that says "Gained Windfury Weapon". The server regulates the cooldown on it based on when the attack occurred according to the client's claims or when the server thinks it should have happened (whichever is more applicable), so if you lagged in sending a Stormstrike to the server, then a white swing procced it on time, it could appear to your client as less than 3.0 seconds between procs.

Either way, given the amount of haste in the game, the exact timing of it should be provable based on frequency of procs with autoattacks. At the time the cooldown was discovered haste did not exist as an itemization stat, so we could only test it with available weapons, and it was clear the cooldown was greater than 2.9 seconds and less than 3.2.

Also, I find it hilarious that trying to cheese synchronized attacks to abuse Flurry ends up costing you Flametongue procs.

And they don't -- serverside, once the timestamps of the attacks that proc WF are lag-corrected. This does not imply in any way that the combat log results are accurate.