Quote Originally Posted by JackFross View Post
Maybe you can point out where I'm going wrong? This is what I'm looking at (my character's current stats are plugged in).
http://puu.sh/jUCaO/a07a245d72.png
Autoattack DPS appears to be significantly too high to me. The rest is a bit hard to judge by eyeball since the spreadsheets I've been playing with have a different order of operations.

Quote Originally Posted by Dervy View Post
How are the DoTs tracked/clipped in your model Sunny? Yours looks extremely interesting.
Well, I've worked with two models to date. One of them is just EMX's inscrutable spreadsheet (updated for HW). The main things I'd like to "fix" about it in the near future (since hey, it's never quite done) are the skill speed DoT buff and adjusting the divisors for oGCD PPS to simulate that sometimes they are delayed slightly by GCDs.

The other, which I have not updated for HW at all, is a spreadsheet that lists every skill use for 8 minutes (arbitrarily chosen to cycle through BfB/IR evenly and give equal weight to opener vs. 100% HT/Disembowel uptime) and applies all buffs. It's pretty inflexible, but in part I found the technique useful for understanding monk opener optimization.

What I would like to build is plain old code (probably a Lisp of some sort because that's just how I roll). Spreadsheets are useful for dynamically experimenting with GCD sequences and visually diagnosing where DoTs fall off such, but these systems are a bit unwieldy when you know how all that works and just want answers. They're also unwieldy in other ways where static code is quite the opposite (commenting, revision control, writing functions to reuse math instead of making a whole new cell that has to be updated manually, testing hundreds of gearsets instantly...). Oh, and I'm just tired of copy/pasting numbers, heh.