Tags
Creators
Details
Licensed ARR
Published 5 months ago
Updated 6 days ago
All versions
0.10
Release
VoxelMap x SeedMapper 26.2 0.103 months ago 235
Compatibility
Minecraft: Java Edition
26.2
Platform
Fabric
Supported environments
Client-side
Changes
Changelog
Features
- Added a Cubiomes Minecraft-version switcher with automatic client-version selection.
- Added ore identification improvements, ore-target autocomplete, and ESP depth fixes.
- Added customizable world-map transport shortcuts, including command templates, visibility, client-command flags, Y-coordinate exclusion, and main-menu display controls.
- Added Fabric Mod Menu integration so the VoxelMap settings screen can be opened from Mod Menu.
- Improved world-map waypoint and marker behavior, including waypoint layering, label ordering, icon rendering, depth handling, highlighted-waypoint alpha, and waypoint visibility over SeedMapper markers.
- Improved world-map navigation, coordinate editing/recentering, deep zoom behavior, performance mode, and overlay presentation.
- Added improved scoreboard placement and world-map status presentation.
- Added settings-screen scrolling and improved access to options on small windows or high GUI scales.
Reliability and compatibility
- Fixed transport shortcuts not loading when saved records included the client-command field.
- Improved world-map cache location handling across dimensions and subworld changes.
- Hardened persistent-map locking and visibility across worker threads.
- Fixed block-height lookup using the wrong block state.
- Fixed biome repository concurrency issues.
- Closed native compression, ZIP, and save-stream resources correctly.
- Added safer compressed-image handling and atomic world-map image-cache writes.
- Improved world-map refresh and cache behavior during dimension and subworld changes.
Upgrade notes
- Transport shortcuts are stored in
config/voxelmap.propertiesand should now survive restarts. - If world-map artifacts remain after upgrading, remove
voxelmap/cacheonce so regions can be regenerated. - Forge and NeoForge artifacts build successfully, but runtime testing is still recommended.
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:cVrDroCh:OFCffO8m"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:cVrDroCh:OFCffO8m"
}

