Tags
Creators
Details
5.29-neoforge
Compatibility
Changes
Highlights / Notes
More reliable map-updates and map-storage: BlueMap now also detects world-changes that did not trigger a filesystem event, and writes to the map-storage are now transactional. Plus some performance improvements and fixes.
Upgrading from 5.28
- Replace the
bluemap.jar-file with the new one - Delete your
<webroot>/index.htmlto make bluemap update the webapp - (Optional) Add the following lines to your
core.conf:# The interval in minutes at which BlueMap checks all region-files for changes. # This is a relatively cheap check IN ADDITION to watching for file-system events, in case those are not reliable. # For HUGE worlds (> 10000 region-files) you might want to consider increasing the interval or disabling this to reduce cpu and file-read load. # Set to 0 to disable. # Default is 5 region-file-check-interval: 5
Changelog since 5.28
- Added a
region-file-check-intervaloption to thecore.conf, BlueMap now regularly checks all region-files for changes to detect world-changes that failed to trigger a filesystem event - Made all writes to the map-storage transactional, errors while writing are now much less likely to corrupt map-files
- Improved render performance by avoiding some unnecessary allocations for every rendered block (thanks to @Hexay, #881)
- Updated the Portuguese translation (thanks to @ComanderP, #871)
- Fixed lowres-tile changes getting lost if a tile was changed while it was being saved (race-condition) (#883)
- Fixed some live tile-updates in the webapp being loaded from the cache instead of the server
- Fixed the quality-parameter of
Accept-Encodingheaders not being recognized correctly (#882) - Fixed the full-update timer not being stopped correctly on a BlueMap reload
- Fixed some more streams not being closed correctly
- Fixed moving files failing sometimes on Windows(-Server)
Full Changelog
https://github.com/BlueMap-Minecraft/BlueMap/releases/tag/v5.29
Projects on Modrinth are automatically available through a Maven repository for use with JVM build tools such as Gradle. To learn more about the Modrinth Maven API, click here.
Note: When available, you should use the creator's maven repo instead as it will have transitive dependency information that the Modrinth Maven API does not. You may also end up with duplicate dependencies if you use a mix of Modrinth and non-Modrinth Maven repositories for your dependencies, because the group identifier will be different when served through the Modrinth Maven API.
Maven coordinates:
Version ID:
build.gradle:
repositories {
exclusiveContent {
forRepository {
maven {
name = "Modrinth"
url = "https://api.modrinth.com/maven"
}
}
// forRepositories(fg.repository) // Uncomment when using ForgeGradle
filter {
includeGroup "maven.modrinth"
}
}
}
// Standard Gradle dependency
dependencies {
implementation "maven.modrinth:swbUV1cr:kknWg6rw"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:swbUV1cr:kknWg6rw"
}

