Module Size

Feature Requests
1

I have made half a dozen or so modules for playtest concepts and I’ve noticed that as maps, charts, and units change, the module size keeps increasing.

This is due to the old images remaining in the vmod. It would be great if when you replace an image, the old one is deleted. The biggest effect is map boards so even just deleting old ones of those would help a lot.

2

Thus spake wifferboy via messages:

I have made half a dozen or so modules for playtest concepts and I’ve
noticed that as maps, charts, and units change, the module size keeps
increasing.

This is due to the old images remaining in the vmod. It would be great
if when you replace an image, the old one is deleted. The biggest effect
is map boards so even just deleting old ones of those would help a lot.

There’s no way to detect unused images without causing a major backward
compatibility problem in 3.2. It would mean breaking almost all custom
classes used by modules today. Brent and I wrote the code to do it a
few years ago, but realized that we couldn’t deploy it.

This will be fixed in VASSAL 4.

–
J.

3

I was just wondering.

A little judicious file-naming and using 7-zip or J-zip to open the module, and sort the image folder by size and delete the old ones is reasonably quick.

Thanks for the info.