Perhaps you can give a bit more information (see also How to report problems):
- Operating system
- Error log
Also, check your V_Global file - which you can find it at
| OS | Path |
|---|---|
 |
C:\Users\USERNAME\AppData\Roaming\VASSAL\prefs\V_Global |
 |
~/Library/Application Support/VASSAL/pref/V_Global |
 |
~/.VASSAL/prefs/V_Global |
where USERNAME is your user name on the computer.
Find the line starting with Modules=. What follows after the = is a list of paths to the various modules known to the Vassal Module Manager. If you are on Windows, then a path could be
C:\Users\USERNAME\Documents\Vassal\Foo.vmod
Check that the paths listed in V_Global corresponds to actual files. If they do not, then something could have been moved. If they do, then perhaps the OS has limited the access to the files for some reason, or the V_Global file could have gotten corrupted. Finally, there’s also the possibility that there’s no paths listed, which again would suggest that the V_Global has gotten tampered with.
The point of the fix in 3.7.22 was to never automatically remove any module from the V_Global file - unless the user explicitly told Vassal to do so. That means, that if module paths are missing from the V_Global file, then, most likely, the user has somehow made that happen.
Yours,
Christian