16 sq km of misery - a brief but vague AAR
Moderator: Arjuna
16 sq km of misery - a brief but vague AAR
I know everyone is excitedly waiting for COTA.
While testing scenarios, I keep a commander's log. Upon conclusion, I summarize the log and produce a scenario review. The review serves as a point of departure to discuss strategy, scenario balance, etc...
While writing up today's contribution, I decided to turn it into a quicky AAR to allow you folks to get another look at a different map and some game flavor. I will not identify the scenario here, since I don't want to create a spoiler thread.
I hope you will excuse my brevity this time, but this is just to tide you forum visitors over while the last remaining details are taken care of.
While testing scenarios, I keep a commander's log. Upon conclusion, I summarize the log and produce a scenario review. The review serves as a point of departure to discuss strategy, scenario balance, etc...
While writing up today's contribution, I decided to turn it into a quicky AAR to allow you folks to get another look at a different map and some game flavor. I will not identify the scenario here, since I don't want to create a spoiler thread.
I hope you will excuse my brevity this time, but this is just to tide you forum visitors over while the last remaining details are taken care of.
2021 - Resigned in writing as a 20+ year Matrix Beta and never looked back ...
RE: 16 sq km of misery - a brief but vague AAR
An interesting scenario. This was one of the longer ones I have played thus far.
Playing as the Germans. Total force consisted of 3 Bn motorized infantry and 1 Bn of armor. German forces enter from the North and are effectively the attacker. Identified as BN1, BN2, BN3, and PZ1.
The scenario length of 6+ days and the scarcity of forces relative to the number of objectives to be taken (and the fact that there were only completion points to be awared) along with a decent number of destroy the enemy points, let to a single conclusion -> Defeat the enemy’s main body and worry about taking objectives at the end. This in essence became the plan.
Taking Castle Ridge was seen as problematic. A difficult position to attack (too much open terrain with good visibility) and a difficult position to hold.
Instead my initial focus was to take and hold the Village of Panteleemon. Panteleemon would be the key to further operations to the South. It was taken on the Day #2 (BN1).
With the arrival of our armor (PZ1) on Day #2, an initial fire support position was set up to the North of the Ridge. While this was happening, a recon tank platoon was sent South through Panteleemon, approaching Poroi, and East to Derbina. The route was determined to be relatively clear.
It looked like there would be an opportunity to encircle the enemy force.
Late that day our armor was ordered South to Derbina to cut the enemy’s line of communications. In the meantime, a reinforcing infantry Bn (BN2) was ordered South to deploy East of Poroi.
On Day #3, Panteleemon looked pretty secure. So, one company was left behind to hold the Village. The Panteleemon Bn (BN1) along with engineers was ordered to make a night time assault on the Tunnels from the North. They reached the tunnels which enemy were unsuccessful in destroying. The fight to hold the tunnels would continue to the end of the battle.
By this time, the enemy was loosely pocketed between the Ridge to the North, Poroi to the West, and Derbina to the South. They were suffering high attrition.
At the end of Day #4, our final infantry Bn (BN3) would arrive. On Day #5, they attacked South across the Ridge pushing towards Platamon while the Bn (BN2) near Poroi pushed East.
For the next two days, horrific carnage of blow counter blow took place.
By day #7, my general staff estimated the enemy had been attrited by 50% and our own force by about 20%. Orders were sent down the line to seize and hold whatever objectives could be taken by our battered units in order to secure a final victory.
I often look for the elegant solution to these battles. There was none to be had here. Many times during the fight, it left me questioning. Had I done the right thing? Would a marginal advantage in the attrition rate over a few days be enough to allow me to achieve victory in the final analysis? Despite my doubts – decisive victory!
(screen shots follow)
Playing as the Germans. Total force consisted of 3 Bn motorized infantry and 1 Bn of armor. German forces enter from the North and are effectively the attacker. Identified as BN1, BN2, BN3, and PZ1.
The scenario length of 6+ days and the scarcity of forces relative to the number of objectives to be taken (and the fact that there were only completion points to be awared) along with a decent number of destroy the enemy points, let to a single conclusion -> Defeat the enemy’s main body and worry about taking objectives at the end. This in essence became the plan.
Taking Castle Ridge was seen as problematic. A difficult position to attack (too much open terrain with good visibility) and a difficult position to hold.
Instead my initial focus was to take and hold the Village of Panteleemon. Panteleemon would be the key to further operations to the South. It was taken on the Day #2 (BN1).
With the arrival of our armor (PZ1) on Day #2, an initial fire support position was set up to the North of the Ridge. While this was happening, a recon tank platoon was sent South through Panteleemon, approaching Poroi, and East to Derbina. The route was determined to be relatively clear.
It looked like there would be an opportunity to encircle the enemy force.
Late that day our armor was ordered South to Derbina to cut the enemy’s line of communications. In the meantime, a reinforcing infantry Bn (BN2) was ordered South to deploy East of Poroi.
On Day #3, Panteleemon looked pretty secure. So, one company was left behind to hold the Village. The Panteleemon Bn (BN1) along with engineers was ordered to make a night time assault on the Tunnels from the North. They reached the tunnels which enemy were unsuccessful in destroying. The fight to hold the tunnels would continue to the end of the battle.
By this time, the enemy was loosely pocketed between the Ridge to the North, Poroi to the West, and Derbina to the South. They were suffering high attrition.
At the end of Day #4, our final infantry Bn (BN3) would arrive. On Day #5, they attacked South across the Ridge pushing towards Platamon while the Bn (BN2) near Poroi pushed East.
For the next two days, horrific carnage of blow counter blow took place.
By day #7, my general staff estimated the enemy had been attrited by 50% and our own force by about 20%. Orders were sent down the line to seize and hold whatever objectives could be taken by our battered units in order to secure a final victory.
I often look for the elegant solution to these battles. There was none to be had here. Many times during the fight, it left me questioning. Had I done the right thing? Would a marginal advantage in the attrition rate over a few days be enough to allow me to achieve victory in the final analysis? Despite my doubts – decisive victory!
(screen shots follow)
2021 - Resigned in writing as a 20+ year Matrix Beta and never looked back ...
RE: 16 sq km of misery - a brief but vague AAR
A close up of the 16 square kilometers where most of the fighting took place.


