In the item DB, is there a tag that could be incorporated into the filters that would make what your currently equipping show up? So you can see what ie the best raid drop is in a slot, and see it compared to what your actually wearing, regardless of where the item your wearing came from.

Thanks for fixing Rawr.Ret to level 80!

Librams aren't all in. I have been editing librams to give an approx. value.

1. and 2., don't know, Ermad?

3. 2.2 will not include tBC items, for this very reason.

4. Yeah, use the Set Default Gemmings feature in the tools menu, to choose 1+ gemming styles that you prefer, and check the box to remove all others.

I am getting an "overflow error" regularly. It happens once in a while when I am picking enchants, as well as sometimes when I attempt to edit the gems. It also happens whenever I try to select a piece of gear in the enhancement shaman model. Also the coloured bars rating the gear do not show in the enhancement or rogue model. Here is a copy of the error, I get this error on both of my computers.

************** Exception Text **************
System.OverflowException: Overflow error.
at System.Drawing.Graphics.CheckErrorStatus(Int32 status)
at System.Drawing.Graphics.FillRectangle(Brush brush, Int32 x, Int32 y, Int32 width, Int32 height)
at System.Drawing.Graphics.FillRectangle(Brush brush, Rectangle rect)
at Rawr.ItemSelectorItem.get_PrerenderedImage()
at Rawr.ItemSelectorItem.OnPaint(PaintEventArgs e)
at System.Windows.Forms.Control.PaintWithErrorHandling(PaintEventArgs e, Int16 layer, Boolean disposeEventArgs)
at System.Windows.Forms.Control.WmPaint(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
at System.Windows.Forms.ContainerControl.WndProc(Message& m)
at System.Windows.Forms.UserControl.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

I know exceptionally little about how this all works, just thought I would bring it up. I couldn't find mention of Overflow errors in any other post in this thread.

And Rawr is awesome thanks Astrylian and everyone else for putting in the work to make this tool.

That's for the report, I'll look into it.

Also, there's no Rogue model currently (old one hasn't been updated for 3.0/80 yet). The Enhance model will work as soon as you select weapons, I believe.

1. Yes they are, you could have just compared the stats in Rawr to in game stats to see if they matched.
2. Yes, I will add something for Block Rating and Defense.
3. No way to delete all TBC items currently.
4. Just set the Default Gems for all items, and check delete others checkbox.

