Is possible to get to the Tankadin section the same optimize of the warrior tank one ?

We miss the possibility to sort and optimize gear for %N% avoid, or %N% life or so, is only to get a more complex filter so we can maximize HP and still get high in expertise or avoid.

Thanks

I appreciate the 3.0.4 armor toggle in Rawr.Bear, but it appears to be flawed. The armor calculation for cloaks multiplies the whole cloak's armor, not just the 'base' value. And the numbers in general seem too high; using the exact same high-end gear I start with 40.5k armor and end with 41k armor, which does not go with community calculations or GC's calculations. Specifically it looks like the armor multiplier is 11.5909 with the metagem. I believe it should be: 5.17*1.1*1.66*1.02 = 9.63.

4.7*1.1*1.66 = 8.58 is the talented number. The extra 1.02 only applies when you have the meta gem, and it applies to all armor values.

This is where I am a bit confused as well because I am able to make a strong setup using the 3.0.4 model that has less armor using best in slot but I take less overall damage. This didn't throw me off so much as the fact that I only lost like 3k armor and people have stated it seems off in its calculations.

In taking a naked character and adding only the Cover of Silence (470 armor) I get the dead on prediction of armor for the current system. However with the 3.0.4 model active, I only gain about 300 armor total, which is totally erroneous.

470*1.66*4.7*1.1=4033.634

The value on Rawr is 3191.9 which also includes armor from Agility. Yet when I make a completed set I can get over 40k again. Confused I am.

EDIT: Just realized you have to include the Survival of the Fittest talent (no tooltip change) to get it working.

New value for the same helm is 4813.154 in total.
4033.634 from helm armor
184.44 base armor with bear talents
125.08 armor from agility (59*1.06*2)

That is a total of 4343.154 so where is the other 470 armor coming from? Perhaps the code has it multiplied by 2.66 instead of 1.66? Or 5.7 instead of 4.7? Something that puts it at a factor of 10.4082 instead?

Sorry, I was counting the 1.02 from the meta (since it was being used in the comparison). But you're right; I mistakenly multiplied twice by the thick hide number, so it should be 8.58 without the metagem, 8.75 with.

ETA: I also didn't take into account the armor from agility, but it still comes out to about a 10x multiplier.

Yeah, I added that in a rush, not positive that it's accurate. And Rawr doesn't even have separate values for bonus vs normal armor, which is why the cloak calculation is off. Once it's on the PTR and we can test how everything interacts, I'll get it accurate.


Also, Retadins: PLEASE stop spamming about your issue (still calculating based on 70 vs 73 combat). We know about it, we're fixing it. We may have a new build with it fixed tonight, not positive.

Playing with Rawr and I have to say i'm very impressed. The Hunter numbers are they based off of the hunter spreadsheet by shandra? Or are they your own numbers, because her spreadsheet seems to be damn accurate.

Well, you can make your own filters, though the drop location data for the new WotLK items is still somewhat incomplete. As Wowhead's data fills in, that'll be more and more useful. I'll probably add built in filters for WotLK Dungeon/Heroic/Raid/HeroicRaid, in the next major version.

I believe the Hunter model is based on Shandra's spreadsheet, but I'm not positive, I'll ask Ebo about it.

What about just a filter for Epic/Blues/Greens? I seem to remember that a much older version of Rawr that I used for my druid had something like that, but I couldn't find it in 2.1.1. (I'm trying to test out Toots' enhancement shaman module.)

No, there isn't a filter on quality yet. That sort of thing is planned though.

bug:
I have 3t7 on my mage, but the set bonus is not being applied (on the buffs tab the option is there, but not checked and is greyed out). When i add a fourth piece of t7 it still does not apply any set bonus to that list.

I can't say anything about the ammo thing, but I'll look into it. Looks like something went wrong with the import and some calculations depend on ammo being set.
Pet DPS is a bit underestimated. I did not yet model all of the pets abilities and damage values of the focus dump is still on level 70 together with all base stats (agi, stam, int). I didn't have any Level 80 Hunter to ask.

