Tags
Creators
Details
11.3
Compatibility
Changes
Fixed
-
Fixed the plugin not loading when multiple achievements use duplicate
DisplayNamevalues.- Unique internal
Namevalues are still enforced. - Blank display names remain invalid.
- Unique internal
Improved Achievement Loading
The plugin now continues loading when individual achievements contain invalid configuration instead of failing the entire plugin.
It now:
- Skips malformed achievements while continuing to load valid ones.
- Skips invalid or non-positive threshold entries.
- Isolates malformed categories and subcategories.
- Logs the exact configuration path for every skipped entry.
- Prints a final count of skipped entries after loading.
- Prevents failed entries from reserving advancement keys.
Global failures that make safe operation impossible, such as unreadable YAML files or invalid database settings, remain fatal.
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:KADKsqnh:RdX411Fh"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:KADKsqnh:RdX411Fh"
}

