additional requirements

Topics: Rawr.Retribution
Aug 16, 2009 at 4:17 PM

I am not sure if I am doing something wrong or what the deal is but when I go into the rawr Optimizer and choose to add an additional requirement the list box only displays for choices

Overall Rating

DPS Rating

Health

Meele Avoid %

 

After watching the video it looks like there is a ton more options, like hit rating, etc. Any help is appreciated, thanks.


Coordinator
Aug 16, 2009 at 6:04 PM

Those options are specific to each model. Which model are you using, and which requirements are you looking for?

Aug 16, 2009 at 11:24 PM
Edited Aug 17, 2009 at 3:21 PM

BloodElf Ret Pally, Hit Cap and Expertise Cap

 

Aug 19, 2009 at 9:01 AM

So is there anyway to do this?

Aug 19, 2009 at 2:33 PM

My guess is that Melee Avoid % is a combination of Hit and Expertise caps (ie, Melee Avoid % = 0 means you're at both hit and expertise caps.  1% means that you're only going to have 1% of your attacks dodged or miss -- 4 expertise below the cap, 1% below the hit cap, or a combination of the two).

Aug 20, 2009 at 1:52 AM

I dont think this takes the Expertise Cap into consideration at all. Can Anyone verify? And it doesn't seem to be working properly for the Hit cap either. Would there be any other possible way to do this inside the program? If not is there a place for suggestions and improvements to the program. Thanks in advance

Developer
Aug 20, 2009 at 2:10 AM

Looking at the function it is calling:

public float GetMeleeAvoid() {
    return 1f
        - GetMissChance(_stats.PhysicalHit, _calcOpts.TargetLevel)
        - GetDodgeChance(_stats.Expertise, _calcOpts.TargetLevel)
        - GetParryChance(_stats.Expertise, _calcOpts.TargetLevel) * _calcOpts.InFront;
Setting 'Melee Avoid % <= 0' should make you both Hit capped (8% @ 83 targ) and Expertise Hard capped (13.75% @ 83 targ if standing in front 100% of the time)

Aug 20, 2009 at 2:19 AM

Thank you for the quick response, is there anyway to adjust the expertise cap without affecting the hit cap? As a Ret Pally should never really be in front of the target therefore that would bring the cap to 214 expertise rating (26 expertise, 6.5%). From what i am understanding its all built into one where if I change the Melee Avoid then that will effect the hit cap as well. This would explain why it is unable to Optimize my results for Melee Avoid % <= 0 when I clearly am reaching the hit cap and the expertise cap for being behind a targ @ 83. Thanks again.

Developer
Aug 20, 2009 at 2:39 AM

uhhh, you dont seem to grasp what this thing is doing.

return 1f
- GetMissChance(_stats.PhysicalHit, _calcOpts.TargetLevel)
- GetDodgeChance(_stats.Expertise, _calcOpts.TargetLevel)
- GetParryChance(_stats.Expertise, _calcOpts.TargetLevel) * _calcOpts.InFront;

GetMissChance is "8% - (Total Hit Bonuses As A Percent)" so you want this to be '<= 0' and this section is not affected by being in font or back

GetDodgeChance is "6.5% - (Total Expertise and Dodge Reduction Bonuses As A Percent)" so you want this to be '<= 0' and this section is not affected by being in font or back

GetParryChance is "13.75% - (Total Expertise and Parry Reduction Bonuses As A Percent)" so you want this to be '<= 0' and this section is affected by being in font or back so standing in back 100% of the time will put this part at 0% automagically. However, I do not suggest for any model to blatently state that you are behind the mob 100% of the time as most fights involve movement and you cannot guarantee being behind the mob 100% of the time. I personally use 75% time in back as it's a decent average amongst most boss fights.

However, I just noticed something else. If you are nice and capped the result of the function is 1, which is being multiplied by 100 (to handle the percentage translation). So in the Optimizer, the requirement that you want to set, with the way the code is currently written, is 'Melee Avoid % >= 100' which means your attacks land 100% of the time.

Since this is counter-intuitive and backwards from how other models are doing it, I can change it to function differently and break out the values in case someone (though there's no reason to) wants to just make themselves hit capped and skip expertise, etc.

Aug 20, 2009 at 3:17 AM

Thank you very much for your explanation and time. Changing 'Melee Avoid % >= 100' worked and showed the values that I needed. It does seem a little backwards but thank you for your help and time. If it is not to much trouble I think it would be a great to have a break down of different values, more options are never a bad thing :) .... Thanks again

Developer
Aug 20, 2009 at 4:29 AM

I've made a commit that gives new optimizer options, basically I copied over DPSWarr's and tweaked them so they work for for Ret.

To be Hit capped (8%) and Dodge Capped (6.5%) use '% Chance to be Avoided (Yellow/Dodge) <= 0'

Aug 20, 2009 at 4:39 AM

Thanks Again for your time really appreciate you taking a look at this and making the changes!

Sep 21, 2009 at 3:02 PM
Jothay wrote:

I've made a commit that gives new optimizer options, basically I copied over DPSWarr's and tweaked them so they work for for Ret.

To be Hit capped (8%) and Dodge Capped (6.5%) use '% Chance to be Avoided (Yellow/Dodge) <= 0'

Hey. Sorry bout opening the discussion again... ive looked for new option in the optimiser and cant seem to find it? Was it removed again or did i miss another discussion

stating it was?

 

Thank you for the nice work!