Tags
Creators
Details
Licensed ARR
Published 4 years ago
Updated 2 days ago
All versions
1.20.1-6.0.0-beta.6+fabric
Beta
journeymap-1.20.1-6.0.0-beta.6+fabric2 days ago 1,314
Compatibility
Minecraft: Java Edition
1.20.1
Platforms
Fabric
Quilt
Supported environments
Client-side
Server-side
Client and server
Changes
JourneyMap 1.20.1-6.0.0-beta.6 for Minecraft 1.20.1
Requirements:
- Java 17
- Minecraft 1.20.1
- Fabric 0.92.3+1.20.1
General Information:
- See http://journeymap.info for information about how to install and use this mod, rules about inclusion in modpacks, translation, etc.
- See http://journeymap.info for information on getting technical support.
- Implements JourneyMap API v1.20.1-2.0.0
CHANGELOG (2026-07-27-21:42:18):
New in 1.20.1-6.0.0-beta.6
- Fixed: Auto-Map performance issues.
- Fixed: Addon marker icons are now centred exactly within their block at every minimap zoom level
- Fixed: Addon overlays could appear a moment late on the minimap after switching dimension, map type, or toggling a layer
- Fixed: Individual addon claim polygons could blink out on the minimap while neighbouring ones stayed visible
- Fixed: Addon marker icons and labels were not clipped to the minimap edge and could spill outside it
- Fixed: Addon overlays could be missing from the minimap after closing the fullscreen map while standing still
- Fixed: Addon marker, image, and polygon overlays leaked textures when removed or replaced
- Fixed: A replaced addon overlay could briefly flicker when the minimap and fullscreen map were both active
- Fixed: Theme border issues.
- Fixed: Entity texture used as raw map icon.
IMPORTANT
- Addons built for 5.9 or 5.10 will not load or work with journeymap 6.0.0
- Addon devs will need to update their plugins to support journeymap-api-2.0.0
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:lfHFW1mp:NbYVKakP"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:lfHFW1mp:NbYVKakP"
}

