Highlights / Notes

Improvements to SQL-storage (especially SQLite performance), general performance improvements and some fixes.

Upgrading from 5.27

• Replace the bluemap.jar-file with the new one
• Delete your <webroot>/index.html to make bluemap update the webapp
• (Optional) Update the additional-headers in your webserver.conf to the new defaults:

  additional-headers: {
    "Cache-Control": "public, max-age=86400, stale-if-error=604800"
    "CDN-Cache-Control": "max-age=60"
  }

• (Optional) Add the following lines to your SQL storage-configs (e.g. storages/sql.conf):

  # SQL-statements that are executed once on every new connection to the database.
  # Leaving this commented out means that BlueMap uses sensible defaults for the used sql-dialect.
  #connection-init-sql: [
  #  "PRAGMA journal_mode = WAL"
  #  "PRAGMA synchronous = NORMAL"
  #  "PRAGMA busy_timeout = 30000"
  #  "PRAGMA foreign_keys = ON"
  #]
  
  # The prefix that is prepended to the names of all tables BlueMap creates and uses.
  # Only lowercase letters (a-z), digits (0-9) and underscores (_) are allowed, with a maximum length of 32 characters.
  # Changing this value on an existing setup will NOT rename existing tables or move data, BlueMap will create new, empty ones instead.
  # Default is: "bluemap_"
  #table-prefix: "bluemap_"

Changelog since 5.27