- Attachments
-
- 16km.jpg (179.96 KiB) Viewed 313 times
2021 - Resigned in writing as a 20+ year Matrix Beta and never looked back ...
RE: 16 sq km of misery - a brief but vague AAR
Final outcome of the objectives ...


- Attachments
-
- 16km2.jpg (62.41 KiB) Viewed 313 times
2021 - Resigned in writing as a 20+ year Matrix Beta and never looked back ...
RE: 16 sq km of misery - a brief but vague AAR
Final numbers ...


- Attachments
-
- 16km3.jpg (38.5 KiB) Viewed 312 times
2021 - Resigned in writing as a 20+ year Matrix Beta and never looked back ...
RE: 16 sq km of misery - a brief but vague AAR
I get the impression from the victory screen, the result is dependant upon destroying the enemy rather than taking ground.
-
-
RE: 16 sq km of misery - a brief but vague AAR
I didn't show the objective screen and points, because that would have pretty much forced me to identify the scenario. However, if I had failed to hold all the objectives which I did, I probably would have gotten a marginal victory or even a draw.
However, clearly in this scenario doing damage to the enemy's main body as opposed to seizing objectives early and holding them was the key. You don't always have that luxury if most of your potential points are of the occupation style. Once you did enough damage, you could just go after the objectives at the end.
However, clearly in this scenario doing damage to the enemy's main body as opposed to seizing objectives early and holding them was the key. You don't always have that luxury if most of your potential points are of the occupation style. Once you did enough damage, you could just go after the objectives at the end.
2021 - Resigned in writing as a 20+ year Matrix Beta and never looked back ...
RE: 16 sq km of misery - a brief but vague AAR
The battle displayed graphically (and hopefully easier to follow):
Yellow - BN1 initial force.
Red - Armor reinforcements.
Purple - Recon element (split off from Armor).
Green - BN2 reinforcements.
Blue - BN3 reinforcements.
The follow screen shots show the major phases and actions over six days.
Yellow - BN1 initial force.
Red - Armor reinforcements.
Purple - Recon element (split off from Armor).
Green - BN2 reinforcements.
Blue - BN3 reinforcements.
The follow screen shots show the major phases and actions over six days.
2021 - Resigned in writing as a 20+ year Matrix Beta and never looked back ...
RE: 16 sq km of misery - a brief but vague AAR
BN1 secures Panteleemon.


