1.1.7
Compatibility
Changes
A compatibility-only follow-up to 1.1.6: the Fabric and NeoForge 26.1 builds now work on Minecraft 26.1.1 and 26.1.2 as well. No gameplay changes — same code as 1.1.6, same biomes, same seeds. Only the supported-version metadata changed.
Changed
- Fabric 26.1 now loads on Minecraft 26.1.1 and 26.1.2. The 1.1.6 Fabric jar was pinned to exactly Minecraft 26.1, so Fabric loader refused to start the game when running on 26.1.1 or 26.1.2. The 26.1.x patch releases are bug-fix-only versions of 26.1 — the worldgen code the mod hooks into is identical — so the supported-version range now covers all three.
- NeoForge 26.1 is now listed for Minecraft 26.1.1 and 26.1.2 on Modrinth. The 1.1.6 NeoForge jar already loaded on the patch releases, but the Modrinth listing only showed up under 26.1, so users on 26.1.1 or 26.1.2 couldn't find it via the version filter. The listing now appears under all three.
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:mzuh1rlR:8yif3C3j"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:mzuh1rlR:8yif3C3j"
}

