How to Integrate VASSAL into the Linux Desktop

[cholmcc]

@akulkis00

If you’re playing a game by email (PBEM), both players starting on the same version of vassal, and you update your vassal installation, but your opponent doesn’t, that alone can lead to problems.

It is unlikely to happen if the update is patch update (e.g., 3.7.25 → 3.7.26), because traits should not be updated in such a patch release, and after all, a .vsav mainly consists of the states of traits. This is also true of logs (.vlog files).

You can look through the changes of recent patch releases, and you will likely find very few changes (if any) that would break .vsav or .vlog compatibility.

It is much more likely that a module (.vmod) upgrade will introduce compatibility changes.

@akulkis00

… autoupdate could cause a lot of frustration for that user …

Again, to be clear, there’s no auto-update scheme in place for any distribution of Vassal - save, perhaps, via Flatpak. Neither -other.zip, -linux.tar.bz2, .deb, .rpm, .dmg, -x86_64.exe, -x86-32.exe, nor -aarch64.exe distributions do automatic updates - the user has to take action, so the point of auto-updating is moot.

Yours,
Christian