The 3.0.4 mode is only for Armor changes. FAP removal isn't considered yet. For weapons to show up in Rawr.Bear, they need to have at least some amount of attack power on them (I think it's like 280 or something, whatever the lowest blue feral staff from tBC has, I think). Just edit Inevitable Defeat, and give it 2084 attack power. (That's how much a same-ilvl feral weapon has)

[Tankadin] Block Rating

Block rating does not seem to convert correctly to block percent. Simply putting in Lavanthor's Talisman to a naked tankadin gives 88.51% block.

Block Rating is incorrectly giving 100x more then it should, will be fixed for next version.

Sorry for the bugs, been busy playing at 80, and haven't been prot since WotLK yet.

V2.1.3 Druid Tree model: It seems to be doubling my haste and crit values under the Basic Stats section. My health and mana are also incorrect. Mana is 2k over what I actually have and health is under about 2k what I actually have. Nothing in the buffs section is checked.

any news about warlock update?

thank you!! great job

Does 3.0.4 mode ignore the armor on weapons? Or do I need to set that to 0 also?

No, it doesn't ignore armor on weapons, nor should it. The armor on weapons will remain, it just won't get multiplied.

Any numbers on Berserking for Cats? I just got the VH staff and I'd like to get the best enchant on it but am not sure on how it compares to Massacre. Could use an advice in the least, if exact number crunching isn't possible yet (like on Mongoose)

I don't have any reliable data on Berserking, yet. Going just on wowhead comments on its proc rate (ie, take with a huge grain of salt), it has the same proc rate as Mongoose. That would make the 3 enchants provide, in optimal Naxx25 gear, about... Massacre=59, Mongoose=60, Berserking=76. Again, those are really rough numbers, based on rumors and here-say, so take them for what you will.

That said, even if Berserking is better, I wouldn't put it on Staff of Trickery. It costs 4-5k gold in mats on most servers, whereas Mongoose costs like 200g. Unless you think you'll never do Naxx10 or 25, I wouldn't drop that kind of gold on the VH staff, personally.

I know a few people have gotten close to this idea, but I don't think it's been suggested outright yet. Can/should Rawr.Bear and other tanking modules have a cap for Survivability? I know it's pretty well established that you need X amount of health and Y amount of damage reduction for a particular encounter, after which you should stack mitigation (and threat/dps) because more survivability isn't needed unless your healers die / fall asleep. The current method of deciding you have enough survivability and switching to Mitigation based sorting works, but throwing a cap on total Survivability score would make it more intuitive, allow Overall to sort by both Mitigation and Threat scores, and still accurately penalize the score of an item that would reduce you below your target Survivability.

It would vary by fight like boss armor / fight time / etc, of course, so it'd be an entry in the Options tab, and probably default to turned off. It could have a pull down with named defaults like Threat has, but based on either encounter or raid level (X for Heroics, Y for 10-man Naxx, Z for 25-man Naxx, and onward). I think it would be a pretty useful option to have.

Actually, yes, that's planned for 2.2.

Not a hard cap, though. Even if you've got 40k health, 5k more health is still better than 0.1% dodge, for an extreme example. I'm not sure of the exact calculations yet, but I'm going to include an option to turn on and define a soft cap for Survivability, where the relative value of survivability drops gradually after you pass the cap. Again, this will be optional, for all you 'never get enough stamz zomg!' people, and I'm not sure of exactly how it will be implemented yet, so your feedback is welcome on this.

I'd propose that you do something like a diminishing returns value with a soft and hard cap. Say, set the soft cap to 40k and the hard cap to 45k (user-changeable) and that each point above 40k got worse and worse until hitting the 45k cap, at which point it does become useless.

I'd also strongly recommend this be the default no matter what you end up doing, so that people using Rawr don't think that it's recommending huge stamina right out of the box.

Agreed. As is, I think Rawr.Bear values items quite well, assuming you're fighting challenging content... there just happens to be no such content available at the moment.

Awesome, I'm looking forward to it. The soft cap does sound even better than a hard cap, too, since additional health isn't entirely useless, just unlikely to come into play in most situations.

I originally had the idea of a health cap, which would let armor continue to provide both Survivability and Mitigation score (though the Survivability contribution would be based on the capped health), retaining most of its value even after you had "enough" health. But the survivability contribution of armor really isn't any more valuable than the survivability contribution of health after the cap, it's used entirely for mitigation, so yeah, a survivability cap is the way to go. Plus, the amount of health necessary for a worst case scenario does vary based on your damage reduction (the thought brings to mind a mage trying to tank Gruul).

I can agree with kalbear's suggestion on the default state. It's a balance between two slightly confusing situations ("Why are the Survivability values of all 20 of these gear pieces exactly the same?" vs "I stacked 60,000 health because Rawr kept rating the stamina items the highest, but our healers say I'm the hardest tank in the raid to heal"), but I'm all for defaulting to the more correct of the two.

Do you think there needs to be a hard cap? I was thinking of just a soft cap, and it declining in value continuously after that. The difference between 60k and 61k health is really really minuscule, but it's not 0, after all.

That'd be the easiest to understand/configure for most users, I think too. Just a slider where they can set what 'enough' seems to be for them, for the content they're doing, with their healers. I figure the default will be... 140k Survivability. Does that sound right? That would be 35,000 health, 41,939 armor. Or 39,691 health, 35,000 armor. Or somewhere in-between.