[vassalengine-announce] VASSAL 3.1.13 released

[Joel U. <uck...@no...>]

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

*********************
Download
*********************

For Linux:

  http://downloads.sourceforge.net/vassalengine/VASSAL-3.1.13-linux.tar.bz2

For Mac OS X:

  http://downloads.sourceforge.net/vassalengine/VASSAL-3.1.13-macosx.dmg

For Windows:

  http://downloads.sourceforge.net/vassalengine/VASSAL-3.1.13-windows.exe

For other operating systems:

  http://downloads.sourceforge.net/vassalengine/VASSAL-3.1.13-other.zip

Source code:

  http://downloads.sourceforge.net/vassalengine/VASSAL-3.1.13-src.zip


*********************
Changes since 3.1.0
*********************

The following bugs are fixed in 3.1.13:

* Bug 2902254: NPE in {Player,Editor}.PromptLaunchAction.actionPerformed()
* Bug 2900930: Trigger Actions not disabled when Property Expression fails
* Bug 2899561: Module is marked 'dirty' as soon as it is opened.
* Bug 2888918: IndexOutOfBoundsException in SpecialDie.getImageName()
* Bug 2817148: NPE in BasicLogger.write() - Trying to log to closed logfile
* Bug 2816987: IndexOutOfBoundsException in SpecialDie.getTextValue()
* Bug: Removed spurious Vengine.jar from Launch4j classpath.
* Bug: Confusing error message on attempt to run without unzipping on Windows

The following bugs are fixed in 3.1.12:

* Bug 2873163: Cannot save module after adding bad SVG image
* Bug 2871323: NPE in ImageIOException
* Bug 2844284: Global key cmd "Suppress individual reports" bug
* Bug 2835838: bad transparency for Type 2 Truecolor PNGs
* Bug: DataArchive.getImageNameSet() returns empty string for images dir

New in 3.1.11:

* The Mac OS X bundle has been updated to run with a 64-bit JVM if one
is available.

The following bugs are fixed in 3.1.11:

* Bug 2849638: StackOverflowError - Return to Deck and Map auto-move
* Bug 2844284: GKC does not "Suppress individual reports" across maps
* Bug 2839916: Player with no Name does not appear properly on Server (II)
* Bug 2817002: UnsatisfiedLinkError in JNA on some versions of Mac OS X

New in 3.1.10:

* VASSAL has a new User's Guide! You can view the User's Guide by selecting
"User's Guide" from the Help menu in any of VASSAL's components.

The following bugs are fixed in 3.1.10:

* Bug 2839923: Users not showing an IP address
* Bug 2839916: Player with no Name does not appear properly on Server
* Bug 2838915: ArrayIndexOutOfBoundsException in ReportState.myKeyEvent()
* Bug 2835827: Use images with premultiplied alpha on Macs
* Bug 2835735: ArrayIndexOutOfBoundsException in PieceDefiner
* Bug 2833840: IllegalArgumentException in FileChooser with Java 1.5
* Bug 2832499: IllegalArgumentException in PropertySheet
* Bug 2832472: Inventory: Pieces appear multiple times  
* Bug 2832471: Inventory: Label for folders cannot contain properties  
* Bug 2827225: NPE in NodeClient.doInvite()
* Bug 2826715: NPE in GlobalProperty.encode()
* Bug 2825175: Game Piece Inventory: "Draw Piece Images?" option is broken
* Bug 2817139: NPE in RangeFilter ctor
* Bug 2827113: ArrayIndexOutOfBoundsException in Embellishment
* Bug 2817070: PropertySheet saves empty hotkey as null
* Bug 2756330: StackOverflowError in BasicPiece.mySetType()
* Bug 2735630: IllegalArgumentException due to non-UTF8 ZipEntry names
* Bug 2259361: NPE in FreeRotator - Counter moved or deleted during rotate 

For changes prior to 3.1.10, 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.13 with the Windows installer will be prompted to
update Java if what they have is older than 1.5.0_08. If you are a Windows
user, you might also need to restart your computer after installing a Java
update in order for Java programs to work properly.

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
forums:

http://vassalengine.org/forums/viewforum.php?f=3

or by email to uck...@no....


Cheers,

Joel Uckelman, for The VASSAL Team

-- 
J.