Tags
Creators
Details
Licensed MIT
Published 2 months ago
Updated 2 days ago
All versions
1.1.0+1.21.1
Release
1.1.0 for Fabric 1.21.12 days ago 16
Compatibility
Minecraft: Java Edition
1.21–1.21.1
Platform
Fabric
Supported environments
Client and server
Required content
Changes
- Reworked mod configuration to use Fzzy Config. Client settings can still be configured in Sodium video settings.
- Atlases can now store explorer maps and buried treasure maps, which displays their target destination in the world map and minimap.
- Reworked Nether maps to properly display terrain instead of just the Nether roof.
- Added Globetrotter enchantment, which makes atlases consume paper instead of empty maps for creating new maps. Found only in stronghold library chests.
- Added information display under the minimap (real time, game time, coordinates, biome, weather), and server-side permission settings for displaying it. Disabled by default.
- Added an option to keep atlases on death. Disabled by default.
- Added many configuration options for controlling item requirements and item scan locations.
- Added support for many accessory APIs.
- Added support for Remapped 2.0+.
- Added Fabric 1.21.1 and NeoForge 26.2 versions.
- Filled maps outside atlases are no longer used by the mod (was confusing to players).
- Ejecting maps using Ctrl + Q now works properly. Ctrl + Q also prioritizes ejecting explorer maps and buried treasure maps over filled maps.
- Fixed coordinate display in the world map not respecting reduced debug info.
- ... and maybe some smaller bug fixes I forgot to put here
Supplementary resources
| File | Type | Size | |
|---|---|---|---|
| mapstitch-fabric-1.1.0+1.21.1-sources.jar | Unknown | 768.21 KiB |
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:etdHQJ0B:Qaz4xdVq"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:etdHQJ0B:Qaz4xdVq"
}


