Tags
Creators
Details
All versions
5.16-spigot
Release
5.16-spigot6 months ago 4,561
Compatibility
Minecraft: Java Edition
1.21.x
1.20.x
Platform
Spigot
Changes
Highlights / Notes
A collection of smaller additions, improvements and fixes.
Upgrading from 5.15
- Replace the
bluemap.jar-file with the new one - Delete your
<webroot>/index.htmlto make bluemap update the webapp
Changelog since 5.15
- WebApp: Replaced using number parameter for cache-control with no-cache header (#762, thanks to Macil)
- WebApp: Use unadjustedMovement if supported in free-flight pointer-lock mode (#763, thanks to Macil)
- Added support for "oversized chunks" → large chunks that are stored separately from the region-files (#772)
- Added
render-thread-priorityconfig value for setting the java thread priority for render-threads - Added RenderPasses which allow addons to modify the entire tile-model without being bound to a custom block or entity
- Added logs for more info when watching for map-updates on the CLI
- Added lenient support for non-standard pack.mcmeta format
- Improved exception-handling of API-consumers
- Improved exception-handling when resolving sponge-dimension directories
- Improved troubleshoot command
- Fixed potential deadlock when resolving a configuration-exception
- Fixed world spawn position not correctly read from the level.dat
- Fixed Thread-Names of MapUpdateService-Thread, Webserver and Scheduler
- Fixed player-skin not being removed from the map-storage if the skin-provider returns an empty skin
Full Changelog
https://github.com/BlueMap-Minecraft/BlueMap/releases/tag/v5.16
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:nTnTxZjy"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:swbUV1cr:nTnTxZjy"
}

