-
Notifications
You must be signed in to change notification settings - Fork 178
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
50.00 - Unit Veterancy Skill Level seems incorrect. #4802
Comments
seeing this as well. combat personnel skills levels are 2 veteran, 6 regular, 5 green (or if counting only TOE units it's 2 vet, 4 reg, 4 green) techs: 5 vet, 4 reg, 2 green, 1 ultra-green. even after removing the 5 veteran techs (and advancing a week), the experience level is still calculating as Veteran. If I switch the campaign options to FM-Mercs reputation, the experience changes to Regular. So it may be something specific to Campaign Ops reputation |
MHQ Code Revision: 1348549 My combat personnel is composed of: I'll append my full savegame and customs, in case a dataset is needed. |
So my first inclination is that one of a couple things could be happening:
Unless investigation shows the final option is true this is working as intended. |
Closing this report as upon investigation the system was found to be working as intended. This can be confirmed by manually totally all relevant skill levels (the ones visible in the Edit Person screen) and then comparing that value to the value shown in debug logging. |
Please re-open as this bug report is accurate. |
Closing as resolved (after further discussion there was found to be an issue) |
Generate brand new company, seems to always be rated as Veteran. It was explained that it should calculate average level across combat only personnel.
To repeat - generate company, advanced a week so unit report would change, look at roster and compare.
My personal Preset - Zero Vets:
Campaign Ops Preset - 3 Vets
Complete Experience Preset - 1 Elite, 1 Vet, 2 Green, 3 Ultra Green.
The text was updated successfully, but these errors were encountered: