TOURNAMENT WINNERS
Congratulations to Brian (Allied) and David (Axis) for their employment of sound tactics, inspiring leadership and good luck!
PLAYER OPINIONS OF THE SCENARIO
"Strong Russian start by the Guards set the tone for this short, intense battle. The decline of German morale in the Stalingrad area was evident by many failed German morale checks, which allowed the Russians to advance rapidly into victory locations with minimal fear of the expected German counterattacks."
HISTORICAL OVERVIEW
The relative quiet of October 6 was obviously taken by Front H.Q. to be a sign of the enemy's exhaustion; they therefore pressed us strongly to counter-attack again with the 37th Division. I signed the order to counter-attack at 4 a.m.; but we were unable to implement it. At 11:20 a.m. the enemy launched a new, powerful attack. We met the attackers with fire from previously prepared and well-camouflaged positions.
It was a full-scale attack. From the vicinity of Verkhneudinskaya Street they threw in two divisions and more than 500 tanks. The first attacks were thrown back. The units of Zholudev's division inflicted heavy losses on the enemy. The Germans brought up reserves and repeated their attack several times. After bitter fighting they managed to penetrate our lines in the evening, seize a block of the Tractor workers' settlement and approach close to the stadium.
Approximately four enemy battalions and sixteen tanks were destroyed in the day's fighting.
After such losses the enemy could not continue his offensive the following day. The appearance of the 37th Guards Division in the path of his main attack had upset Paulus's calculations. He had been unable to strike a lighting blow and break through our front. We had not failed to locate his main group.
In the fighting for the factory district the soldiers of Zholudev's (37th GD), Gorishny's, Andryusenko's and Gorokhov's divisions distinguished themselves. It was they who stopped the enemy on October 7 at the walls of the Tractor factory, and in the Krasny Oktyabr and Barrikady settlements, and by doing so made it possible for the Army to regroup its forces and prepare for the battles ahead.
-- Marshal Vasili Ivanovich Chuikov. The Battle for Stalingrad. Holt, Rinehart and Winston. 1964, pp 173-177.
RESOURCES
Victory Points Sheet.
"The Guards Counterattack", SQUAD LEADER. Baltimore, MD: The Avalon Hill Game Company, 1977.
https://storage.googleapis.com/archivesqlt/AAA00001A.pdf
"Squad Leader Replay". The Avalon Hill General Magazine. Baltimore, MD. May 1978.
https://drive.google.com/file/d/0BxBhV3GHa1N8dHdNckp4NHVXTU0/view?resourcekey=0-I-USMJticAm310okJwxrOA
"Officer Cadet School". Squad Leader Academy.
http://www.wargameacademy.org/sqla/Resources/OCS/index.html
"Stalingrad: The Campaign", Army University Press.
https://youtu.be/5p7EeTcktVU
Marshal Vasili Ivanovich Chuikov. Battle for Stalingrad. Holt, Rinehart and Winston. 1964, pp 171-187.
https://storage.googleapis.com/archivesqlt/Publications/history/AAA00001H.pdf
Q&A SECOND EDITION
The updated Q&A document redline is here, with the following changes:
Added new Q&A below.
Separated SQL 63 ON BOARD ARTILLERY and COI 63 NEW ARTILLERY CHARACTERISTICS.
Appended answers with errata and clarifications, marked with {SB}, so the responsible person is identified.
Added the COD second edition changes from 17.2-29, since no second edition ever published.
Add key SQLA conventions.
Moved superseded Q&A to end of compilation.
Comments have reason/rule/justification for changes.
The tournament will use the updated Q&A in draft. Please feel free to provide any comments on the changes.
Single Round Split Competition
This is a dual competition for the best allied player and the best axis player. This provides a level playing field between opponents and reduces the effect of an unbalanced scenario.
Pace
The tournament is paced for PBEM of a seven turn scenario. Players have fourteen weeks to complete the match or one player turn a week for a seven turn scenario. Scenarios of greater length have the same fourteen weeks and pace must be managed by players. Matches that fall behind should meet face-to-face on VSQL to ensure timely completion.
Rules and Conventions
Generally, all rules are in play unless mutually agreed upon in advance. The Tactical Training Series explicitly state rules in effect. The twelve original scenarios use the rules through those introduced.
The Squad Leader Academy Conventions are in effect, they answer rule questions from prior SQLA tournaments and provide guidance to the Administrators in rule disputes. Players are advised to read them beforehand.
Significant conventions
31B requires passengers to 'bail-out' when an AFV fires or is hit to prevent the 'panzergrenadier' hack. They may not move to an adjacent hex nor fire that player turn.
36B crews may not attempt AFV immobilization.
48B an ATG crew is only effected by a hit on the gun. This is a departure from the example but agrees with the rule.
57A Units may not advance 'up-and-over'. This prevents a unit entering close combat from outside the defender's LOS during the dfph.
The Supplemental Rules of Combat compile rules by firing unit type and target types. Use this to find the related rules in one paragraph and to resolve uncommon situations
Rule disagreements should be resolved in the following steps:
Players should discuss between themselves.
Roll the dice by mutual agreement.
Ask the Administrator, he resolves the dispute to continue play. Please post questions to BGG - Squad Leader forums for quickest response.
Medium
The official medium is VASSAL's SQUAD LEADER module. Players may use another medium upon mutual agreement.
VASSAL version 3.2.17
VSQL version 4.2.2
Boards version 5 SK
ACTS is the official dice roller, it verifies rolls and it facilitates play-by-email. You can create an account and log in here.
You should use the Squad Leader Series Module in ACTS, a template for our games.
Quick and easy ACTS
Place fire and target counters on VSQL board and type Firepower, modifiers and terrain.
Copy and paste this into ACTS Dice Roll comments and roll dice.
Copy and paste dice roll results into VSQL and resolve shots.
Players not desiring the additional record keeping may use VASSAL's internal dice roller, subject to agreement of both players.