There is a bug with [Girdle of Chivalry] being under-valued. May not be working correctly with gems, but I'm not sure. Right now, with no belt equipped and at 216 hit rating, Rawr is telling me it's the 5th best plate belt. However, if I apply the relative stat values to both items (while no belt is equipped), I get [Girdle of Chivalry] at 293.8 DPS, while it's only showing up as 241.45 DPS. Doing the same to [Girdle of the Ascended Phantom] (which it currently recommends as BiS), I get 252.48 DPS, and it shows as 248.84. If I ignore both red gems in the [Girdle of Chivalry], I get 240.04, which is a lot closer to what's being listed and is what leads me to believe it may have something to do with gems.

edited to note: stats seem to update correctly when equipping [Girdle of Chivalry], but unless there's some hard DR I'm hitting on strength or haste somewhere, it doesn't make sense to be that low on DPS.


Also noticing an oddity in relation to expertise. In my current gear set, I have 0.01% miss (262 hit) and 0.68% dodge (23 expertise, 150 rating) with [Ruthlessness] as ring 1, [Surge Needle Ring] as ring 2 and [The Jawbone] as my weapon.

Rawr tells me that [Ring of Invincibility] and [Strong-Handed Ring] are both better than both rings I have equipped (specifically, RoI > SHR > Ruthlessness for ring 1 and SHR > RoI > SNR for ring 2), and [Betrayer of Humanity] is the best weapon. However, if I equip either ring into either slot, it tells me Jawbone is now the best weapon, and the rings swap around a lot. The following happens in each scenario, starting from the base set of Ruthlessness, SNR, Jawbone.


Equipping BoH --> Ruthlessness and SNR become BiS. Miss is unchanged. Dodge goes up to 3.72%.
Equipping SHR over Ruthlessness (ring 1) --> Jawbone becomes BiS weapon. RoI is still > SHR for ring 1. Ruthlessness becomes BiS over SNR for ring 2. Miss goes to 0.00%, and Dodge goes up to 1.65%.
Equiping RoI over Ruthlessness (ring 1) --> Jawbone becomes BiS weapon, RoI remains BiS ring 1, and SNR moves to BiS for ring 2. Miss is unchanged, and dodge moves up to 1.65%.
Equipping RoI over SNR (ring 2) --> Jawbone becomes BiS weapon. SNR becomes BiS for ring 1, and Ruthlessness is now better than both RoI and SHR. SHR remains better than RoI for ring 2. Miss goes up to 0.99% and dodge stays at 0.68%.
Equipping SHR over SNR (ring 2) --> Jawbone becomes BiS weapon. Ruthlessness becomes BiS for ring 1. SHR remains BiS for ring 2. Miss goes up to 0.13% and dodge remains unchanged at 0.68%.



Lazyeye_-_Ret.xml Download File on FileFront is the XML file for reference.

I do not have heroic presence enabled, however, even if I did [Girdle of Chivalry] has less hit than [Girdle of the Ascended Phantom], which be even more of a reason why it should be the better belt when hit is not useful considering it has 19 more strength and 64 haste compared to 33 crit.

I will respond to this with another quote, I urge everyone to please read the first post FULLY before posting bugs/problems:

If for whatever reason Endoscient doesn't reply to you or get your message, you can shoot me a PM with the XML. But we really can't help you without that, there are too many factors to go into play and 90% of the time the issue is a buff option or config option that you haven't setup properly (that being said, if there IS a bug we want to find it, so we need to see the XML).

Lazyeye_-_Ret.xml Download File on FileFront is the XML file.

