This project is read-only.

Crit Rating in Optimize?

Topics: Rawr.Base.Optimizer
Apr 3, 2009 at 5:22 PM
After reading some of the things I didn't know in "Did you know?" and also the wish list thread, I started playing a little more with optimize and the newer features.  But when I went to pick a Crit Rating in Additional Requirements, I found it wasn't there.  An accident?  Or is it missing on purpose?  I realize it isn't on the main Optimize dropdown but I wouldn't mind being able to optimize my DPS Rating with a certain level of hit, haste and crit.
Apr 3, 2009 at 5:56 PM
Those sort of things are called Optimizable Stats, and it's up to the model to provide them to the Optimizer. Some models provide lots of optimizable stats, some don't. Let us know which model you're using, and what stats you'd like to see. It's not too difficult to add them, we just need to know which all stats you'd like to optimize/require for each model.

Keep in mind that these optimizable stats would be in terms of the stats that actually make a difference; ie, it'd be Crit %, not Crit Rating.
Apr 3, 2009 at 6:37 PM
Well, I'm using the Mage model.  I was looking at the two numbers displayed, Crit Rate (%) and the Crit Rating (numerical value).  Either way would be great to include.  The model provides the availability of Hit Rating and Haste Rating so I simply was looking at including Crit Rating because each of these would be the numeric value rather than the percentage that number evaluates into.  (If it was the Crit Rate or % then it might be a little confusing since the other numbers are the "Rating".)
Apr 3, 2009 at 7:32 PM
Well, I suppose it should be both, if not just the %s. Consider how if you're 1 crit rating under that crit rating requirement, it'd prioritize an item with 1 crit rating, over an item with 20 spirit, which would provide more crit %.

Kavan, thoughts?
Apr 3, 2009 at 9:59 PM
My thoughts are that I don't want to encourage optimization requirements that are misguided. If you have a reasonable use for a certain stat to be used as a constraint I'll consider adding it. Then again it doesn't hurt me to add them other than it clutters the list, so I might also be persuaded by popular demand. :)