Originally Posted by Kisko
I figured that Redcape weights are for naked toon and then I asked myself - why would I use naked weights to make gear/enchants/etc decisions for a far from naked ret paladin?
|
I would recommend re-examining Redcape's spreadsheet. His stat weights are based on the values input by default (when you download) or when you personally change the settings (Gear or Talents, Buffs, Enchants Tabs) and then rerun the simulation.
My understanding is that his default values are for vaguely BiS T11 gear. Thus the stat weights are produced based on this information - not a naked toon. Rather than force Hit/Exp to zero when over cap, he has them turn red (I work with some colourblind folks, so realize this may not be immediately noticeable). His mouseover tooltips even explain this fact.
Also, be very careful where you are "adding 300 points to different ratings." If you add in the "Testing" fields it does not re-run the simulation. As such numbers for Haste will be incorrect, while other stats (being linear) do display properly. The Testing value for Haste is only reducing CS CD, Spell GCD, and swingtimer - it is not updating procs (more AoW from faster swing, more DP from more CS, etc) and the collisions that occur. More Haste is not always a gain, while more of anything else (when below caps in the case of Hit/Exp) is always a gain.
In order to accurately model an increase in Haste in Redcape's spreadsheet, your best solution is to go to the Gear tab, find an item with no Haste, add a value of Haste and press "Make Rotation."
Example: I add 20 Haste to his default and see 8 DPS increase (false value). Press Make Rotation and it becomes 47 (true value). Change to 50 Haste and Make Rotation - suddenly I only gain 36 DPS.
Wait, 50 Haste give 36 DPS, while 20 gave 47? Going from 20 extra to 50 extra was a loss of 11 DPS? Yep, that's the type of results I'd expect from his simulation. This is why I always tried to average out Haste across a broad range to give is a reasonable value.