Elitist Jerks - View Single Post - Enhance Shaman: The Collected Works of Theorycraft, Vol I

Ilmatar · 06/25/07, 3:51 PM

I am very interested in these numbers, but I have not (yet) done testing with them. I have no passive haste to test with and so none of my testing would be deterministic.

It is my theory that haste will have the additional, hidden, benifit of improving consistency of windfury hits (not between MH and OH, but in lessening the time that we spend waiting for WF to proc). The scenario that I think would test that theory is to get several sets of very low dps weapons (any dps value works, speed is the important factor), windfury on both, blasted lands. The sets of weapons should have speeds which corolate to weapon speeds reachable via haste. The weapons should be buffed with Windfury and non-SS/shock combat should be recorded. If possible, Flurry should be de-specced for this test (my character is poor. I have +6 str gems in some stuff, and other stuff still has +hit gems from when +hit was god). The data recorded from the test should be parsed, and presented such that it shows time-> and the state of the windfury cooldown. The total time spent in combat during the 3s WF cooldown (WF procs * 3) should be recorded. The total time spent in combat outside the 3s WF cooldown (combat time - wfcd cimte). And the average time spent waiting for Windfury to proc, outside the cooldown (sequential data parsing needed).

The test should be repeated with the various sets of weapons.

It seems like common sense, to me, that haste should have the additional, hidden, effect of reducing time spent waiting for WF to proc. Like you have said previously, though, testing is key. I'm one of those jerks who likes to theorycraft and hates to test, but honestly, testing in World of Warcraft, for me, is frustrating. I feel like I can't set up deterministic tests; can't test against mobs (easily and solo) that provide accurate simulation data; and with no knowledge of the net code in WoW we have no idea if event order is maintained, or if it is maintained with some sort of update-priority (where some events, of higher priority, will be sent in guaranteed order), so combat log examination is not (necessarily) representative of the order in which events took place on the server.

06/25/07, 3:51 PM	#114
Ilmatar Situational Shaman Ilmatar Draenei Shaman <Ad Naseam> Feathermoon	I am very interested in these numbers, but I have not (yet) done testing with them. I have no passive haste to test with and so none of my testing would be deterministic. It is my theory that haste will have the additional, hidden, benifit of improving consistency of windfury hits (not between MH and OH, but in lessening the time that we spend waiting for WF to proc). The scenario that I think would test that theory is to get several sets of very low dps weapons (any dps value works, speed is the important factor), windfury on both, blasted lands. The sets of weapons should have speeds which corolate to weapon speeds reachable via haste. The weapons should be buffed with Windfury and non-SS/shock combat should be recorded. If possible, Flurry should be de-specced for this test (my character is poor. I have +6 str gems in some stuff, and other stuff still has +hit gems from when +hit was god). The data recorded from the test should be parsed, and presented such that it shows time-> and the state of the windfury cooldown. The total time spent in combat during the 3s WF cooldown (WF procs * 3) should be recorded. The total time spent in combat outside the 3s WF cooldown (combat time - wfcd cimte). And the average time spent waiting for Windfury to proc, outside the cooldown (sequential data parsing needed). The test should be repeated with the various sets of weapons. It seems like common sense, to me, that haste should have the additional, hidden, effect of reducing time spent waiting for WF to proc. Like you have said previously, though, testing is key. I'm one of those jerks who likes to theorycraft and hates to test, but honestly, testing in World of Warcraft, for me, is frustrating. I feel like I can't set up deterministic tests; can't test against mobs (easily and solo) that provide accurate simulation data; and with no knowledge of the net code in WoW we have no idea if event order is maintained, or if it is maintained with some sort of update-priority (where some events, of higher priority, will be sent in guaranteed order), so combat log examination is not (necessarily) representative of the order in which events took place on the server.