BlueMap

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

Full Changelog

https://github.com/BlueMap-Minecraft/BlueMap/releases/tag/v5.21