0.1.10.1+1.20.1-forge
Compatibility
Changes
Sorry for the REPLACE-mode compatibility issue with Immersive Weathering and Moonlight, and thanks for reporting and testing it.
Fixed REPLACE-mode icicle compatibility:
- Resolve the backported icicle from its registered item, never an early block-to-item lookup that can return AIR.
- Preserve foreign icicles while the replacement item is still registering, without poisoning either block's item cache.
- Keep Immersive Weathering/Moonlight creative-tab entries nonempty; replacement still works for placed blocks, recipes and inventories.
- Apply the same readiness checks to saved inventory decoding, modern item components and creative-tab deduplication.
Back up worlds before using REPLACE: saved conversions remain permanent. This fix does not restore items already saved as empty by an older build.
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:8laIEMSc:R7vEoYYG"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:8laIEMSc:R7vEoYYG"
}

