MapTool 188.8.131.52 is available for download from http://www.rptools.net/ by clicking on the Download link in the top toolbar.
The commit log is available via the GitHub page but many of the changes were related to the build system and automation; I've tried to separate them in the spoiler area, below, but no guarantees. (MapTool 184.108.40.206 was released Jul 2nd, 2016 so commit entries prior to that apply to the previous build.)
Major fixes include the token ID bug (where tokens contain all digits and are converted to numbers) and a problem with Meta-I not clearing FoW properly (Ctrl-I on Windows and Unix, Cmd-I on macOS).
Code: Select all
Author: Frank Edwards <[email protected]>
Windows support files added; README cleanup
Truncate tool tip text on the Properties panel of the Edit Token
Dialog so that MT doesn't crash (appears to be a JIDE bug?).
If the property value is > 100 characters in length, the tool
tip is truncated to the first 100 characters, plus "..."
Fix for drag/drop on OS X Java 1.8u72+:
Somewhere around 1.8u60 it seems Oracle added support for
additional drag/drop data flavors. OS X now has flavors it
didn't before and it broke. The tweak is a better implementation
overall as it allows a data flavor to match but the import
to fail, yet the next data flavor will still be attempted
(previously it would not proceed to the next flavor on failure).
Author: Jamz <[email protected]>
Enhancement Fix for 220.127.116.11
o Removed hard coded paths from CreateVersionedInstallSplash (left
relative path default).
o Updated build.gradle to pass paths to CreateVersionedInstallSplash
based on gradle.properties & getVersionName()
optional and skipped if -web_output is not passed to
o Gradle fix to properly copy & update launch.properties file during
o jWrapper jar updated to 0049034758
o Gradle enhancement to rename and copy completed jWrapper
installations to target directory
o Gradle enhancement to run new class CreateVersionedInstallSplash
which creates a matching "Installing" splash image which jWrapper embeds
and uses in it's installation.
Bug Fix - Exposing Visible Area
- Reported @ http://forums.rptools.net/viewtopic.php?f=86&t=26960
- ctrl+i was not working if "FoW: Expose only at waypoints" option was
- build.gradle fixed missing "i" @ line 419
Bug Fix - Default Lumens & Always Visible rendering
Bug Fix - "Always Visible" tokens rendering twice
- Fixes issue where tokens that were marked as "Always Visible" were
rendering twice and tokens with transparency would show up darker as
they overlaid each other.
Bug Fix - Default Lumens
- Fixes default lights to setting of lumens=0
- Adds lumens to Light Format help text with explanation and examples.
Updated Sample Lights as well with lumens settings.
Author: uthin <[email protected]>
Small fix to facing arrow; original forum subject: “Unwanted
Token Facing Indicators”
Author: David Rawlins <[email protected]>
Merge pull request #117 from Jaggeroth/master
Author: Frank Edwards <[email protected]>
Updated documentation for build system
Moved 'createLaunchPropertiesFile' into launcher
Added a section to the end of 'processResources' that did everything
that used to be in the other task, plus added a line of output
confirming that the new file was created.
Add 'launch.properties' dependency to launcher
Removed 'launch.properties' and added that name to .gitignore, since
it's a generated file now.
Clean up launcher directory and 'build.gradle'
Leftover files for the launcher were removed. The gradle build
file had references to 'mt.cfg' replaced with 'launch.properties'.
The jwrapper template was updated with another variable
(mainClassName). The launch.properties template was cleaned
up and had a newline added to the last line.
Added top-level readme file for MapTool repo
GitHub issue 37:
Now catching exceptions from the heartbeat thread. Treating
them as transient issues, but we notify the chat window of
the system hosting the server and all GMs, providing the
server's IP address and port number. If we decide the messages
happen too frequently, it's easy to change the backoff by
changing the WARNING_TIME.
The announcement for 18.104.22.168 is here and 22.214.171.124 just got a brief note in about the fourth posting or so.