1.1.7
Compatibility
Changes
We've optimized the plugin; now the harvest takes longer but it manages to collect the crops (it doesn't put as much strain on the server anymore), and loading from a file has been optimized. If you have the old version of the plugin installed, contact me on Discord and I’ll show you how to upgrade to the new version without errors (you can try replacing the plugin yourself—there might not be any errors, but if any do occur, be sure to reach out)! And for those installing the plugin for the first time, there won’t be any errors!
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:G1H4x02Z:rhce4WaQ"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:G1H4x02Z:rhce4WaQ"
}

