Tags
Creators
Details
Licensed Apache-2.0
Published 5 months ago
Updated 3 days ago
All versions
1.3.1+fabric-1.21.1
Release
1.3.1 · fabric · 1.21.12 weeks ago 32
Compatibility
Minecraft: Java Edition
1.21.1
Platform
Fabric
Supported environments
Client-side
Required content
Any compatible version
Changes
Release Date: October 7, 2026 Supported MC Versions: 1.20.1 (Forge/Fabric), 1.21.1 (NeoForge/Fabric), 26.1.2 (NeoForge/Fabric), 26.2 (NeoForge/Fabric)
Fixes
- Explored terrain is now saved and restored across save/quit, client restarts, dimension changes and reconnects.
- Singleplayer saves and multiplayer server addresses have separate terrain archives, with complete dimension identifiers keeping dimension data separate.
- Scanning unloaded chunks no longer erases previously explored terrain.
- Versioned tile files are replaced atomically. Corrupt or newer-format files are preserved; temporary read/write failures retain new exploration for retry.
- Large saved map views load progressively with bounded resident tile memory. Completed texture pixels stay visible after tile eviction, and changed views cancel stale requests.
- New scan results cannot be overwritten by queued older disk reads; recovered writes and edited/evicted tiles refresh the displayed map.
Upgrade Notes
- Back up your world and configuration, replace the matching loader JAR, and restart the client.
- Keep existing configuration and waypoint files. No configuration reset is required.
- Previous versions did not save explored terrain. Areas already discarded by an older session must be revisited once; this update cannot reconstruct them.
- Very large archives fill progressively. If storage is unavailable, unsaved exploration remains in memory until it can be written or the client exits.
- Multiplayer archives are keyed by the configured server address. A server replacing its world at the same address cannot be automatically distinguished by this client-only storage scheme.
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:lLviL6Oq:dXW48SO0"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:lLviL6Oq:dXW48SO0"
}

