MapTool 1.11.0 Alpha Build 1

Warning Alpha Release, please do not use for your regular gaming, or use it to modify maps you don't have a backup of!

What's Changed

• Fixes for several macro functions where name was case sensitive #3011 #3013
• implement terrain VBL #2755
• Preference Dialog Fixes #3063
• More error handling / clean up for Universal VTT import #3061
• Disable Direct 3D by default #3065
• Space/Enter will no long advance initiative #3066
• show / hide / get visibility of overlay macro functions #2431
• Add initial support for Add-Ons #1346 #1348 (see also https://rptools-doc.craigs-stuff.net/blog/add-on-libraries)

NOTE: if you experiment with the terrain VBL feature be sure to set the VBL mode back to plain VBL or MBL before exiting MT 1.11.0 or previous MapTool versions will not be able to start.

Full Changelog: 1.10.1...1.11.0-alpha.1

1.10.3: Fix for NPE on exit with no connection

Before uninstalling any old version, if you have saved your campaign files, logs, or anything you want to keep under the directory structure where MapTool is installed please copy them elsewhere beforehand. It is also a good idea to always have backups.

Note: Do not install over the top of an old version, either install into a new directory or remove the old version.

Bug Fix release for MapTool 1.10.3

What's Changed

• Fix for issue some windows users are experiencing which does not allow them to exit MapTool.

Bug Fix release for MapTool 1.10.2

What's Changed

• Fix for webp images not being displayed in html dialog/frame when using getTokenImage(), tblImg() as source

Bug Fix release for MapTool 1.10.1

What's Changed

• Fix for size modifier in getTokenImage()
• Properly return numeric values from JavaScript UDFs
• Update README.md Github introduction to MapTool
• New translations updates

See ChangeLog for v1.10.1 for more details and links to individual issues.

Feature release for MapTool 1.10.0

Highlights

• Significantly reduced startup time for MapTool with a large asset cache under Windows.
• User database with encrypted passwords and public key support for logging in to MapTool servers plus macro functions for accessing database.
• WebRTC supported for connecting to servers without using port-forwarding.
• More support for JavaScript through GraalVM-JS.
• Access HTML/CSS/JS content on lib:tokens via URI from dialogs/frames/overlays plus new macro functions to open dialogs/frames/overlays using URIs.
• GIF anim support in dialogs, frame5 and overlays.
• More performance improvements for Fog of War handling.
• New macro functions, bug fixes and localization translations.

See ChangeLog for v1.10.0 for more details and links to individual issues.

Platform Notes

We strongly encourage you to use the installer format for your operating system. The JAR file should only by used by advanced users comfortable with installing Java releases. It requires a working Java 16 install with JavaFX on your system in order to use it.

Download one of the assets listed below. Each platform has options for which file to download, as described below.

• Windows: Use either .msi (recommended) or .exe.
  • Recommend that previous 1.10 versions be uninstalled prior to installing new one. If you have made modifications to the MapTool.cfg file, make a backup so you can copy your changes into the new config file.
  • Do not install over older versions of MapTool.
  • We're seeing notes from Windows users that they double-click the icon after installing and no window appears. This seems to be an antivirus issue, so check your AV if you have this problem.
• Linux: Use either .deb or .rpm (depending on which packager your system uses).
  • The deb version installs under /opt/maptool/bin as MapTool.
