Should logfiles form 3.2.x ( in this case 3.2.svn8313) be usable in 3.1.19?
If so, I have a problem, and they are not. If not, carry on…
No, this will almost definitely not work.
We do guarantee that 3.1.19 log files will work on 3.2, so any problems going in that direction we want to hear about.
thanks,
Brent.
Logfiles from the 3.2 beta will not be usable in 3.1.x
I think this is something that’s going to have to be made more explicit for users, because there are a number of modules floating around out there now that require 3.2 beta due to the new features that have been added: Andean Abyss, B-17, the playtest module for A Distant Plain (I think?), et al.
Thus spake keethrax:
Should logfiles form 3.2.x ( in this case 3.2.svn8313) be usable in
3.1.19?
No. Versions of VASSAL are backwards-compatible (meaning that they’re
able to read files from older versions) but not always forwards-
compatible (meaning that they might not be able to read files from
newer versions) across major.minor versions.
So, for example, 3.1.x and 3.1.y should be interoperable, as they have
the same major and minor versions, differing only in the micro version.
In contrast, you will be able to read files from 3.1.x in 3.2.y, but
there is no guarantee you’ll be able to read 3.2.y files in 3.1.x.
In practice, this means that all of the players in a game should be
using the same major and minor version of VASSAL, since everyone will
presumably be saving games.
–
J.
Thanks for the replies. I assumed that was the case. But then I thought about it some, and didn’t want to be silently sitting on a problem if I was wrong.