Issue with the new beta: by mistake, initially, I opened a module last edited in Vassal 3.5.8. Opening a log file I was greeted with this ominous dialogue.
The link to the Java replacement resource (javadoc) bounced with a 403 Forbidden code, so that was no help. In the details of the dialog is a (thankfully) short list of items within the module that seem to be running afoul of the new code.
Any suggestions on how to fix the module once 3.6 becomes the Vassal standard?
OK, the link to the web page works. But I’ll be damned if I can find anything like a “solution” to the problem. I can use the search function to get here:
Since you’re looking for a method which was removed in 3.6.0-beta1, you won’t find it in the 3.6.0-beta2 javadoc. You need to look in the javadoc of a version where the function still existed, such as 3.5.8.
You’d be replacing this method call with something that produces an ImageOp, possibly one of the static methods from Op. My guess is that you’d need Op.load(), but it’s hard to tell without seeing the code you have.
Um… I guess I am, because I’m the one who made some small edits to the current 3.5 version. The previous version, I’m not in contact with that maintainer.
I can find one folder in the archive that has .class files in it. Nothing with .java or anything similar. The entire .vsav is only 2.62MB. Would it be better to send it to you via FB or some other delivery device…?
This second replacement was a bit fraught; neither cfr nor procyon were able to decompile completely. In this instance, procyon figured out a case that cfr did not which I couldn’t see how to repair, while the bits that procyon didn’t get I did see how to repair, so I worked from what procyon produced instead.
I’ve sent you back the module. I have not tested it beyond that it loads. You’ll want to check that FlatTopPlayerRoster and FlatTopPropertySheet still behave as expected.