Tags
Creators
Details
5.21-paper
Compatibility
Changes
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-intervaland theupdate-cooldownsettings from yourplugin.confinto yourcore.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-intervalconfig - Moved
update-cooldownandfull-update-intervalconfigs fromplugin.conftocore.conf - Added
/bluemap tasks cancel allcommand 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
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:eM2WNEZA"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:swbUV1cr:eM2WNEZA"
}

