I've always taken a learn while doing approach. I wanted to learn how to make VASSAL modules so I started making modules based on a favorite game series.
The biggest playability down-side to the GCACW system is counter clutter. In the board game each combat unit almost always carries two markers (strength and fatigue) and can often carry several more (demoralized, out of supply, entrenched, and an attached leader).
When two-thirds (or more) of the counters on the board are status markers, maneuver planning is confusing and physical handling is cumbersome. So my solution was to create roster sheets to hold all these markers off the board where they are arrayed (unstacked) by unit and viewable at a glance.
Aside: I lay claim to the invention of roster sheets back in the early 1990s: MS Word documents in three columns, with a 1 x 3 table for each combat unit to hold strength, fatigue, and one other marker. I would not play the boardgames without these rosters.
They are still found today as BGG file downloads using the same basic layout. My original roster for Cedar Mountain is still shown on the MMP website (clip at right).
First Generation Modules
All of the pre-existing modules for GCACW go to great lengths trying to duplicate the marker handling of the board games. But why duplicate the biggest downside of the system? These modules specify that each unit must own its fatigue marker (which is ostensibly generic) in order for the automated recovery methods to work properly. The myriad of prototyping and triggering necessary to accomplish this just makes the module buggy, and the user experience frustrating if a game gets off track in its fatigue marker handling.
A Different Way
There are two Best Practices listed in the VASSAL 3.1 Designers Guide that apply here:
- Limit Automation
- Leverage Programmatic Efficiencies
VASSAL has two features that are ideally suite to handle games with lots of status markers, i.e. Game-piece Layers and Dynamic Properties. My approach to the GCACW modules has been to replace each type of status marker with a Game-piece layer that is keyed to a Dynamic Property (leverage programmatic efficiencies). A side effect of this is to greatly simplify the Global Key Commands of the recovery phase vs existing modules (limiting automation).
These are my resulting no-markers modules, all using a common system of right-click menu commands for unit status layers:
- Stonewall Jackson's Way
- Here Come the Rebels
- Stonewall's Last Battle
- Roads to Gettysburg
- Grant Takes Command
- Lee vs Grant
Yes, I include Lee vs Grant in the GCACW series. It has all of the core design elements - zoomed out from division level to corps level. It is ideal for learning the basic system and you can play the whole campaign in a day.
All Green Alike: Not particularly interested in this as a campaign. I'd rather play Bull Run, which is actually a very solid Rich Hamblen design with bad box art. I don't own SJW2 so not having access to the campaign rules is an issue.
On to Richmond: Recently re-acquired this. Interested in the campaign, but not a fan of the map. The only available module uses low quality scans and possibly a patchwork image. When trying to overlay a hex grid you can't get alignment in all parts of the map.
There is a rumor that the next (and last) eastern theater GCACW game will combine OTR, GTC and a new Petersburg campaign. If that gets published in my lifetime, I'd make no-markers modules for all three. It would also be the first wargame ever to cover the Petersburg and Appomattox campaigns, too.
Stonewall in the Valley. Interested in the campaign but the three staggered maps of the campaign game are quite expansive for a VASSAL module. I've got a one in the works that will eventually see the light of day. Just a matter of applying the nuts and bolts of my other GCACW modules to another set of maps and counters.
Battle Above the Clouds and Atlanta is Ours: Not interested in the western theater.