Unable to enter new version of a module

[cholmcc]

@SteelDragon

I planned on having all VASSAL modules for the Torch campaign by itself to be version 1.X. All VASSAL modules for the Torch and Western Desert campaigns combined would be version 2.X. Finally, All VASSAL modules for the Torch, Western Desert, and Near East campaigns combined would be version 3.X. What do I need to do here? Thanks.

I guess you are talking about the project Torch.

As I understand it, you have three types of modules

1. Torch campaign
2. Torch and Western Desert campaigns
3. Torch, Western Desert, and Near East campaigns

What would be most natural in that case, would be to have 3 different packages, say

• Torch campaign
• Torch and Western Desert campaigns
• Torch, Western Desert, and Near East campaigns

Module releases (or versions) within a package are independent of each other, so there’s no need to make any kind of convention on the release numbers in that case. In fact, it is better to use a straight-forward increasing version number for each package.

If you do this, you will have a structure like

• Project: Torch
  • Packages:
    • Torch campaign
      • Release 1.1.0
      • Release 1.0.0
    • Torch and Western Desert campaigns
      • Release 1.1.0
      • Release 1.0.0
    • Torch, Western Desert, and Near East campaigns
      • Release 1.1.0
      • Release 1.0.0

Users will see the three package and the latest release of each of them underneath. See for example Afrika Korps (3rd Ed.) which has 2 packages: Colourful and Ol’School. Please also read about the structure of the GL.

If you put all three kinds of modules in the same package, then users will off-hand only see the module with the largest version number (according to Semantic Versioning) - e.g., your WITD-Western_Desert&Torch&Near_East_v3.0.vmod module. To see the other modules, a user would have to click Older releases.. which is a little counter-intuitive.

Please also consider to structure the README part to make it clear what goes with what.

@SteelDragon

I am trying to add a new version of a module to my Torch project and it gives me an ‘Invalid version’ error message. I am trying to add ‘WITD-Western_Desert&Torch-2.2.0.vmod’ to the project. It is an update to the ‘WITD-Western_Desert&Torch_v2.1.vmod‘.

Check that the version set inside the module file WITD-Western_Desert&Torch-2.2.0.vmod - presumably 2.2.0 is the same as the release to which you are trying to add it. See also about adding a module to a release.

Yours,
Christian