Board & Card Games Stack Exchange is a question and answer site for people who like playing board games, designing board games or modifying the rules of existing board games. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Vassal is a great way to try out a game, but it seems that vassal versions and module versions frequently create trouble actually trying something out, i.e. you want to try something that requires the latest version, so you remove your older version and install the latest version. Then it will no longer open a module written for a lower version.

As vassal is Java (I think) it probably doesn't use the windows registry, but it could have some favorite directories it stores things in. If different versions use the same installed program GUID under windows, that could cause some serious pain. There are lots of ways things could go wrong with multiple installations, some of which might not be obvious right after installation.

So what is the most painless way to keep multiple versions of vassal around in windows so that they won't step on each other's toes? I don't really want to run one VM per vassal installation.

Any other way of solving problem that different modules need different vassal installations on windows is just as good, as that is the root problem.

share|improve this question

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.