Tags
Creators
Details
Licensed ARR
Published 2 months ago
Updated 6 days ago
All versions
0.12
Release
VoxelMap x SeedMapper 26.26 days ago 226
Compatibility
Minecraft: Java Edition
26.2
Platform
Fabric
Supported environments
Client-side
Changes
Added
- Merged PR #16 with major upstream VoxelMap updates.
- Added the new sidebar-based settings screen with categorized options, tooltips, and dependency-aware controls.
- Added improved SeedMapper settings, structure detection, loot controls, ESP options, and marker configuration.
- Added ChunkSync sharing categories, player-layer management, and improved sharing controls.
- Added server aliases and improved per-server data handling.
- Added world-relative singleplayer storage and migration support.
- Added data migration screens and waypoint/config migration helpers.
- Added improved packet handling and multiloader support.
- Added updated Fabric, Forge, and NeoForge entrypoints and compatibility changes.
- Added improved color picker and settings UI controls.
- Added autocomplete support for SeedMapper text fields.
- Added improved world map rendering, waypoint handling, translation updates, and resource loading.
Fixed
- Fixed a world-map crash caused by a race condition in shared region data.
- Fixed world-map dimension previews showing entities and portal markers from the wrong dimension.
- Fixed End previews displaying Overworld containers, chests, and Nether portal markers.
- Removed the unused End portal-frame and End beacon icons from the SeedMapper feature strip.
- Fixed world-map text, atlas, waypoint-loading, and rendering issues from the upstream updates.
- Fixed settings input focus and autocomplete dropdown placement.
- Fixed various packet, waypoint, portal, and resource-reloading issues.
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:EjGbZGNb"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:cVrDroCh:EjGbZGNb"
}

