Can't start Combat Commander modules, any of them

Technical Support & Bugs
1

Hi everyone. I’ve had a problem come up today when trying to run Combat Commander,

Screenshot 2021-10-24 140347
Screenshot 2021-10-24 1403471737×1443 177 KB

CCP or CCE. I upgraded Vassal to 3.6.0 Beta-3 today and suddenly I get the message attached, but not for any of the other 2 dozen games I have on vassal that are running normally. If anyone has any advice, I have a match later today! Much appreciated and sorry for bothering anyone.

2

This has been in the works for many, many months now to try and encourage module designers to come up with a plan for their (often very aged) custom code methods.

If you are in a pinch for today, just downgrade to the current stable release of VASSAL (or install it side-by-side).

1 Like
3

Also double check that you are using the latest version of the module. I am pretty sure CC has already been updated to be 3.6 ready.

4

I have not updated the module. I have always stated I am waiting for V4. Last stable edition was 3.2.6
It does work with later Vassal editions but I have not verified to what point

5

I checked all the modules in the archive to see which would be affected by removing deprecated code in 3.6; it wasn’t a very long list and almost no modules in it were their current versions. I thought that the CC modules were not in that list, so this is a surprise to me.

The custom code report for CC:E says this:

Removed classes, methods, and fields in /home/uckelman/Downloads/Combat_Commander_Europe.vmod
(used by => removed item, version when removed

cc.CCEmbellishment => VASSAL.tools.DataArchive.getCachedImage(java.lang.String), 3.6.0
cc.CCEmbellishment => VASSAL.tools.DataArchive.getImageBounds(java.awt.Image), 3.6.0
cc.CCEmbellishment => VASSAL.tools.DataArchive.getScaledImage(java.awt.Image, double), 3.6.0
cc.PieceMover => VASSAL.tools.DataArchive.getCachedImage(java.lang.String), 3.6.0

Those wouldn’t be very hard to adjust for; it’s a matter of getting the images via ImageOps instead of the DataArchive. I’d be happy to advise with that if I could see the source code.

As for what else would need to be adjusted to be current, that report doesn’t and can’t tell you. It’s possible that nothing else would need adjusting. Do we know if CC:E works in 3.5.8?

That said…

I’ve been working on a module data converter for several weeks now, and that’s necessary for V4. I’d like to be able to continue on with that; the only reason I can is that I’ve been able to mostly disengage from work on 3.6.

I expect that dealing with complaints about the CC modules being broken with 3.6 will delay V4 more than fixing the modules will. I would prefer not to have to undertake that work myself and avoid the delay entirely, but I will do it if I must. Even if V4 were ready now, 3.5.8 (and soon 3.6.0) would still be the current V3 release in use. V3 has a fair bit of life left in it yet.

We don’t have plans for anything beyond 3.6 in the V3 series, so getting things current for 3.6 may be the last time that job needs doing.

6

Do we know if CC:E works in 3.5.8?

CC:E works in 3.5.8. It’s the last working version.

7

There are now CC:E and CC:P modules updated to work with Vassal 3.6 if you check the module pages.

1 Like