ZA RODINU! (Kamil vs Mike) March 1943!

[Mike29]

T12. 04.09.1941 Western front. All units are in good condition.

[Mike29]

T12. 04.09.1941 South. We try to break distance.

[Mike29]

T12. 04.09.1941 Crimea. Remarkable attack of Coastal army.

[Mike29]

T13, 11.09.1941. Heroic battle of Leningrad.

[Mike29]

T13. 11.09.1941 Valdai area.

[Mike29]

T13. 11.09.1941 Western front

[Mike29]

T13. 11.09.1941 Tula - Voronezh sector.

[Mike29]

T13. 11.09.1941 South

[Mike29]

T14. 18.09.1941. End of operation "Varangian". It was planned for 5 turns from T9. Important and I hope the only railroad of AGN destroyed. Also seen as AGN changed direction of attacks. Attempts to pass y shortest way to Leningrad have failed. Two new pockets in Reserve front sector.

[Mike29]

T14. 18.09.1941. Defense of Moscow.

[Mike29]

T14. 18.09.1941. South.

[Mike29]

T 15. 25.09.1941. Leningrad area. Now we dont expect direct attack to Leningrad so 16 army moved to Tosno and 27 to east of Novgorod. We recognize operative target of AGN as encircleent of Novgorod and this fully suit us as this is better than attempt to reach Shlisselurg. We even move some fresh and weak units of 55 Army to Novgorod to sweeten this ojective.

[Mike29]

T 15. 25.09.1941. Moscow region. Nothing principal new here. High activity in Reserve front sector.

[Mike29]

T 15. 25.09.1941. Bryansk front. High concentration of German fast units. On this turn core decision was made y me to hold Vyazma and prevent sturm of Mozhaysk (last) line of defense.

Basis:

1. Kamil has 2 turns until the mud. He plays very offensive and seems doesnt care about defense line before blizzard, so he might goes all in and try to take Moscow, all the more nearly all tanks of the South are here.

2. If he broke my last line with forts on next turn he would have 70% chance to take Moscow on winter turns.

3. We have enough power to reopen any big pocket, so having only one turn after that such pocket will be alive during all mud and this will prevent Vyazma region from uilding forts efore lizzard. It is also will be headacke for Kamil if he will keep Moscow in mind after the mud.

I dont insist this the only right solution, and would be glad to see comments of Kamil here.

[Mike29]

T 15. 25.09.1941. South.

[KamilS]

I really felt angry at myself after Your successful raid against my rail road in AGN area and I was not far of using one of panzers from AGC area to deal with the threat immediately.

It would have been catastrophic if I have done it.

[Peltonx]

The GHC not taking Leningrad is becoming the norm.

Moscow is impossible as I have yet to see it taken in a server based or a beleivable PBeM after 1.06.11

[Mike29]

I played to much with unbeleivable opponents last time, so I reinsured and get another 200 000 to Kamil's moneybox. [:)]

[KamilS]

Pelton

The GHC not taking Leningrad is becoming the norm.

Moscow is impossible as I have yet to see it taken in a server based or a beleivable PBeM after 1.06.11

It is harder to do it theses days, but at the end of the day I guess it is about risk.

Either You maximise your potential gain, or minimise your potential loss.

Making Moscow itself a target is a bit tricky business. In my opinion it only makes sense to use it as a bait and force Soviet player to fight for it.

[KamilS]

It is quite funny thing, that at Leningrad approaches both of us evaluated other side being much much stronger. After reading this part of AAR and seeing real strength of Mike's troops I feel, that pouring arriving reinforcements into AGN area would have made the difference, but I have to say, that I do not regret not doing it.

I strongly believe that Leningrad is secondary objective and prioritising AGN over AGC has to be really justified by favourable developments.

It is either everything or nothing. Terrain favours defender massively, limits possible direction of assault and its remote location prevents using engaged troops elsewhere for 2-3 turns.

Don't get me wrong, Leningrad has to be attacked, but I strongly believe it is up to Soviet player to lose it or not. Axis should avoid overcommitting there.