• macOS: Use either .pkg (recommended) or .dmg.
  • On macOS, to run the app the first time after installation, hold Ctrl while clicking the icon and continue to hold Ctrl while choosing Open, then choose to open the application (this is part of Apple's approach when dealing with an unidentified developer).
  • The macOS Gatekeeper may flag the DMG file as broken. See this issue for more details.

Full Changelog: 1.10.2...1.10.3

MapTool 1.10.2

Before uninstalling any old version, if you have saved your campaign files, logs, or anything you want to keep under the directory structure where MapTool is installed please copy them elsewhere beforehand. It is also a good idea to always have backups.

Note: Do not install over the top of an old version, either install into a new directory or remove the old version.

Bug Fix release for MapTool 1.10.2

What's Changed

• Fix for webp images not being displayed in html dialog/frame when using getTokenImage(), tblImg() as source

Bug Fix release for MapTool 1.10.1

What's Changed

• Fix for size modifier in getTokenImage()
• Properly return numeric values from JavaScript UDFs
• Update README.md Github introduction to MapTool
• New translations updates

See ChangeLog for v1.10.1 for more details and links to individual issues.

Feature release for MapTool 1.10.0

Highlights

• Significantly reduced startup time for MapTool with a large asset cache under Windows.
• User database with encrypted passwords and public key support for logging in to MapTool servers plus macro functions for accessing database.
• WebRTC supported for connecting to servers without using port-forwarding.
• More support for JavaScript through GraalVM-JS.
• Access HTML/CSS/JS content on lib:tokens via URI from dialogs/frames/overlays plus new macro functions to open dialogs/frames/overlays using URIs.
• GIF anim support in dialogs, frame5 and overlays.
• More performance improvements for Fog of War handling.
• New macro functions, bug fixes and localization translations.

See ChangeLog for v1.10.0 for more details and links to individual issues.

Platform Notes

We strongly encourage you to use the installer format for your operating system. The JAR file should only by used by advanced users comfortable with installing Java releases. It requires a working Java 16 install with JavaFX on your system in order to use it.

Download one of the assets listed below. Each platform has options for which file to download, as described below.

• Windows: Use either .msi (recommended) or .exe.
  • Recommend that previous 1.10 versions be uninstalled prior to installing new one. If you have made modifications to the MapTool.cfg file, make a backup so you can copy your changes into the new config file.
  • Do not install over older versions of MapTool.
  • We're seeing notes from Windows users that they double-click the icon after installing and no window appears. This seems to be an antivirus issue, so check your AV if you have this problem.
• Linux: Use either .deb or .rpm (depending on which packager your system uses).
  • The deb version installs under /opt/maptool/bin as MapTool.
• macOS: Use either .pkg (recommended) or .dmg.
  • On macOS, to run the app the first time after installation, hold Ctrl while clicking the icon and continue to hold Ctrl while choosing Open, then choose to open the application (this is part of Apple's approach when dealing with an unidentified developer).
  • The macOS Gatekeeper may flag the DMG file as broken. See this issue for more details.

1.10.1

Note: Please either remove old version or install into a new directory, do not attempt to overwrite a previous version of MapTool with the new version.

Bug Fix release for MapTool 1.10.1

What's Changed

• Fix for size modifier in getTokenImage()
• Properly return numeric values from JavaScript UDFs
• Update README.md Github introduction to MapTool
• New translations updates

See ChangeLog for v1.10.1 for more details and links to individual issues.

Feature release for MapTool 1.10.0

Highlights

• Significantly reduced startup time for MapTool with a large asset cache under Windows.
• User database with encrypted passwords and public key support for logging in to MapTool servers plus macro functions for accessing database.
• WebRTC supported for connecting to servers without using port-forwarding.
• More support for JavaScript through GraalVM-JS.
• Access HTML/CSS/JS content on lib:tokens via URI from dialogs/frames/overlays plus new macro functions to open dialogs/frames/overlays using URIs.
• GIF anim support in dialogs, frame5 and overlays.
• More performance improvements for Fog of War handling.
• New macro functions, bug fixes and localization translations.

See ChangeLog for v1.10.0 for more details and links to individual issues.

Platform Notes

We strongly encourage you to use the installer format for your operating system. The JAR file should only by used by advanced users comfortable with installing Java releases. It requires a working Java 16 install with JavaFX on your system in order to use it.

Download one of the assets listed below. Each platform has options for which file to download, as described below.

• Windows: Use either .msi (recommended) or .exe.
  • Recommend that previous 1.10 versions be uninstalled prior to installing new one. If you have made modifications to the MapTool.cfg file, make a backup so you can copy your changes into the new config file.
  • Do not install over older versions of MapTool.
  • We're seeing notes from Windows users that they double-click the icon after installing and no window appears. This seems to be an antivirus issue, so check your AV if you have this problem.
• Linux: Use either .deb or .rpm (depending on which packager your system uses).
  • The deb version installs under /opt/maptool/bin as MapTool.
• macOS: Use either .pkg (recommended) or .dmg.
  • On macOS, to run the app the first time after installation, hold Ctrl while clicking the icon and continue to hold Ctrl while choosing Open, then choose to open the application (this is part of Apple's approach when dealing with an unidentified developer).
  • The macOS Gatekeeper may flag the DMG file as broken. See this issue for more details.

MapTool 1.10.0

Feature release for MapTool 1.10.

Highlights

• Significantly reduced startup time for MapTool with a large asset cache under Windows.
• User database with encrypted passwords and public key support for logging in to MapTool servers plus macro functions for accessing database.
• WebRTC supported for connecting to servers without using port-forwarding.
• More support for JavaScript through GraalVM-JS.
• Access HTML/CSS/JS content on lib:tokens via URI from dialogs/frames/overlays plus new macro functions to open dialogs/frames/overlays using URIs.
• GIF anim support in dialogs, frame5 and overlays.
• More performance improvements for Fog of War handling.
• New macro functions, bug fixes and localization translations.

See ChangeLog for v1.10.0 for more details and links to individual issues.

Platform Notes

We strongly encourage you to use the installer format for your operating system. The JAR file should only by used by advanced users comfortable with installing Java releases. It requires a working Java 16 install with JavaFX on your system in order to use it.

Download one of the assets listed below. Each platform has options for which file to download, as described below.

• Windows: Use either .msi (recommended) or .exe.
  • Recommend that previous 1.10 versions be uninstalled prior to installing new one. If you have made modifications to the MapTool.cfg file, make a backup so you can copy your changes into the new config file.
  • Do not install over older versions of MapTool.
  • We're seeing notes from Windows users that they double-click the icon after installing and no window appears. This seems to be an antivirus issue, so check your AV if you have this problem.
• Linux: Use either .deb or .rpm (depending on which packager your system uses).
  • The deb version installs under /opt/maptool/bin as MapTool.
• macOS: Use either .pkg (recommended) or .dmg.
  • On macOS, to run the app the first time after installation, hold Ctrl while clicking the icon and continue to hold Ctrl while choosing Open, then choose to open the application (this is part of Apple's approach when dealing with an unidentified developer).
  • The macOS Gatekeeper may flag the DMG file as broken. See this issue for more details.

MapTool 1.10.0 Beta 4

WebRTC

Beta Test 4 to test WebRTC changes in MapTool - This feature will allow player clients to connect with the server without requiring port-forwarding on the server end. To test both Server and Player clients must enable it via the Help menu -> Use WebRTC for communications...

Those users that were unable to configure the router that an ISP provided should give this a test.

User Passwords

Also part of this build is the initial per-user password database support. This can be enabled on the Start Server dialog. You will need to manually add the passwords.json file to your .maptool-rptools/config directory. You can create the file initially in plain text and MapTool will convert on server startup. Example passwords.json file:

{
	"passwords": [
		{
			"username": "GM",
			"password": "MothersMaidenName",
			"role": "GM"
		},
		{
			"username": "Player1",
			"password": "NotMyBirthday",
			"role": "Player"
		}
	]
}

See #2917 for more details.

MapTool 1.10.0 Beta 2

Beta 2 test build for WebRTC network changes in MapTool.

MapTool 1.10.0 Beta 1

Beta a for 1.10.0
Build contains significant under the hood changes to networking connection so needs some testing

MapTool 1.9.3

Bug fix release for MapTool 1.9.

Of particular note are several VBL/MBL performance fixes for complex maps plus a variety of QoL and functionality fixes.

See full ChangeLog for v1.9.3 for more details and links to individual issues.

Platform Notes

We strongly encourage you to use the installer format for your operating system. The JAR file should only by used by advanced users comfortable with installing Java releases. It requires a working Java 16 install with JavaFX on your system in order to use it.

Download one of the assets listed below. Each platform has options for which file to download, as described below.

• Windows: Use either .msi (recommended) or .exe.
  • Recommend that previous 1.9 versions be uninstalled prior to installing new one. If you have made modifications to the MapTool.cfg file, make a backup so you can copy your changes into the new config file.
  • Do not install over older versions of MapTool.
  • We're seeing notes from Windows users that they double-click the icon after installing and no window appears. This seems to be an antivirus issue, so check your AV if you have this problem.
• Linux: Use either .deb or .rpm (depending on which packager your system uses).
  • The deb version installs under /opt/maptool/bin as MapTool.
• macOS: Use either .pkg (recommended) or .dmg.
  • On macOS, to run the app the first time after installation, hold Ctrl while clicking the icon and continue to hold Ctrl while choosing Open, then choose to open the application (this is part of Apple's approach when dealing with an unidentified developer).
  • The macOS Gatekeeper may flag the DMG file as broken. See this issue for more details.

MapTool 1.9.2

Bug fix release. Missed one.

Bug Fixes

• #2749 Macro editor help missing entries for many functions. Most documented functions now have help.

See full ChangeLog for v1.9.0 for more details and links to individual issues.

Platform Notes

We strongly encourage you to use the installer format for your operating system. The JAR file should only by used by advanced users comfortable with installing Java releases. It requires a working Java 16 install with JavaFX on your system in order to use it.

Download one of the assets listed below. Each platform has options for which file to download, as described below.

• Windows: Use either .msi (recommended) or .exe.
  • We're seeing notes from Windows users that they double-click the icon after installing and no window appears. This seems to be an antivirus issue, so check your AV if you have this problem.
• Linux: Use either .deb or .rpm (depending on which packager your system uses).
  • The deb version installs under /opt/maptool/bin as MapTool.
• macOS: Use either .pkg (recommended) or .dmg.
  • On macOS, to run the app the first time after installation, hold Ctrl while clicking the icon and continue to hold Ctrl while choosing Open, then choose to open the application (this is part of Apple's approach when dealing with an unidentified developer).
  • The macOS Gatekeeper may flag the DMG file as broken. See this issue for more details.