VASSAL Launcher 1.30

[sushidog]

A simple solution would be to uninstall the older VASSAL version.

I don't think you understand the purpose of VASSAL Launcher.

 

[ScottRomanowski]

I know that, without VASSAL Launcher, if you install VASSAL version x, then install VASSAL version y, Windows associates double-clicking with version y, even if x is a later version. I know because I've done it by accidentally myself.

If you associate opening .vlog/.vsav files with running VASSAL Launcher, you will have to have multiple configs with different launch directories to tell VL "if I open a .vlog/.vsav from there, use this VASSAL version and this module". You will have to save your logfiles/savefiles in those different directories. You also have to tell VL about the versions of VASSAL you have installed. "Uses latest VASSAL" means "the latest version that you've told VL about"; VL doesn't monitor your system as you install/uninstall items.

 

[sushidog]

I know that, without VASSAL Launcher, if you install VASSAL version x, then install VASSAL version y, Windows associates double-clicking with version y, even if x is a later version. I know because I've done it by accidentally myself.

If you associate opening .vlog/.vsav files with running VASSAL Launcher, you will have to have multiple configs with different launch directories to tell VL "if I open a .vlog/.vsav from there, use this VASSAL version and this module". You will have to save your logfiles/savefiles in those different directories. You also have to tell VL about the versions of VASSAL you have installed. "Uses latest VASSAL" means "the latest version that you've told VL about"; VL doesn't monitor your system as you install/uninstall items.

Ah, I see. So if I uninstall the latest VASSAL and then reinstall it, it will become the default VASSAL for all my non-VASL games (because I installed an earlier version for VASL-templates after installing the latest VASSAL). Or I could associate different directies with different configs, but they all just need the same config, so hopefully the resintalling the new version will do the trick.

Thanks for the response. Cool utility, really helpful for when you need an older version.

 

[ScottRomanowski]

ScottRomanowski updated VASSAL Launcher with a new update entry:

Version 1.30

Added the ability to change the VASSAL module in a configuration. The game name and the preference file must be the same in the old and new module; this hopefully will prevent people from creating a configuration with a module for game X, then accidentally changing it to a module game Y.

Also ensure that VL creates the "inactive" directory in the extension directory, both where VASSAL uses it and in VL's copies of the extension directories.

Read the rest of this update entry...