0.2.3-1.20.1
Compatibility
Changes
Someone was complaining on Github, so I have removed an error logger that I thought I had removed. Almost certainly this won't actually fix the issues with concrete curing lag people have had, but it will fix the log spam.
I have an idea for a way to fix curing lag, but I'm going to try implementing that in 1.21 and then backporting
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:ca9X1Phr:aeht9lRu"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ca9X1Phr:aeht9lRu"
}