• Added a table-prefix option to the SQL-storage config to change the names of the tables BlueMap uses (#457)
• Added a connection-init-sql option to the SQL-storage config, and BlueMap now uses sensible defaults for each dialect (e.g. WAL-mode for SQLite)
• Changed the default webserver additional-headers to use the standard CDN-Cache-Control header instead of Cloudflare-CDN-Cache-Control (thanks to @w00000dy, #870)
• Improved map-update performance by caching render-state data and parsing block-states faster
• Improved compatibility with some filesystems
• Fixed some streams not being closed correctly
• Fixed another issue with loading saved render-tasks
• Fixed the time of the last full map-update not being saved, which could cause early full updates after a restart
• Fixed an error when full-update-interval is set to 0 or a negative value
• Fixed marker colors being displayed in the wrong color-space

Targets:

Java: 25
BlueMapAPI: 2.8.1

Highlights / Notes

Hotfix for 5.26.

Upgrading from 5.26 or 5.25

• Replace the bluemap.jar-file with the new one
• Delete your <webroot>/index.html to make bluemap update the webapp

Upgrading from 5.24

• Replace the bluemap.jar-file with the new one
• Delete your <webroot>/index.html to make bluemap update the webapp
• Add the following lines to your webserver.conf:

  # Additional headers the webserver should include in the responses it sends.
  additional-headers: {
    "Cache-Control": "public, max-age=86400"
  }

Changelog since 5.26

• Fixed the map shifting when the camera crosses 10000-block boundaries

Targets:

Java: 25
BlueMapAPI: 2.8.0

Highlights / Notes

Hotfix for 5.25.

Upgrading from 5.25

• Replace the bluemap.jar-file with the new one
• Delete your <webroot>/index.html to make bluemap update the webapp

Upgrading from 5.24

• Replace the bluemap.jar-file with the new one
• Delete your <webroot>/index.html to make bluemap update the webapp
• Add the following lines to your webserver.conf:

  # Additional headers the webserver should include in the responses it sends.
  additional-headers: {
    "Cache-Control": "public, max-age=86400"
  }

Changelog since 5.25

• Fixed the line-shader (used for markers/lines on the map) not being compatible with the newer three.js version
• Fixed the additional-headers webserver config also overriding the cache-control headers of live-data and SSE responses

Targets:

Java: 25
BlueMapAPI: 2.8.0

Highlights / Notes

A smaller release focused on fixes and dependency updates, plus improved swamp-colors and a new option to add custom webserver response headers.

Upgrading from 5.24

• Replace the bluemap.jar-file with the new one
• Delete your <webroot>/index.html to make bluemap update the webapp
• Add the following lines to your webserver.conf:

  # Additional headers the webserver should include in the responses it sends.
  additional-headers: {
    "Cache-Control": "public, max-age=86400"
  }

Changelog since 5.24

• Added an additional-headers webserver config option to add custom HTTP headers to served map/file resources (thanks to @iCiaran, #862)
• Updated a bunch of libraries and dependencies
• Fixed incorrect swamp grass color (was missing its noise pattern)
• Fixed default-config generation error on Windows
• Fixed players sometimes disappearing when write-players-interval is used

Targets:

Java: 25
BlueMapAPI: 2.8.0

Highlights / Notes

Adds compatibility with Minecraft 26.3 worlds, plus a handful of fixes and improvements.

Upgrading from 5.23

• Replace the bluemap.jar-file with the new one

Changelog since 5.23

• Added support for Minecraft 26.3 worlds
• Resolve default blockstates for 26.3+ worlds via data/<namespace>/defaultBlockstates.json
• SSE connections now send periodic keepalive messages to stop idle connections from timing out (thanks to @pR0Ps, #829)
• Updated Polish translation (thanks to @alliewegner, #832)
• Bumped js-yaml from 4.3.0 to 4.3.1 (#831)
• Fixed Region-update tasks with no changes not immediately freeing their memory
• Fixed BlueMap scheduler not running as a daemon thread
• Fixed webserver request-handlers not properly closing when BlueMap unloads
• Fixed the storage command sometimes not recognizing loaded maps correctly
• Fixed an error when tasks sometimes not saving/loading correctly (again)
• Fixed an error when updating players before BlueMap is fully loaded
• Fixed entity rotation (if there is an addon that adds entity models)

Targets:

Java: 25
BlueMapAPI: 2.8.0

Highlights / Notes

The integrated webserver now pushes markers and freshly rendered tile-updates to connected webapps using SSE.
And some more fixes and smaller improvements.

Upgrading from 5.22

• Replace the bluemap.jar-file with the new one
• Delete your <webroot>/index.html to make bluemap update the webapp

Optionally:

• Add the following lines to your webserver.conf:

  # Whether to use Server-Sent Events (SSE) for pushing tile and marker-updates to the connected clients.
  # Default is true
  sse-enabled: true

• Add the following lines to your webapp.conf:

  # This will configure the webapp to request the map-tiles compressed and decompress them manually.
  # Enable this only if you intend to host the webapp statically, with an external webserver without additional configuration.
  # Default is "false"
  #client-decompression: true

Changelog since 5.22

• Use Server-sent events to push updates for map-tiles, players, and markers (optional, thanks to @pR0Ps, #819)
• Added webapp-option to decompress tiles on the client, making it possible to host the webapp statically (thanks to @fechan, #815)
• No longer delete the whole map if no region-files exist (map might be configured incorrectly)
• Try to resolve symlinks when loading resources
• Added (usually hidden) config for dimension-type to fix paper-api added worlds
• Removed native linear region format support, use the linear-addon instead
• Track full-update-interval per-map instead of globally
• Fixed race-condition when saving lowres-tiles sometimes corrupting them (#821)
• Fixed live-player-markers config not being respected
• Fixed worlds with / in dimension key not being detected correctly on paper
• Fixed tasks sometimes not saving/loading correctly
• Fixed in-memory region-update-timestamps not resetting on purge

Targets:

Java: 25
BlueMapAPI: 2.8.0

Highlights / Notes

Fix for a map-breaking bug in 5.21: update directly to this version, skip version 5.21!

Upgrading from 5.20 (and 5.21)

• Replace the bluemap.jar-file with the new one
• Move the full-update-interval and the update-cooldown settings from your plugin.conf into your core.conf

This update contains some internal changes which might break some BlueMap-Addons that work with custom block-renderers.
-> Make sure to check if your addons need to be updated.

Changelog since 5.21

• Fixed an issue causing the textures of maps from previous versions to be corrupted

Targets:

Java: 25
BlueMapAPI: 2.8.0

Highlights / Notes

• Minecraft 26.2 support
• Changes to how map-updates are scheduled. Render-Tasks now persist over restarts/reloads

Upgrading from 5.20

• Replace the bluemap.jar-file with the new one
• Move the full-update-interval and the update-cooldown settings from your plugin.conf into your core.conf

This update contains some internal changes which might break some BlueMap-Addons that work with custom block-renderers.
-> Make sure to check if your addons need to be updated.

Changelog since 5.20

• Updated resource-extensions to account for 26.2 bed and sign changes (-> 26.2 support)
• BlueMap now keeps track of when it last updated which region-file and uses this information to sort it's update-tasks.
  This makes sure that no matter how slow the update-process is in comparison to the world-changes,
  BlueMap will always have eventually updated each region-file.
• BlueMap now saves render-tasks and loads them when it restarts or reloads
• BlueMap no longer updates all maps each time it loads. Instead, it persists the last full-update time
  and schedules full map-updates based on the full-update-interval config
• Moved update-cooldown and full-update-interval configs from plugin.conf to core.conf
• Added /bluemap tasks cancel all command to cancel all render-tasks at once
• Updated API to 2.8.0
• Reworked block-color calculation, added a registry for addons and
  the ability to configure custom color-map textures in the blockColors.json
• Re-enabled support for fabric-pemission-api
• Skin-Profile requests now use the un-dashed UUID format (aligning with mojang-default)
• Enhanced debug-dump with registry-information
• Added version information to the debug-log
• Fixed an issue with paper not loading custom dimension information correctly
• Fixed skin-download config doing nothing
• Fixed potential error when trying to load an entity-chunk with a formatted CustomName

Targets:

Java: 25
BlueMapAPI: 2.8.0

Highlights / Notes

This version fixes some bugs with the previous release.

Upgrading from 5.19

• Replace the bluemap.jar-file with the new one

Changelog since 5.19

• Fixed a bug that caused BlueMap to no longer be able to load worlds with the old (pre 26.1) format
• Fixed a bug causing some cases of high cpu-usage due to busy-waiting for region-folders to exist
• Fixed a bug where the webserver is not closing active connections when reloading bluemap
• Improved debug-dump with some more information

Targets:

Java: 25
BlueMapAPI: 2.7.8

Highlights / Notes

This version fixes two issues caused by a breaking change in the newest Paper builds for 26.1.1.

Upgrading from 5.18

• Replace the bluemap.jar-file with the new one

Changelog since 5.18

• Fixed BlueMap generating the wrong world-paths in the default map-configs on the latest paper builds
• Fixed BlueMap not displaying player-markers on the latest paper builds
• Fixed worldfolder resolve logic in the spigot implementation to better support the newest paper builds and hybrids

Targets:

Java: 25
BlueMapAPI: 2.7.8