Tags
Creators
Details
5.23-forge
Compatibility
Changes
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.htmlto 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-typeto 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
Full Changelog
https://github.com/BlueMap-Minecraft/BlueMap/releases/tag/v5.23
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:gJpRIUGn"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:swbUV1cr:gJpRIUGn"
}

