Vassal 3.7.28 Relased

[uckelman]

VASSAL 3.7.28 Released

Download: https://github.com/vassalengine/vassal/releases/tag/3.7.28

Release notes: https://forum.vassalengine.org/t/vassal-3-7-release-notes/78948

Changes since 3.7.27

Bug fixes

• 15111: Fixed typos in menu item text
• 15054: Fix Truncated text label on hidden pieces

Improvements

• 15083: Tile large Charts
• 15042: Update MacOS launch script to allow more options
• 14547: Optimize sum and count expressions

Other changes

• 15131: Upgraded maven-artifact 3.10.0
• 15130: Upgraded apache-maven 3.10.0
• 15123: Upgraded checkstyle to 14.3.0
• 15122: Upgraded commons-lang3 to 3.21.0
• 15114: Upgraded logback-classic to 1.6.4
• 15106: Upgraded slf4j-api to 2.0.20
• 15096: Upgraded byte-buddy to 1.18.14
• 15094: Upgraded asciidoctorj-pdf to 2.3.27
• 15085: Upgraded maven-deploy-plugin to 3.2.0
• 15084: Upgraded maven-install-plugin to 3.2.0
• 15080: Upgraded clirr-maven-plugin to 2.9
• 15079: Upgraded exec-maven-plugin to 3.6.4
• 15068: Upgraded spotbugs-maven-plugin to 4.10.4.1
• 15065: Switched from obsolete mockito-inline to mockito-core
• 15050: Upgraded maven-surefire-plugin to 3.6.0

 

[ibncalb]

I'm never sure if this has an effect on VASL, but thank you

 

[Robin Reeve]

I opened VASL and started selecting boards for a new game.
Vassal crashed.
I had to reboot my (Windows) PC.
I uninstalled Vassal and installed the previous version (3.7.27) : everything went as a charm.

 

[PresterJohn]

Updated from the Win-x86-64 and running beta5 without any problems, so far.
Will try the .deb later.

 

[uckelman]

I opened VASL and started selecting boards for a new game.
Vassal crashed.
I had to reboot my (Windows) PC.
I uninstalled Vassal and installed the previous version (3.7.27) : everything went as a charm.

We'd need more details about what happened to investigate further.

 

[uckelman]

I'm never sure if this has an effect on VASL, but thank you

It does. 15054 fixes a problem someone here reported.

 

[Robin Reeve]

We'd need more details about what happened to investigate further.

When selecting a board, I had a strange display. Then Vassal crashed (a window opened telling thete was a bug) and Vasl didn't answer anymore.
Windows 11.
I tried to install 3.7.28 again, but it crashed the same way.

 

[PresterJohn]

No problems opening existing games.

However, File - New Games - throws an unexpected exception error when you select a board. Once you clear the error the board will open.

6.7.4-beta5. No extensions were loaded.

 

[Robin Reeve]

I think I use beta 4.
I use extensions, but none has caused problems up to now.

 

[PresterJohn]

I tested back to VASL 6.7.1.
Something has changed with the board picker.

 

[Robin Reeve]

Here is a download link to a small video that shows what happens (I have been using beta 5) : https://www.dropbox.com/scl/fi/qohb95p197n3ic3clixvw/2026-10-03-10-55-20.mp4?rlkey=pfm91351dg8eahb6kjy20479t&dl=0

 

[PresterJohn]

I'm pretty sure there's more than a few error logs being sent to VASSAL.

Of course it may be a bug that VASL has been working around for a long time and needs to be reset

 

[uckelman]

If you'd like to troubleshoot the problem you're seeing:

The builds archive is here. I've set the filter to display only builds from 3.7.28 development. Each build is identified by an 8-digit hexadecimalt git hash following "SNAPSHOT". The 64-bit x86 Windows builds which aren't branch builds are these:

