1.0.5
Compatibility
Changes
✅ Added full version compatibility support from Minecraft 1.17 up to the latest release, ensuring seamless operation across all modern server versions.
✅ Implemented cross-version handling for internal API changes to maintain consistent behavior and stability.
✅ Ensured all existing features, commands, and placeholders work identically on every supported version without limitations.
✅ Improved long-term maintainability by future-proofing the plugin against upcoming Minecraft updates.
✅ Verified performance and reliability across the entire supported version range for production environments.
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:qFZbTPYs:sMaKeWK8"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:qFZbTPYs:sMaKeWK8"
}

