Unity of Command: Voronezh – Turn 4

The tide of German oppression rolls in to the shores of the two Russian Cities.

Here is Turn 4 of the Video AAR of the Voronezh Scenario.


The last remains of Russian resistance in our rear are wiped out. They had the odds stacked against them, and they really didn’t stand much of a chance of ever taking Kursk. With our rear secured, I can afford to push my back line infantry forward to support the offensive.

I keep the pressure on in the North, by stabbing my heaviest armour units forward, pounding them into submission with an Iron Fist! Meanwhile, I am able to close the gap between the two offensive limbs and merge them both into one large offensive front.

Supply in the South has been a nagging problem for the last couple of turns, and my troops at the front line there are totally out of supply (they have ref exclamaition marks next to their icons). They have no offensive capability, and are weakened by their out of supply state. I take the decision to pull them back towards the bridge, to get some hot meals into the troops and stock up on ammo for the imminent offensive push next turn.

With the main Southern offensive out of action, I move forward anything I can bring to bear on the Southern defenders – mainly lighter armour and troops from the back lines that have the mobility to get some hits in.

The broadening of the front line has slightly eased the supply issues in the South, because some supplies are being passed down from the well supplied road to Voronezh.

The Russians have very little left in terms of manpower or armour to put up resistance against us. However, what they do have, they tenaciously stack up against our front line attackers. They throw their last Air Attacks in to the North, in a last ditch attempt to disrupt our progress.

Next turn, I am sure I can push home a Victory.

Join me for the next instalment in Turn 5.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Ian Bowes / spelk