There seems to be a general discrepancy between losses incurred by attrition (due to cold weather or jungle terrain etc.) and the corresponding manpower drain from the MP pool.
I do not have a savegame to append, as it seems to be a general bug/feature.
It is fairly easy to find.
Simply create a situation where you take some attrit. losses (preferably heavy as it will show clearer). Suspend offensive operations (or cheat and make all enemies go away). This should ensure that all losses taken are due to attrition.
Let the time run for a certain period (say a month). Note drain on MP pool.
Reload and repeat. Only do not reinforce. After said month note how much your army is below "ideal" strength.
From my experiments (somewhat less controlled than suggested here) the losses taken from attrition are insignificant compared to the drain incurred on the MP pool.
Idle speculation: Tooltip says attrition is measured in %/week. Could it be that the attrition per day has been multiplied by 7 rather than divided (an error of factor 49)?
Because the discrepancy seems to be in that general area (more than *10 and probably not more than *100)
Edit: Sent Bugreport
I do not have a savegame to append, as it seems to be a general bug/feature.
It is fairly easy to find.
Simply create a situation where you take some attrit. losses (preferably heavy as it will show clearer). Suspend offensive operations (or cheat and make all enemies go away). This should ensure that all losses taken are due to attrition.
Let the time run for a certain period (say a month). Note drain on MP pool.
Reload and repeat. Only do not reinforce. After said month note how much your army is below "ideal" strength.
From my experiments (somewhat less controlled than suggested here) the losses taken from attrition are insignificant compared to the drain incurred on the MP pool.
Idle speculation: Tooltip says attrition is measured in %/week. Could it be that the attrition per day has been multiplied by 7 rather than divided (an error of factor 49)?
Because the discrepancy seems to be in that general area (more than *10 and probably not more than *100)
Edit: Sent Bugreport
Last edited: