VASSAL 3.1.8 released

The VASSAL Team is happy to announce the release of VASSAL 3.1.8, which
fixes several problems found in earlier versions.


For Linux: … ux.tar.bz2

For Mac OS X: … macosx.dmg

For Windows: … indows.exe

For other operating systems: …

Source code: …

Changes since 3.1.0

The following bugs are fixed in 3.1.8:

  • Bug 2817069: IllegalComponentStateException in MenuDisplayer
  • Bug 2817064: Global Key Commands can send Null KeyStrokes
  • Bug 2817038: NPE in MetaDataFactory.buildMetaData()
  • Bug 2816275: NPE in Embellishment adding layer with no image
  • Bug 2813782: NPE in VASSAL.counters.AreaOfEffect.getArea
  • Bug 2813765: Can’t always Peek at a card, even though you can unmask it

The following bugs are fixed in 3.1.7:

  • Bug 2811307: Extraneous error messages in Embellishment following property
  • Bug 2811211: Area of Effect does not display in all Zoned Grids
  • Bug 2806392: Observer side linked to password
  • Bug 2806183: Trigger action fails to execute another TA more than once
  • Bug 2805282: SendToLocation does not undo correctly
  • Bug 2804153: NPE in ModuleManager when refreshing Save Folder

The following bugs are fixed in 3.1.6:

  • Bug 2798275: Layer following prop does not allow non-string custom props
  • Bug 2794703: StackOverflow using Embellishment level following property
  • Bug 2793103: Memory check fails on Linux due to architecture mismatch
  • Bug: Transparent images used for orthogonal rotations of opaque sources
  • Bug: Incorrect PropertySource used to evaluate properties
  • Bug: Use bounds for primary screen on multi-monitor X11 systems.

The following bugs are fixed in 3.1.5:

  • Bug 2786932: MemoryUtils.getPhysicalMemory() fails on PPC Linux

  • Bug 2787242: Layer tracking Property - Report Action lags on PieceName

  • Bug 2787134: NPE during map scrolling due to off-EDT Swing calls

  • Bug 2785328: ImageIO fails to read size of JPEGs with bad color profiles

  • Bug 2784636: NPE in MapShader.buildTexture()

  • Bug 2766794: Expanded Stack of 2 pieces collapses when arrow keys used

  • Bug 2659577: ImageSaver paints Boards with no background black

  • Bug: Accidentally rejecting perfectly valid mask images in ADC2 symbol sets

  • Bug: CounterDetailViewer calls Swing methods off EDT

  • Bug: CounterDetailViewer should not appear during piece drags

  • Image scaling is now 35% faster.

  • Map-edge autoscrolling is now smoother and more responsive.

For changes prior to 3.1.5, see the change log.

The recommended minimum Java version for VASSAL 3.1 has changed. A bug in
versions of Java prior to 1.5.0_08 (a.k.a. Java 5 update 8) prevents some
images from loading properly. We now recommend that anyone using a version
of Java older than 1.5.0_08 upgrade to at least 1.5.0_08.

For Linux and Mac users, this should require no action on your part. Windows
users installing VASSAL 3.1.8 with the Windows installer will be prompted to
update Java if what they have is older than 1.5.0_08.

For feature changes from 3.0 to 3.1, see the release notes for 3.1.0.

Please report all bugs, even if they are bugs which you’ve already reported
against other versions. We take your bug reports very seriously—they’re
the reason we’re able to find and fix bugs.

Help us test

Should you find any problems/oddities/bugs, please tell us so that we can
fix them for the next release of VASSAL.

Report bugs here in the Technical Support & Bugs category at the VASSAL

or by email to


Joel Uckelman, for The VASSAL Team

We’ve found an unintended side-effect of one of the bugfixes in 3.1.8, so we’ve taken it down and will be back with 3.1.9 in a day or two. Our appologies for the inconvenience.


Fixed in swampwallaby-3.1@5835.

If you can build an svn version, I’ll get soft-bug to test it for us.


Messages mailing list …

Post generated using Mail2Forum (

Thus spake “Brent Easton”:

Merged to 3.1@5836.

I’ve uploaded 3.1.9-svn5837 for you.


Messages mailing list …

Post generated using Mail2Forum (

Thus spake “Brent Easton”:

BTW, I threw in a fix for Bug 2817613 also. (The problem was something
which could only happen in modules which use the old Zoomer attributes
and had the furthest zoomed-out level set as the initial one.)


Messages mailing list …

Post generated using Mail2Forum (

I put my VETO for * Bug 2813765: Can’t always Peek at a card, even though you can unmask it

I have sent you my vision about the consequences about changing a “Concept” which has a big impact about how Vassal Designer have used it to allow :

  • Auction system : Revealed or Masked
  • How to manage Revealed / Masked cards and Ownership in Boardgames design.

When i have firstly declared a big bug for 3.1.8 i was not primary taken seriously … Then now i ask to remove this till a real analysis about how to provide compatibility with previous modules is done .

Please consider that this is a big impact for previous modules already done, and give us a solution instead of putting this like this.

I only ask for compatibility and real analysis, i do not want a mandatory new “Concept” which oblige to modify modules with too less possibility in design that was provided before.

I can help you if you want help …



Hi Grégory,

We certainly do take your comments seriously. I’m sorry if you feel we don’t.

I am happy for bug 2813765 to be dropped while we discuss this further.

Your argument about backward compatibility is valid, I just did not realise that anyone seriously depended on the unmaskability of opponents pieces. The correct way to introduce this functionality is probably to add a further GlobalOption ‘Allow non-owners to peek at masked pieces’.

HOWEVER, If you are creating modules that depend on the GlobalOptions setting of ‘Allow non-owners to unmask pieces’ = Always, then they are seriously flawed and any player can cheat by looking at any time at supposedly masked cards, with no warning to other players, even with bug 2813765 removed.

There are other ways to implement the sort of functionality you are after that correctly hide the identity of hidden cards from all players until the appropriate time. For example, See the ‘Random placement of treasures’ thread immediately following this one.

Personally, I believe the ‘Allow non-owners to unmask pieces’ option is about as useful as mammary glands on an adult male bovine and should be completely removed from Vassal.

I think we need some detailed discussion on the subject of ‘Storing and Revealing information hidden to all players in a Vassal module’ in a separate thread. It is a subject that comes up regularly and is not well handled within Vassal at the moment.


*********** REPLY SEPARATOR ***********

On 10/07/2009 at 9:59 AM soft-bug wrote:

Brent Easton
University of Western Sydney

Messages mailing list …

Post generated using Mail2Forum (

Thus spake “Brent Easton”:

So what should I do w/r/t releasing 3.1.9? Roll back both patches?


Messages mailing list …

Post generated using Mail2Forum (

Yes, I think that is best. Roll them both out and release to resolve the AreaofEffect bug.


Messages mailing list …

Post generated using Mail2Forum (


Your email is bouncing, I have PM’d you.


Messages mailing list …

Post generated using Mail2Forum (

Thus spake “Brent Easton”:

Done. I’ve released 3.1.9 without the patches for Bug 2813765.


Messages mailing list …

Post generated using Mail2Forum (