Panzer Grenadier Battles on April 27th:
Arctic Front Deluxe #40 - Children's Crusade Broken Axis #14 - Târgu Frumos: The Second Battle Scenario 3: Sledge Hammer of the Proletariat
Army Group South Ukraine #6 - Consternation Road to Berlin #73 - She-Wolves of the SS
Errors? Omissions? Report them!
The Mius Line
Edelweiss #9
(Defender) Germany vs Soviet Union (Attacker)
Formations Involved
Germany 99th Gebirgs Regiment
Soviet Union 395th Rifle Division
Display
Balance:



Overall balance chart for Edel009
Total
Side 1 1
Draw 0
Side 2 0
Overall Rating, 1 vote
5
4
3
2
1
2
Scenario Rank: --- of 913
Parent Game Edelweiss
Historicity Historical
Date 1941-12-02
Start Time 09:00
Turn Count 40
Visibility Day & Night
Counters 88
Net Morale 1
Net Initiative 0
Maps 3: 1, 2, 3
Layout Dimensions 84 x 43 cm
33 x 17 in
Play Bounty 173
AAR Bounty 171
Total Plays 1
Total AARs 1
Battle Types
Urban Assault
Scenario Requirements & Playability
Edelweiss Base Game
Eastern Front Maps + Counters
Introduction

After failing to hold the city of Rostov, the Germans fell back to the Mius River in southern Ukraine. There the 49th Mountain Corps dug in for the winter, and despite the critically low temperatures the jägers received such comforts as a movie theater and a field brothel. But the Red Army had no plans to let them enjoy their creature comforts.

Conclusion

The Germans flung back the Soviet attack, which came poorly prepared as the green troops bunched into waves and had little artillery support. Later, none of the division's senior officers would admit to giving the order for a counter-attack. Regardless of the desires at headquarters to hold the more-defensible river line, the jägers left their dugouts. They captured the town of Dmitrievka and pushed 395th Rifle Division back several kilometers from their starting positions.

Additional Notes

If German Gebirg leaders are preferred to regular Heer leaders, they may be gotten from Avalanche Press.


Display Order of Battle

Germany Order of Battle
Heer
  • Towed
Soviet Union Order of Battle
Army (RKKA)

Display Errata (3)

3 Errata Items
Overall balance chart for 63

The morale and combat modifiers of German Sergeant #1614 should be "0", not "8".

(Shad on 2010 Dec 15)
Overall balance chart for 54

The movement allowance on the counters in Airborne is misprinted. It should be "3."

(rerathbun on 2012 Jan 30)
Overall balance chart for 951

The reduced direct fire value in Kursk: Burning Tigers is 4-4.

(plloyd1010 on 2015 Jul 31)

Display AARs (1)

Edelweiss #9
Author triangular_cube
Method Solo
Victor Germany
Play Date 2020-07-05
Language English
Scenario Edel009

This scenario was extremely disappointing. On the surface, there is an interesting engagement to play out. You have a large Soviet formation attacking a densely defended German line. As the attack is developing, the Soviet player must make the decision to fully support it playing for the win, or alternatively decide to break off the attack as it begins to falter and establish their own defensive line in an attempt to stop the German counterattack and play for the draw. The "twist" of having the scenario (and the engagement it is modeling) switch off the attacker role in the middle of the scenario is somewhat unusual for the very early PZG modules.

Unfortunately there are numerous issues here that make this practically impossible for the Soviet player. The first being the river. This was during a time in PZG history where the scenario designers seemingly forgot how river crossings work. The scenario gives river crossing numbers, but neither side has engineers. (This issue unfortunately spans many modules in this era). Playing RAW this means the Soviets have to cram a more or less regimental size force of morale 7 dorks across a single, heavily defended bridge hex. For the sake of giving them a chance I would recommend letting them cross with the river crossing procedure sans engineers, which has been recommended by many for the similarly constrained EFD scenarios...

However, this wont help you much, as the Germans have just about as many troops as you do. Enough to literally stack every town hex in question 3 high while still defending the bridge directly with 2 companies of heavy weapons. What we are supposed to do against that is an unsolvable problem. Play balance was never a major concern for these early modules, and it shows here. The design philosophy tended to be "here is the OOB, here is the historic objective, deal with it". This one was far worse than most in that regard.

My playthrough went about as well as expected. The German OBA wrecked the low morale Soviets before they could get across the river. Those that even got close got tore up by the German machine guns. They limped back to their own town hexes and got mopped up by the equally large, but better morale, and better firepower Germans. Well, thats what happened IRL so whats the problem I suppose?

If I had to play this one again (which isnt likely to happen), and I grant the river crossing concession to the Soviets, they MIGHT have a chance by playing extremely "gamey" and scattering their forces to the wind in the backfield; waiting until the last 10 turns or so to rush the German spawn and assault all the town hexes simultaneously The objective is to occupy, not control, the hexes. Still, even then youre looking at like a 1 in 10 chance of pulling it off, which sadly is better than playing it straight up.

I gave this one a "2". Its a VERY low 2, probably a 1.5 that gets rounded up because PZG. I reserve ratings of "1" for scenarios that are mechanically broken (ie not enough turns to complete the objective while playing unopposed, exit more steps off the board than the player starts with, etc.) but the balance is so bad here that it certainly flirts with it. In the end, the decision of when to switch to the defensive for the Soviet player gives it enough spice to grant it a 2 and move on with my life.

As always, I may have just been missing something here too.
0 Comments
You must be a registered member and logged-in to post a comment.
Errors? Omissions? Report them!
Page generated in 0.391 seconds.