- Attachments
-
- 16kmgph01.jpg (111.61 KiB) Viewed 312 times
2021 - Resigned in writing as a 20+ year Matrix Beta and never looked back ...
RE: 16 sq km of misery - a brief but vague AAR
Armor places fire on the defenders on the Ridge.


- Attachments
-
- 16kmgph02.jpg (112.77 KiB) Viewed 312 times
2021 - Resigned in writing as a 20+ year Matrix Beta and never looked back ...
RE: 16 sq km of misery - a brief but vague AAR
Recon element breaks off to gauge enemy resistance to Derbina.


- Attachments
-
- 16kmgph03.jpg (116.29 KiB) Viewed 312 times
2021 - Resigned in writing as a 20+ year Matrix Beta and never looked back ...
RE: 16 sq km of misery - a brief but vague AAR
Armor follows South to Derbina to cut the enemy's line of communications.
BN2 seals off the area deploying East of Poroi.

BN2 seals off the area deploying East of Poroi.

- Attachments
-
- 16kmgph04.jpg (120.61 KiB) Viewed 312 times
2021 - Resigned in writing as a 20+ year Matrix Beta and never looked back ...
RE: 16 sq km of misery - a brief but vague AAR
While leaving a company guarding Panteleemon, BN1 assaults the Ridge.


- Attachments
-
- 16kmgph05.jpg (121.47 KiB) Viewed 312 times
2021 - Resigned in writing as a 20+ year Matrix Beta and never looked back ...
RE: 16 sq km of misery - a brief but vague AAR
The enemy is trapped in a pocket.
BN3 attacks pushing South into the pocket.
BN2 attacks pushing East into the pocket.
---
Not shown, on the final day all units redeploy to hold the designated objectives of the operation.

BN3 attacks pushing South into the pocket.
BN2 attacks pushing East into the pocket.
---
Not shown, on the final day all units redeploy to hold the designated objectives of the operation.

- Attachments
-
- 16kmgph06.jpg (124.47 KiB) Viewed 312 times
2021 - Resigned in writing as a 20+ year Matrix Beta and never looked back ...
RE: 16 sq km of misery - a brief but vague AAR
I suppose I should have done the graphic thing before, but I was on my way out for a Valentine's dinner.
All may be fair in love and war, but, at least, for love you better be on time. War always falls behind schedule.
All may be fair in love and war, but, at least, for love you better be on time. War always falls behind schedule.
2021 - Resigned in writing as a 20+ year Matrix Beta and never looked back ...
RE: 16 sq km of misery - a brief but vague AAR
ORIGINAL: MarkShot
All may be fair in love and war, but, at least, for love you better be on time. War always falls behind schedule.
So that's a Kratzerism is it?[;)]
RE: 16 sq km of misery - a brief but vague AAR
ORIGINAL: ArjunaSo that's a Kratzerism is it?[;)]ORIGINAL: MarkShot
All may be fair in love and war, but, at least, for love you better be on time. War always falls behind schedule.
I suspect it's a universal given. [;)]
Ray
