Tags
Creators
Details
Licensed ARR
Published 4 years ago
All versions
26.1-6.0.0-beta.65+neoforge
Beta
journeymap-26.1-6.0.0-beta.65+neoforge3 months ago 1,945
Compatibility
Minecraft: Java Edition
26.1.x
Platform
NeoForge
Supported environments
Client-side
Server-side
Client and server
Changes
JourneyMap 26.1-6.0.0-beta.65 for Minecraft 26.1
Requirements:
- Java 25
- Minecraft 26.1
- NeoForge 26.1.0.1-beta
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 (2026-04-09-22:56:34):
New in 26.1-6.0.0-beta.65
- Added: Cartography option "Use Nether Surface Lighting" - when disabled, Nether surface map uses maximum brightness; when enabled, uses actual world light levels
- Added: Brightness map filter option
- Added: Minimap Option for which layer to render on, default: Last
- Fixed: Base Map shader not always working.
- Fixed: Baby mobs causing issues.
- Fixed: Forge log spam
- Fixed: GameTime InfoSlot skipping minutes
- Fixed: Zombie Villagers not respecting Show Villagers toggle and ignoring Show Villager Names setting
- Fixed: Native out of memory crash when saving map
- Fixed: JVM crash when writing region map images to disk
- Fixed: Compatibility crash with Tectonic when automapping chunks
- Fixed: Chunk cache not persisting data; block data only available in render range
- Fixed: Map colors in custom dimensions (e.g. Pixelmon Ultra Space) changing with day/night cycle
- Fixed: The End night map button no longer shown; The End uses day map only
- Fixed: Team prefix rendered twice when Show Team Names is enabled
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:TheYMGh0"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:lfHFW1mp:TheYMGh0"
}

