Tags
Creators
Details
Licensed ARR
Published 4 years ago
Updated 2 days ago
All versions
1.21.4-6.0.0-beta.33+fabric
Beta
journeymap-1.21.4-6.0.0-beta.33+fabric2 years ago 2,432
Compatibility
Minecraft: Java Edition
1.21.4
Platforms
Fabric
Quilt
Supported environments
Client-side
Server-side
Client and server
Changes
JourneyMap 1.21.4-6.0.0-beta.33 for Minecraft 1.21.4
Requirements:
- Java 21
- Minecraft 1.21.4
- fabric 0.110.5+1.21.4
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 v2.0.0
CHANGELOG (2025-01-12-15:09:42):
New in 1.21.4-6.0.0-beta.33
- Added: Force purge all images from memory before exiting game.
- Changed: Adjusted how modded flowerblock colors are calculated. Please report any issues.
- Fixed: Enabling rendering of an Overworld waypoint in the nether changes waypoint position.
- Fixed: Issues when using the mousebutton to open/close the fullscreen map.
- Fixed: More fixes in place to prevent CCMs when getting waypoints to render and added better logging.
- Fixed: Forge Optifine crash.
- Fixed: Cobblemon NPC Icons
- Fixed: Region tiles not getting cleaned properly when switching dimensions.
- Fixed: Display Update not getting called when closing the fullscreen map.
- Fixed: Waypoint command crashing servers sometimes.
- Fixed: Regions of the map appear brighter when teleporting.
- Fixed: Errors when resources packs use invalid namespace names.
- Fixed: Weird issues with very old data.
- Fixed: Mod Compat, immersive portals
- Fixed: Modded leaves colors using or not using the biome color incorrectly.
- Fixed: Another Waypoint crash...
- Fixed: Icons and grid vibrate when the player moves.
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:Jw52YTRb"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:lfHFW1mp:Jw52YTRb"
}

