Tags
Creators
Details
4.9.9.3
Compatibility
Changes
Changes and Fixes
- Do not save default configs twice (was accidentally slipped back in when it shouldn't have been on plugin enable)
- Remove leftover debug info (during Folia Testing in 4.9.9.1 that was left over)
- Update dependencies for database types
- Fixed Libby import issues
⚠️ Notes
While 1.21.9 is being worked on, we have noticed bugs that have appeared around FileConfiguration.
We recommend staying up to date on these builds, as they are not the default versions on both providers and bugs may occur.
When using Java, we recommend the Adoptium JDK 17–21 for the best experience with this plugin.
Some users have had success using Java 22–25, but we have not tested on these versions — testing should be done as usual.
If changes need to be made to how configurations are handled, we will update to handle it properly.
Supplementary resources
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:vCFaodCy:N0nYPSV7"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:vCFaodCy:N0nYPSV7"
}

