Tags
Creators
Details
Licensed ARR
Published 4 years ago
Updated 2 days ago
All versions
26.2-1.16.9
Release
VoxelMap-Updated 26.2-1.16.96 days ago 1,264
Compatibility
Minecraft: Java Edition
26.2
Platform
Fabric
Supported environments
Client-side
Client and server
Changes
VoxelMap 26.2-1.16.9
✨ New
- Redesigned settings menu — categorized options with tooltips, sliders and toggles, plus a dedicated dialog to show/hide individual radar mobs.
- Mod menu integration — open VoxelMap settings from ModMenu (Fabric) or the config button in the Forge/NeoForge mod list.
- Tutorial toast replaces the old welcome screen on first launch.
- Better waypoint sharing — clearer chat messages with Add and Highlight buttons, Xaero waypoint detection, and fixed private sharing.
- Singleplayer data now lives in the world folder (
saves/<world>/data/voxelmap/), so worlds with the same name no longer overwrite each other. A migration dialog moves existing data. - Server aliases — let several addresses share one set of waypoints and map cache.
- Paste all three coordinates at once when editing a waypoint.
🐛 Fixed
- Map updates live again with Sodium installed — block changes no longer require a relog.
- Waypoints no longer disappear after leaving and rejoining a world.
- Update checker no longer treats
1.16.10as older than1.16.9. - Waypoint labels, icons and highlights render correctly again; icon picker and icon atlas fixed.
- Scoreboard moves below the minimap again; lightmap refreshes on world change.
- World map: fixed world name display and cache folder renaming.
- No more "No value present" errors on join with Connected Textures enabled, plus the follow-up missing/incorrect color errors.
- Several crashes, memory leaks and race conditions fixed for long sessions.
🌍 Other
- Updated and restored translations, removed unused entries, added German for the new menu.
- Removed the deprecated color-code method for map permissions — servers use the settings packet.
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:wkzK5379:8JgngETk"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:wkzK5379:8JgngETk"
}

