Links
Tags
Creators
Details
Licensed CC-BY-NC-SA-4.0
Published last month
Updated 2 days ago
All versions
1.12.2-r.1+mc26.2
Release
1.12.2 Release 1 for MC 26.22 days ago 225
Uploaded by
Compatibility
Minecraft: Java Edition
26.2
Platform
Fabric
Supported environments
Client and server
Required content
Any compatible version
Changes
KNOWN ISSUE
- When upgrading to this and future versions, the Icarus' Folly (Smith Hepatizon Elytra) advancement may be revoked. Affected players can restore it with
/advancement grant @s only matcha:end/smith_bronze_elytra.
BREAKING CHANGES
- Item and crop migration
- Hepatizon Elytra (
matcha:bronze_elytra→matcha:hepatizon_elytra) - Tomato (
minecraft:beetroot→matcha:tomato), along with tomato seeds and crop blocks (minecraft:beetroots→matcha:tomatoes)
- Hepatizon Elytra (
- Don’t worry — existing mod saves are migrated automatically.
New Feature
- CliffTree compatibility! (Fabric mod only)
Bug Fixes
- Upstream behavior sync
- Drowned can now spawn at Y=43–62.
- The Crystal Heart cooldown is now 20 ticks (1 second).
- In Hard difficulty, deaths and Wither effects now reduce the health limit by 2 hearts (4 HP) per occurrence.
- Health limit reductions are now tracked correctly in Peaceful difficulty.
- Weather is now cleared only after sleep finishes.
- DFU now runs only migrations newer than the save’s recorded data version, instead of rerunning all migrations from v0.
- Asylum Seeker now summons villagers from the culture stated in its item description, instead of always summoning desert villagers.
- Fixed item Lore positioning when advanced tooltips are enabled.
Note
- The internal data migration schema version is now v6.
Optional dependencies
Any compatible version
Any compatible version
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:9LKX5H57:GceVdxLM"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:9LKX5H57:GceVdxLM"
}

