• Blitz Shadow Player
  • Caius
  • redboot
  • Rules
  • Chain of Command
  • Members
  • Supported Ladders & Games
  • Downloads
Forums
#02 Second Battle of Kharkov-Explicit Supply by Rick Bancroft - Printable Version

+- Forums (https://www.theblitz.club/message_boards)
+-- Forum: The Firing Line (https://www.theblitz.club/message_boards/forumdisplay.php?fid=1)
+--- Forum: Tiller Operational Campaigns (https://www.theblitz.club/message_boards/forumdisplay.php?fid=11)
+---- Forum: TOC Mod Scenario List (https://www.theblitz.club/message_boards/forumdisplay.php?fid=107)
+----- Forum: Kharkov 42 Mods (https://www.theblitz.club/message_boards/forumdisplay.php?fid=112)
+----- Thread: #02 Second Battle of Kharkov-Explicit Supply by Rick Bancroft (/showthread.php?tid=47192)



#02 Second Battle of Kharkov-Explicit Supply by Rick Bancroft - Mr Grumpy - 07-31-2008

#02 Second Battle of Kharkov-Explicit Supply
Kharkov, May 12th, 1942: In 1941, the first year of war in Russia, the German Army plowed their way across much of the Soviet Union and was stopped at the very approaches of Moscow by the Soviet winter offensive. Much has been written of this Moscow counteroffensive, but a lessor known, but rather successful Russian Winter Offense also occurred near Kharkov and resulted in the formation of the Iyzum Bulge. Both of these successes led Stalin to feel that the momentum was his. It turns out he was wrong in both cases. Nevertheless, by the spring of 1942 he was planning a bold move to encircle Kharkov and surround the German Army in the Ukraine with a two-pronged attack. His attack was also to preempt the German summer offensive that was expected to happen in the Moscow region. This Soviet Summer Offense was known as the Second Battle of Kharkov. This version has had supply units added in for explicit supply, and the terrain defensive modifiers adjusted higher for some terrain.

Large Scenario 140 turns, Designer Adj by Rick Bancroft

Download Scenario Files

Any comments you would like to leave about this scenario can be posted in this thread.