You are probably right about the expertise thing though with respect to Jawbone and Ruthlessness. I thought it was modeling the dwarf racial and I guess it's not. That would explain why Ruthlessness and Jawbone are swapping back and forth for BiS when equipping them. However, it doesn't explain why RoI and SHR show up as better than SNR when none of the 3 rings runs into a hit capping problem (SNR brings me to 1 rating below cap, while SHR is 5 below cap) and none have expertise on them (so it shouldn't have anything to do with that).


Actually, looking at it again, it looks like Rawr is already modeling the dwarf racial. I only have 2 items with expertise (helm and weapon) that total up to 118 expertise, which is what Rawr is showing. But it says I have 19 expertise. 118 expertise rating translates to roughly 14.33 expertise, which rounds down to 14. It shows as 19 already, which would be including the dwarf bonus.

Is the hit / expertise cap for specials lower than normal?

*sigh* I did not realize there was an updated .dll, so it looks like the haste thing was what was giving me most of the weird results. I was seeing vastly different results than what you described until I updated the dll file, which fixed everything I was having a problem with. Thank you and I apologize for not re-reading the first post.


edit: The wait feature is interesting. I see a direct increase in dps as I increase the wait limit up to 0.83 seconds, after which nothing changes. I've always wondered about whether I should wait an extra half second to cast Judgement or CS or squeeze in a DS or Consecration, and this is leading me to believe I should just wait. Is this feature fully implemented and accurate?

This is a beta version based on theorycrafted values which change every time Blizzard updates the PTR with a new build. Even if we were a month into 3.1 and the theorycrafting community had settled on one weighting for stats, there's no way to be sure that any of it is 100% accurate.

Are these the best values that they can come up with based on incomplete information? Probably, but that doesn't mean a whole lot right now. Don't try to read too much into spreadsheets and Rawr... They are nothing more than tools to help point you in the right direction.

The currently accepted best method for DPSing is to use the ability highest on priority list in the Ret thread when multiple abilities come off CD at the same time. NEVER wait for another ability to come off CD if you already have one you can use.

There is a bug in the currently released version that over values the dps gained by setting a higher wait. It will be fixed for next release. The wait feature is more of a model of human error. Say if Judgement is coming off cd .05 sec before Crusader Strike, it is very unlikely we will be able to tell which one is truly coming up first, so we just hit the higher priority one.

No matter how good the Theorycrafting gets, there will never be one final set of stat weightings. How much dps each stat gives depends on how good/high your other stats are. That is why you use a theorycrafting tool like Rawr or Redcape's spreadsheet instead of an inaccurate addon like Pawn.

Hi,

Possibly being an eejit here (new to Rawr), but when you say talent ranks look wrong, does this include talents that you expect to be available not appearing? And if so, what does one do about it?

I ask because having downloaded according to instructions, I cannot see the Divine Guardian talent at all in the Prot tree.

Based on the fact that I haven't found any other comment about this, and the fact that it is currently thought to be part of the generally accepted "best" spec for Ret (0/17/54), I suspect I may have done something embarrassingly wrong, but for the life of me I can't see what it is ;-)

Divine Guardian isn't in, because when we updated the talent trees it wasn't implemented yet. It doesn't effect calculations in anyway, so you can just pretend you have it. It will be in for the final 2.2 release.

Is there a better module suited for the live realms than the one that comes in the latest stable version of Rawr? As it is now that one doesn't value librams and certain enchants and trinkets.

The librams are already in the (2.1.9) item cache; not sure why they are not available in the comparisons window. There is a thread in the Rawr discussion forum in which the original author stated that he'd fix this if it were an easy fix, so I'm guessing either he didn't get round to it (understandibly, given that he's otherwise occupied at the moment), or it isn't easy.

As for enchants, those need to be amended by hand in the EnchantCache.xml file. From another discussion on Rawr forum, you can fix Berserking (I assume that's the one you want - it was for me) by finding that entry in EnchantCache.xml, incrementing the ID field, and replacing <BerserkingProc>1</BerserkingProc> with <AttackPower>140</AttackPower>.

The only other change I made to get a reasonable 3.0.9 module in 2.1.9 was to edit Chuchu's Tiny Box of Horrors (using the Edit Item interface) to add (iirc) 51.2 flat Crit Rating to simulate the proc (based on discussion on wowhead).

Hope this helps.