For The People

Tips When Updating/Maintaining Module

Vassal Module development is a bit "wild west", in that anyone can jump in and do it, and anyone can upload a new one to the server! So by all means jump in and help! BUT, there are a few "delicate" aspects of updating a For The People module, and this file lists a few steps that "if followed" will make everyone's life easier. They are also documented here lest we forget them ourselves! -- Brian Reynolds, 2020

A WORD OF WARNING

This module does depend on quite a few "custom java classes". The most complicated ones have to do with the automatic stack reorganization (if you think it's slow now, wait till you see it without the custom classes!). The source java code for the classes IS included in the module "vmod" file, but modifying and maintaining custom java classes is considerably more painstaking than regular Vassal work, and is definitely "not for the faint of heart". You have been warned!

FIRST AND FOREMOST!

Most importantly, the four "Scenario" saves must be recreated afresh whenever there have been any changes to prototypes and internal logic. The "Refresh Counters" function is NOT sufficient, as there are aspects which this cannot touch! Therefore each of the four scenarios must be created again manually - frustrating, but only takes about 5-10 minutes.

Step 0 - (Optional-but-Recommended) See if the coast is clear!

Step 1 - Update Campaign/1861 Scenario

Step 2 - Update 1862 Scenario

Step 3 - Update 1863 Scenario

Step 4 - Update 1864 Scenario

Step 5 - Optional But Recommended - adjust Change List and Credits

Step 5 - Save Your Module Out

Step 6 - Test Module Even More ("Just In Case")

Step 7 - Upload to the For the People Vassal Module page

Step 8 - Relax and Enjoy!