Improved CamOps Unit Rating Handling Within Clamp #3980
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Current Implementation
Currently we clamp CamOps unit rating within the bounds of the FM:F (F-A*) rating system.
Problem
While my earlier fix addressed the issue of CamOps unit rating modifiers breaking a bunch of things (see #3933), there is still the issue of the CamOps Unit Rating method resulting reaching the maximum/minimum modifier faster than expected - from a balancing point of view.
Solution
Dividing the CamOps unit rating by 3 produces closer results to the equivalent FM:M rating. It's not an ideal solution, but it resolves the biggest issues.