Overall Accuracy: The module is very very VERY loosely based on shandra's spreadsheet. I only adapted some ideas (like rotation generation) and some numbers (hunter ap to pet ap conversion). Most of the information comes directly from news sites and beta forums and all of the code is self written. I also focused on getting the overall scaling right: While the numbers may be off be quite a bit, Rawr should be right when proposing updates.

Unfortunately I started playing a DK, so I won't be able to put any level 80 hunter experience into the module soon. If anyone has any suggestions: you are invited to add them yourself or contact me via codeplex or ej private messages and I'll see what I can do :-)

I appreciate the effort to implement a hunter model in Rawr, but currently the values are considerably off and that does influence the value of stats when you consider upgrades.
Checking relative stat values crit value seems to have no influence on pet dps even if you have talents like Go for the Throat and Cobra Strikes. So the relative value of crit rating will be wrong.
Also mana is an issue for hunter dps but not considered at all in the model which severely devalues int.

Currently I don't think it will value items correctly, not even close.

A couple things for Rawr.Mage:

• [Earthspike] shows as the best in slot offhand. It is a main hand dagger.
• When optimizing it tells me to socket everything with [Runed Dragon's Eye] but it is Unique Equiped Prismatic Gems (3)
• When Optimizing it tells me to use two [Figurine - Twilight Serpent] but it is unique

Known issue. Add the name of the set to each item and the set bonus will be enabled.

I love Rawr, great job.

One problem I have found persisting though is that on the moonkin model both moonfury and earth & moon are still 5 points in the talent trees. Back in 3.0.2 they were both reduced to 3 for the same effect as having 5 points in the old talents except the extra damage from earth & moon for the moonkin was left at 1% per point. If you could update this asap that would be great as it really hurts accurate calculations for moonkins.

I noticed the same thing with the hunter numbers. Shandras sheet gives very different numbers for the worth of stats. If you don't mind ebolad I'll rewrite the hunter portion and base it directly off of shandras spreadsheet. I'm currently at work and my boss does not have a task for me to do for the next month or so. So I should have sufficient time to rewrite the code for hunters.

Also looking at just making a quick hook so I can manually set the worth of stats so I can use the UI of Rawr even with the calculations being wrong. I'm assuming Rawr rates the items directly off the worthwhile values of stats.

I'm a software developer by profession, just not C# heavy done some silverlight, but I'm familar enough with C#.

On a computer that used to run rawr 2.1.1 as of yesterday, it just suddenly stopped working. When i launch the exe, I get i rawr loading please wait, then it just closes, no error no message. Tried uninstalling and re-installed .net 2.0, re-downloaded rawr, still does the same thing. Any suggestions?

No, Rawr doesn't rate things like that at all. Rawr uses an accurate complete situation model. Send me an IM, and I can set you up to start working on it. cnervig@hotmail.com on MSN, Astro tSD on AIM.

EDIT: Anyone getting crash-on-launch problems with 2.1.1, it's likely due to a bug in the priest model in 2.1.1. Here's our current development beta of 2.1.2, to let you guys use Rawr until we get 2.1.2 done and released. http://dl-client.getdropbox.com/u/38...r%20b2.1.2.zip

This was brought up in the Tank forums:

3.0.4 Armor mode is adding on an extra 100% armor to the final value.

I believe the culprit is in:
Rawr.Bear\CalculationsBear.cs
Line 649:
If I'm not mistaken, the "+=" there should be just an "=". That, or 4.7 should be changed to a 3.7.

Aye, it's known. (I responded to it in that thread too.) Will be fixed, along with with any other armor irregularities as soon as 3.0.4 is on the PTR and we can test things.

Go ahead. I hope you'll find at least some my code useful. If you have any question, feel free to contact me.

The last version of the worksheet I saw, did not have mana mechanics either. I planed on doing more work after reaching level 80 on my hunter.