VASSAL-3.7.28-SNAPSHOT-4ab6f9e-windows-x86_64.exe     2026-09-27T14:17:10Z
VASSAL-3.7.28-SNAPSHOT-3a24f07-windows-x86_64.exe     2026-09-27T14:15:39Z
VASSAL-3.7.28-SNAPSHOT-99c7277-windows-x86_64.exe     2026-09-27T13:06:27Z
VASSAL-3.7.28-SNAPSHOT-07e79a2-windows-x86_64.exe     2026-09-23T12:10:06Z
VASSAL-3.7.28-SNAPSHOT-194db08-windows-x86_64.exe     2026-09-19T13:08:13Z
VASSAL-3.7.28-SNAPSHOT-4614f1c-windows-x86_64.exe     2026-09-17T22:23:46Z
VASSAL-3.7.28-SNAPSHOT-3367148-windows-x86_64.exe     2026-09-15T23:00:49Z
VASSAL-3.7.28-SNAPSHOT-78f9d34-windows-x86_64.exe     2026-09-15T22:59:30Z
VASSAL-3.7.28-SNAPSHOT-4744940-windows-x86_64.exe     2026-09-15T22:41:21Z
VASSAL-3.7.28-SNAPSHOT-77d35e2-windows-x86_64.exe     2026-09-14T11:48:32Z
VASSAL-3.7.28-SNAPSHOT-d55785f-windows-x86_64.exe     2026-09-14T11:46:35Z
VASSAL-3.7.28-SNAPSHOT-77d35e2-windows-x86_64.exe     2026-09-13T22:38:03Z
VASSAL-3.7.28-SNAPSHOT-c2c1489-windows-x86_64.exe     2026-09-09T14:18:57Z
VASSAL-3.7.28-SNAPSHOT-93c857a-windows-x86_64.exe     2026-09-08T22:05:19Z
VASSAL-3.7.28-SNAPSHOT-f484a94-windows-x86_64.exe     2026-09-08T12:41:15Z
VASSAL-3.7.28-SNAPSHOT-3b73f36-windows-x86_64.exe     2026-09-08T11:15:47Z
VASSAL-3.7.28-SNAPSHOT-d59ceb8-windows-x86_64.exe     2026-09-08T11:10:44Z
VASSAL-3.7.28-SNAPSHOT-a5ea42b-windows-x86_64.exe     2026-09-08T10:24:25Z
VASSAL-3.7.28-SNAPSHOT-2504b8c-windows-x86_64.exe     2026-09-08T10:19:02Z
VASSAL-3.7.28-SNAPSHOT-5f607f0-windows-x86_64.exe     2026-09-08T10:17:16Z
VASSAL-3.7.28-SNAPSHOT-455a8e6-windows-x86_64.exe     2026-09-07T22:08:14Z
VASSAL-3.7.28-SNAPSHOT-e59c57a-windows-x86_64.exe     2026-09-07T21:54:43Z
VASSAL-3.7.28-SNAPSHOT-0f2139f-windows-x86_64.exe     2026-09-06T19:09:11Z
VASSAL-3.7.28-SNAPSHOT-bd65540-windows-x86_64.exe     2026-09-06T15:30:47Z

You can determine which build is the one which introduced a breaking change for you by doing a binary search over the builds. That is: Pick one in the middle of the untested range and try it. If it's good, then try one halfway between the nearest bad one and it; if it's bad, then try one between the nearest good one and it. You already know a pair of good and bad builds---the 3.7.27 and 3.7.28 releases---which bracket the list above. The process should take at most 5 steps. Let me know what you find.

 

[PresterJohn]

I believe the correct IT term is "hold my beer".


It looks like 78f9d34 introduced the error on opening a new map.

 

[uckelman]

Please try one of these builds and let me know if this solves the problem.

 

[PresterJohn]

I tried the x86-64 and it seems to open new maps from the board picker correctly.

 

[uckelman]

Vassal 3.7.29 will be available shortly with the fix. Thank you for testing.

 

[PresterJohn]

Let me see Claude AI drinking beer (and not just acting drunk) while it tests code.