You can add it yourself with a temporary buff to the buffcache. It's easy enough; if you want the specific xml message me privately.

Ardent Defender reduces the amount of all damage that would take you below 35% health by 20%, thus effectively increasing stam's contribution to EH by a fair amount (and in turn making stam into a mitigation stat, interestingly enough). It's a crucial part of the equation for survival and mitigation both, but unfortunately I'm not enough of a math or programming whiz to be able to model it myself.

Using the T9 Raids, 25, Heroic settings in the options tab RAWR is optimizing me to a fully raid buffed health pool of only 52k. Am I understanding correctly that the optimizer assumes that 100% of incoming damage is physical?

Yes. You're welcome to bump the soft cap settings up, if you need more survivability.

I was wondering why the last version was showing me rare gems instead of epic so I grabbed this only to find the default for at least cat and bear is still rare.
I can add the epic ones I want but it never seems to save the ones I set so how do I make it epics by default?

Gemming Templates are in the GemmingTemplates.xml file; you can transfer that between versions if you like. Yeah, I need to update the default ones for Cat/Bear to be epic.

Rawr (v2.2.19) is showing me that Discerning Eye of the Beast is the BIS for me as destruction warlock. Is it true or somekind of bug??
My Armory

It's a wowhead bug, rawr is fine. On wowhead it shows 418 Spellpower for this trinket, while ingame it is 75(Not sure).
It's happening with all Heirloom items, on my bear model I got 2000+ armor on a leather heirloom item.
Right clicking on the item and refreshing it's data using wowarmory should fix it.

rawr can't find Boots of the Icy Floe. Is there anyway to insert into rawr database? How can I do it?

A) Tools > Edit Items > Add
B) It's probably already there. Check the ALL filter, to see if you have it filtered out.

I'm pretty sure there's something fishy going on with Rawr. Last night I finally got a long-overdue weapon upgrade (which put me horribly over hit cap), so I decided to fool around in Rawr/SEIC to help decide between glyphs (again). I typically look at Rawr's relative stat values to give me an idea of where I'm at for valuing haste vs. SP, but I found something pretty weird.

With Rawr's top 3 listed glyphs for my gear (LB, Lava, ToW) here are the relative stat values.


Same 3 glyphs, but using SEIC:

(note that the CL after LvB or the no CL rotations have crit being worth even less relative to haste)

The odd thing is that if I use the glyphs SEIC suggests in Rawr (FS, Lava, LB), then haste pops back up above crit (though not by much - haste = 2.54 DEP, crit = 2.19 DEP). The reason this is odd is because I would have thought that the glyph of Flame Shock would make crit a more valuable stat than the glyph of ToW or (especially) the glyph of Lava.

A possible explanation:
When I throw in the Glyph of Lava, crit shoots way up. With FS, it goes back down. When combining the glyph of Lava with the 4t9 set bonus, LvB becomes quite powerful. I'm guessing that the increased value from crit stems from Rawr not taking into account that it has a 100% crit chance from FS when calculating glyphs/relative stat values. The reason this problem probably exists is because of the 3.2.2 Flame Shock change, since the glyph seems to be the reason crit is devalued with the Flame Shock Glyph. Without the FS glyph, I suppose it's still calculating it with the LvB consuming the FS.

No, it's actually 13.75%

We can look into that, since your testing did get parries. It may be 13.8% or something.

Here is the screenshot. Sorry, interface is in Russian, but you can see numbers.


I doubt it can be any less than 14%. As far as I know Blizzard does not take into account minor changes in expertise rating when calculating parries. You need to increase expertise skill to see the difference. And 56 expertise skill would be -14%...

The Blizz Interface shows you rounded values, individual ratings points do still have value (you don't need to have several rating before gaining a point)

While the Blizz interface rounds inaccurately, the fact that Rawr says he is over the parry cap, and he got a parry, says that something's wrong. So it's not necessarily 14%, but it's more than 373.

I got parried with 407 expertise rating (+ 6 expertise from Talents) after ~1200 attacks. (Screenshot).
That means parry chance is at least (407/8.1974973675+6)/4 = 13,9123248155.

Didn't get a parry with 409 rating in ~1600 attacks. (Screenshot)

I'd suspect parry chance to be 14%, and that all sample sizes so far to test between 408 and 410 rating were just too small.

Had a weird thought while berating myself for low uptimes on debuffs on a recent WWS.

One of the knocks on Rawr generally is that it outputs a theoretical dps, with perfect uptimes and 100% dots all the time.

How hard would it be to implement the ability to analyze uptime variability for dots or buffs?

just a checkbox and a slider for one or many of the items you're typically looking at. Also drives home how much improvement can be gained just from improving rake or rip uptime.

(Just an idea so I can beat myself up some more for consistently coming in 1k under where Rawr places my dps)

Latest version actually has that; Lag Variance. That's how much buffer time you need between the ending of and the reapplication of de/buffs.

Being able to run 2 instances of Rawr at the same time would be extremely valuable for people like me with 2 specs and 2 sets of gear. Any plans in that direction?

This is already possible by extracting the program into two different locations on your pc. I have one placed the My Documents folder, then another on the Desktop. Simply create a shortcut to each, then you can pin both shortcuts to your start menu, and you're good to go. Each will run as two separate programs, yet will draw from the same saved profiles you create and store.

I wanted to use the latest Rawr version to play around with some gemming options but it showed completly skewed gear ratings (like T8,5 as BIS etc). After looking at the relative ratings I think I know why. Haste is valued with -17. For once haste should never be negative I think and I'm even far from the soft cap.
Here's a screenshot:


I used the default 0/13/58 talent build and a priority list (cod, immo, conf, cb, inc) and an armory-imported char. Anyone got an idea what might be causing this?
Here's the xml file: http://testfarm.net/aylirabugged.xml

Thanks.