Optimizer Window Options

Under the Additional Requirements heading for the Hunter, rather than
Hit Rating, there is an option that reads "% chance to miss (yellow)." This is followed by an input box starting at 0.00 with up and down arrows to move numbers...uh....up
and down. The question is, how does this work? If I want a zero chance to miss I select it and leave it at 0.00? Or do put in a number to be read as a percentage, for example 8.00 (as in 8%) for the Hunter hit cap? There isn't much
documentation on specific settings under the Additional Requirements and how to use them properly. There are several other potential setting which also use % but seem more straight forward,
"armpen %." That simply implies you are looking for a % of armpen for the optimizer to find the best way to implement for you. The
"% chance to miss (yellow)", is a bit less clear to me, more along the lines of muddy. If any of you have any insight on this/these setting(s), input would be appreciated.

I swear, there's no way to write this stuff out so there's no way a person would ask this question.

This is what you want

% Chance to Miss <= 0

OR

% Chance to Miss <= 0.05

The latter allows the optimizer to not absolutely enforce capped hit rating, but rather allows some room for gems to halvsies it. That is to say, at 5 rating from cap you would get more benefit from another AGI/Hit gem then a pure Hit gem.

'Armor Penetration %' is literally just that, how much armor penetration % you want to enforce (either more than or less than).

This question has been asked and answered several times in these forums and in multiple issues.

My apologies. I tried using the search tool but didn't find the information for which I was looking. I am not a programmer, coder or whatever one needs to be to create these sorts of things, but I am not stupid. Why could it not be
written simply as hit rating like it is for the Death Knight? Hit rating is hit rating, regardless of class. I would also like to point out that the DK module indeed gave me halvesies on gems even though I put in a static desired hit
rating. That would make it easier to understand and no one would have to ever bother you or these boards again with such silly questions.

I appreciate your answer, but not the intolerant "tone" that went along with it. It wasn't necessary. However, for your piece of mind, I shall not bother this discussion community with future babble.

Because we do not want actual ratings listed in any of the models, they require too much of the end user. The DK model using that is actually breaking our uniformity check and they need to remove it.

'Hit Rating' requires the user to know every possible combination of Hit Rating cap for their character. For a Fury Warrior with Precision, he could have 1, 2 or 3 points giving him 1, 2 or 3% Hit, which changes his soft caps. Then there's the Draenei Hit%
buff for another 1%. Asking the User to memorize all these values and try to screw with the numbers by hand is unnecessary.

'% Chance to Miss' is uniform in that you only ever really need to enter one value, 0. Then the model will take the appropriate steps, via talents or gathering hit rating, to make you not Miss.