Create account / Log in
Discussion History

Module:GMT East Front Series Volume I


Jump to: navigation, search
AGS KtR Crimea.jpg
Publisher GMT Games Era WWII
Year 1996 Topic Eastern Front
Players 1 to 4 Scale Operational
Length Long Series GMT East Front Series


Filename Filetype Size Date Compatibility
BAGSCN_v1.31.vmod Module 68.88 MB 2014-03-13 Vassal 3.2.11
BAGSCN_v1.3.vmod Module 68.13 MB 2013-09-12 Vassal 3.2.8
BAGS_v1.2.vmod Module 52.85 MB 2012-12-01 Vassal 3.1.20
Combined Game Scenarios for Army Group South_v1.32.pdf User Guide 1.02 MB 2014-03-18 PDF
Combined Game Scenarios for Army Group South_v1.3.pdf User Guide 993 KB 2013-09-13 PDF

Module Information

Maintainer Gary
Contributors Steve Bradford, Steve Petras


With Permission of GMT.

This module covers the three GMT Eastern Front Series games: Army Group South, Kiev to Rostov and Crimea.

They can be played separately or as a single combined game.

Version 1.2 has, along with some minor errata-fixes, an additional Southern Bessarabia Map!

Version 1.3 has the set-up for the Southern Bessarabia/Danube map, a fuller game piece pallet to allow interworking with the Army Group Center/North module for those ambitious enough to play the whole of 1941 Barbarossa - and the coloured supply tags used on the North-Center module which proved popular.

NOTE: Version 1.31 is the latest and includes set-up and counter errata, plus to include additional Axis and Soviet user accounts to facilitate multi-player gaming in the larger Campaigns. As a result of play-testing, the new module also includes more overlap maps in the area North of Kiev to facilitate the combined game transfers between AGC and AGS.

Load any existing game into 1.31 and it will have the errata updates and fixes - you will need to press the Vassal button 'update pieces' to refresh units of games already started under previous module versions to get the new features.

Memory: This is a large module and you may get ‘Out of Memory’ warnings when accessing all of the map unless you set your initial heap to 512 MB and maximum heap to 1024 (double the defaults); these are located in the top left-hand buttons of the module. Also change the preferences on the Main Vassal Application to JVM initial and maximum heap to 512 and 4096 MB. It should all work OK from then-on.

Screen Shots


  • Gary
  • Steve Bradford
  • jeb123
  • Joey Sabin