The VASSAL Team is happy to announce VASSAL 3.6.17.
IMPORTANT
NEW! 64-bit ARM packages: There are now MacOS and Windows packages for 64-bit ARM processors. If you have a Mac with an Apple Silicon CPU (which is a 64-bit ARM processor), we recommend using the 64-bit ARM build.
Code deprecated more than a year ago has been removed. Modules containing custom code using that code MUST be updated if they are to work with 3.6.
Things may be broken which worked previously. If you find a new bug, please report it.
Modules saved in 3.6 are not openable by earlier versions of VASSAL. We recommend keeping a backup copy of any pre-3.6 modules you plan to modify in 3.6 until youâve verified that everything works to your satisfaction.
12247: Fix error dialog broken since 3.6.15 for exceptions with null messages
12237: Fix edge case Mat Refresh bugs
12234: Donât try to render SVG which would have a width or height of zero
12233: Ensure that OpMultiResolutionImage.getBaseImage() never returns null
Other improvements
12250: Adjusted TilingHandler to simplify VASL and VSQL custom tilers
12238: Upgrade bundled Java from 19 to 20
Changes since 3.6.15
Bug fixes
12232: Notify user about mismatch between module and save version instead of throwing IllegalStateException
12231: Check that all tiles exist for an image when tiling, not just 0,0@1:1
12221: Fixed various missing searchability on various components
12209: Report correct trait in expression Audit Trail
12159: Correctly handle install paths containing spaces in VASSAL.sh
12158: List Key Commands tool can be re-opened after closing with X button
12152: Work around Java bug which prevents displaying Windows file dialogs
Changes since 3.6.14
Bug fixes
12119: Restore vanished Load Comments
12116: Pieces shouldnât receive same GKC twice just because it sent them to a new map
12105: Deckâs âSend-to-Deckâ subcomponent has access to properties (e.g., PlayerSide) and properly shuffles âalways shuffleâ decks
12093: Fix disabling of toolbar items nested in multiple Toolbar Menus
Other improvements
12140: Action Buttons on pieces that have just been drag-moved are suppressed for a half second for user-error avoidance
12085: Screen capture default icon height adjusted to match the other 16-pixel-high icons
12069: Tiling: Improved detection of and recovery from running out of memory; improved error dialogs
9894: Improved error dialog for failure to start child process
See the Release Notes for descriptions of the changes in 3.6.
Minimum Requirements
VASSAL 3.6 requires Java 11 or later.
The Windows and MacOS packages have an appropriate version of Java bundled with them, so there is no need to install Java separately on those operating systems. On Linux, use your package manager to install Java 11 or later.
Help us test
Please report bugs in the Technical Support & Bugs category at the VASSAL forum.
Just wanted to say what a great job you guys are doing. Iâm really enjoying all the new upgrades and features you guys have implemented to vassal. Thanks for the hard work!
Iâm currently designing in V 3.6.7, having not updated for a year or so. Today I thought I would download the latest version (3.6.17?) to look at using it for future designs. However, after the download was apparently complete, I received a warning from Microsoft that the file ââŚisnât commonly downloadedâŚâ and I am prevented from placing the .exe file in my system for later installation (I donât yet plan to design with 3.6.17 until Iâm certain I donât have any problems understanding it - Iâll continue to use 3.6.7). However, I canât get to understand 3.6.17 if I canât install it. Can you help, please?
There should be little to nothing new to understand for module design across patch releases. New features customarily donât appear in patch releases. 3.6.17 shouldnât affect your design work over 3.6.7 unless you were relying on a bug that we fixed. If you are relying on a bug we fixed, then discovering that is the first step toward correcting it, and the sooner the better.
This is your browser? Windows Defender? telling you that it hasnât seen a lot of downloads of our installer yetâwhich is unsurprising, given that 3.6.17 was released only a week ago.
Iâd like to be able to provide you with some screenshots of how to tell Windows that this is fine, but Iâm not a Windows user so I canât produce them myself. (If anyone can provide those screenshots, Iâd appreciate having them.)
I think what youâre seeing is distinct from Windows Defender preventing the installer from running, for which we do have a FAQ entry and screenshots, here.
If you use almost any other browser to download the current installer, I donât think youâll encounter this extra barrier, just the standard Defender warnings in the aforementioned wiki link.
This is very much a Microsoft Edge thing. I just tried downloading it myself and got the same message. All you need to do is click the meatball menu (three horizontal dots on the right side of the file), and click on keep. Then you will be able to open/run the file. Windows Defender may also throw a warning for you because the software isnât âsignedâ, but you can just bypass that one as well.
