Filter loader...
Filter versions...

Highlights / Notes

Copper-chests and coppergolem statues models.
And reverted the integrated webserver changes from 5.12.
(There are some issues with using virtual-threads in combination with a database-storage that could lead to the webserver becoming unresponsive. This issue is resolved when using Java 24+ but as long as BlueMap still supports Java 21 we revert to the previous webserver implementation)

Upgrading from 5.12

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

Changelog since 5.12

  • Added models for copper-chests
  • Added models for coppergolem statues
  • Added models for hanging-signs that are attached=false
  • Added models for all pale-oak signs
  • Reverted the integrated webserver changes from 5.12
  • Fixed a loading error on forge 1.21.9+ (#743)
  • Added a cooldown-time when updating the same region-file multiple times in a row
  • Also scan the item folder in resourcepacks for block-models (fixes a compatibillity issues with ItemsAdder resourcepacks)
  • Fixed and improved several small code-issues

Full Changelog

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

Highlights / Notes

This is a one-off backport of BlueMap 5.12 for Forge 1.20 - 1.20.4 (including 1.20.1) due to very high demand.

This Version needs Java 21 to run!
Forge and most mod's should be able to run on Java 21 instead of Java 17. If you can't use Java 21, then you need to use BlueMap 5.3 instead.

Upgrading from 5.3

The previous BlueMap version that supported Forge 1.20.x was 5.3, so you are likely upgrading from there.

There have been a ton of changes and new config values etc., so I really recommend you to do a full clean installation of BlueMap:

  • Stop the server
  • Make a backup
  • Delete your current ./mods/bluemap-x-yz.jar
  • Delete the ./config/bluemap
  • Delete the ./bluemap directory
  • Put the new bluemap-5.12-mc1.20-6-forge.jar in the ./mods folder
  • Start the server
  • Reconfigure BlueMap again, using the newly generated configs
    You can keep the configs from your backup aside, to help you with the porting
  • run /bluemap reload

If you don't want to do a clean installation to keep your currently rendered maps, you need to follow the upgrade-steps from these changelogs:

Changelog

For changelogs please see: https://github.com/BlueMap-Minecraft/BlueMap/releases

Highlights / Notes

Full 1.21.9 support, rework of the integrated webserver and more bugfixes and improvements!

Upgrading from 5.11

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

Changelog since 5.11

  • Updated fabric-implementation to 1.21.9
  • Rework of the integrated webserver from NIO to using Virtual-Threads, improving performance and maintainability
  • Added remapping chain -> iron_chain for RP version 67 for improved backwards-compatibility
  • Added support for block-properties in the block-colors config
  • Added support for addon dependencies and soft-dependencies (#730)
  • Pushed BlueMapAPI to 2.7.6
  • Improved logging for region/chunk loading errors
  • Fixed paper reading the wrong minecraft version id when not on a release version (Snapshots,Pre-Releases,RCs)
  • Fixed element default UV calculation, fixing the appearance of the cauldron and cactus-flowerpot
  • Fixed melon- and pumpkin-stems not being colored correctly (#734)
  • Fixed inside-out cubes not working, fixing the appearance of all spawner-blocks
  • Fixed wrong tile coordinates being displayed in /bluemap debug map ... command
  • Fixed inheritance of ambient-occlusion property from parent block-model (thanks to Uiniel, #729)
  • Fixed webserver incorrectly handling absolute form of HTTP "path" (#737)
  • Fixed legacy config error not showing the problematic config file

Full Changelog

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

Highlights / Notes

With Render-Masks it is now possible to limit your map render to all kinds of shapes and perfectly control what you want to be visible on the map, and which regions should remain hidden.

Upgrading from 5.10

  • Replace the bluemap.jar-file with the new one
  • Delete your <webroot>/index.html to make bluemap update the webapp
  • You will need to update your map configs!
    • Find the section with min-x, max-x, min-z, max-z, min-y and max-y in your map config file, e.g.:
      #min-x: -4000
      #max-x: 4000
      #min-z: -4000
      #max-z: 4000
      #min-y: 50
      max-y: 90
      
      and add render-mask: [ { before, and ] } after the section, e.g. like this:
      render-mask: [ 
        {
          #min-x: -4000
          #max-x: 4000
          #min-z: -4000
          #max-z: 4000
          #min-y: 50
          max-y: 90
        }
      ]
      
      -> here is a video-example
    • Optionally, you can add the new edge-light-strength: 15 property to your map config as well

Changelog since 5.10

  • Added a list of render-masks to the map-configs, replacing the previous min-x, max-z, etc.., properties (#81)
  • Added edge-light-strength to the map-configs to control the lighting of map-edges if render-edges is enabled
  • Custom dimensions are now ordered last by default
  • Improved structure and comments of the default map-configs
  • Added support for minor pack-versions introduced in Minecraft Snapshot 25w31a
  • Fixed lily_pad's having no tint color (#727)
  • Fixed error if biomes water-color has alpha (#715)
  • Updated bluemap-api to 2.7.5

Full Changelog

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


Project members

BlueColored

Owner

Details

Licensed MIT
Published 3 years ago
Updated 10 days ago