From: Living in the fair city of Melbourne, Australia
Was this fire from a previously unseen enemy?
Bear this in mind, that 1 tank lost out of 12 represents 8% casualties, which is fairly high for a single engagement. Also the unit is at close quarters and within effective range of the enemy tank company. The German company is doing amove to a defend - ie iot is not in an offensive posture. These are all likely factors but I would need to step through a saved game taken from just before the engagement to be sure.
According to ESTAB, a full strength Panther Coy has 17 tanks. Since Phoenix started with an initially depleted unit of 12 Panthers as seen in
..beeing at 70% of full ESTAB,...now the question:
Is these initially depleted units equally brittle as units that took same losses during an actual battle?
That's a very good question. Perhaps Arjuna can clarify. I think the game engine does indeed keep track of the difference between the strength a unit starts the scenario with and the state at any point in time: when it takes losses, the bar goes from bright blue to a dimmer hue of blue. I've always sort of assumed that was this difference the one taken into account in "morale" related computations. Note that less than 100% estab is denoted by the bright blue bar being shorter than the maximum length.
Maybe the unit wouldn´t be that brittle if it would rather be an overstrength Plt initially. Scenario makers could add a (oversized) platoon type unit to ESTAB, but in the game name it Coy, reflecting the habit of germans to send units into combat that aren´t worth their name designations (Divisions in Regimental size, Btl in Coy size and so on). Just an idea, in case depleted units are more brittle than one would suspect.
If the above is part of the reason, a far more elegant solution would be to make a duplicate of the Pz Coy unit, name it something like Pz Coy (-) or Pz Coy (late 1944), and reduce its estab of men/machines/whatever to a lower # of elements, to reflect the fact that "100%" for 1944 German units actually means "70%". This of course means more work for the scenario designer (and introduces plenty of opportunities for fumbling when assigning estabs, since one can't check these as you can with other unit attributes).