uhhh, you dont seem to grasp what this thing is doing.
- 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,