Rawr (v2.3.23 released on 9/12) - Page 160

Astrylian · 09/08/09, 10:35 PM

I believe it was the new 3.2 Idol. In fact I don't believe there's anything in 2.2.15 that's 3.2.2-specific for Moonkin, though I very well may be wrong. Dopefish?

foxglove · 09/09/09, 1:46 AM

Under mono, the filter box is exceedingly tiny. I barely get the full name of any one dungeon at a time, and the scroll buttons scroll more than one line at a time. It's very difficult to use them. When I open the "Tier 9 raids" submenu, a left-right scrollbar appears and it becomes entirely impossible to read what I'm clicking on. Is there any XML file I could edit by hand to configure the filters?

Astrylian · 09/09/09, 1:56 AM

ItemFilter.xml

That said, anyone still struggling through Mono crap, send me an e-mail about beta testing Rawr3.

thedopefishlives · 09/09/09, 8:19 AM

Originally Posted by Astrylian

I believe it was the new 3.2 Idol. In fact I don't believe there's anything in 2.2.15 that's 3.2.2-specific for Moonkin, though I very well may be wrong. Dopefish?

Moonkin don't have any pending changes for 3.2.2 aside from the daze effect on Typhoon, that I'm aware of. You are correct; the calculation bugfix was to solve a problem discovered by Erdluf of these forums involving the calculation of the new Tournament idol, Lunar Fury.

janaka · 09/09/09, 3:13 PM

ProtWarr: Unless I'm doing something terribly wrong, "Chance to be Crit" seems to be calculated incorrect: At 543 Defense and 15 Resilience the Stats pane says 0,32% and the tooltip "CRITTABLE! Short by -34 defense or 31 resilience to be uncrittable".

At 555 Defense and 0 Resilience it's 0% and "Chance to crit reduced by 5,60%". So the necessary crit reduction in % seems to be correct, but it obviously only counts about 0,036% crit reduction per point in defense, instead of 0,04%.

Jothay · 09/09/09, 6:25 PM

Originally Posted by Sheltim

Using 2.2.15 and DPSWarr, I'm getting NaN for every value when I select Arms. I get expected values when I select Fury. I have an item in every slot and my talents are set up. Is anyone else experiencing this?

EDIT: After a bit more experimentation, it seems to be due to the Arms-specific abilities. Some combinations of abilities cause NaN and some do not. For example, when you select Arms on the Options tab I see NaN. When I uncheck Mortal Strike, NaN goes away. However, not every combination that includes Mortal Strike yields NaN.

This was fixed, it's not the abilites, it was that you aren't generating enough rage to fufill your rotation and HS's were going negative, which was the actual bug. There's also a corner case where landed attacks per second were coming up zero and screwing with another thing, these have both been fixed for next release.

In the meantime, if you select your Raid Buffs instead of leaving yourself unbuffed, you can probably hit hard enough to generate enough rage for your rotation and the NaN's will go away.

Jothay · 09/09/09, 6:33 PM

Originally Posted by janaka

Yeah, I'm aware of the expertise mechanics. I was saying this because I find it very odd that the tooltips tell me that I need X more hit rating to the cap, and at the same time suggest that I free expertise, although both have about the same value (threat-wise, and expertise potentially even more survival-wise).
Anyway, it's good to know that the internal calculations are fine, but I'd still like to see the displayed numbers corrected. If I can be of any help, please let me know.

The ratings on the panel are set that way intentionally with the Tooltip going into more details. They aren't "wrong". And the Hit and Expertise calcs are entirely separate, if you are under the hit cap, it will tell you to get more hit, if you are under the expertise dodge cap (and we added a separate line for parry cap in DPSWarr) it will tell you to get more expertise. If you are over on either one it will tell you how much you can free for that one only. That said, EvanM changed the ProtWarr panel to an older method that doesn't include this extra information.

ebs2002 · 09/09/09, 6:36 PM

To clarify Jothay's comment just a smidge (I checked in that fix):
The "corner case" in DPSWarr he's referring to was actually hit any time you tried to change your MH weapon. Attacks went to 0, interval went to 1/0 = infinity, bad things happen. That bug has been fixed as of changeset 36583.

Jothay · 09/09/09, 6:37 PM

Originally Posted by janaka

ProtWarr: Unless I'm doing something terribly wrong, "Chance to be Crit" seems to be calculated incorrect: At 543 Defense and 15 Resilience the Stats pane says 0,32% and the tooltip "CRITTABLE! Short by -34 defense or 31 resilience to be uncrittable".

At 555 Defense and 0 Resilience it's 0% and "Chance to crit reduced by 5,60%". So the necessary crit reduction in % seems to be correct, but it obviously only counts about 0,036% crit reduction per point in defense, instead of 0,04%.

Double-check your target level as this affects that number. I'm looking at a blank ProtWarr and it says Chance to be Crit 6.20% and 689 defense away from uncrittable.

Oakenshield_Drenden · 09/10/09, 3:22 AM

I'm struggling with how to think about the Rawr Boomkin model (Sustained dps vs. burst dps). Trying to decide on optimal trinkets, and thinking of buying the Talisman of Resurgence, which on a total basis is the top trinket.

However, I am probably not thinking about it correctly depending on the correct interpretation of the model.

Should I be looking at
a) the total dps (Burst + Sustained) ,
b) Burst dps only if I don't have mana issues
c) Sustained dps only if I do have mana issues

At this point I'm rarely having mana issues, so I think it should be b) (ie look at Burst dps only)

Thank you & apologies if this is a basic question.

Astrylian · 09/10/09, 3:34 AM

You should be looking at (a), total. *Typically* sustained and burst will be identical. That means you're not running OOM. If they're not, make sure that you've fully buffed yourself, and you have the fight duration set to something reasonable.

janaka · 09/10/09, 11:08 AM

Originally Posted by Jothay

Double-check your target level as this affects that number. I'm looking at a blank ProtWarr and it says Chance to be Crit 6.20% and 689 defense away from uncrittable.

Target level was always set to 83. But good hint anyway, now I see the problem: Chance to be Crit against level 83 should be 5.6% and not 6.20%. 5% for level 80 is correct, but then Rawr obviously gives 0.4% additional crit chance per mob level, instead of 0.2%.

kalbear · 09/10/09, 5:06 PM

For Rawr.Bear, the resistance mouseover/math is incorrect and off by 10% per category, at least on the tooltip. It appears the nature survival is also incorrect.

The example is Melaar of Sen'jin and their Nature Resist; they have 245 NR with only a NR totem, but have a 43% average chance to resist and 30% minimum. According to the resistance table by Shamgarr this should be 33% average, with a minimum of 20%.

I'm really happy this feature is in Rawr, by the way.

The Not So Evil · 09/10/09, 6:21 PM

245 NR + NR totem = 245+120 = 365, which means 30% resist or more vs 83 (Boss).

I think you may have to explain more in detail what numbers you have and what numbers you expect to see.

Malleus · 09/10/09, 7:02 PM

Originally Posted by The Not So Evil

245 NR + NR totem = 245+120 = 365, which means 30% resist or more vs 83 (Boss).

I think you may have to explain more in detail what numbers you have and what numbers you expect to see.

I believe Kalbear is saying that Melaar has 245 NR including the Totem.