Tags
Creators
Details
All versions
v2.8
Beta
Premium Advancements | Custom Achievements v2.83 months ago 23
Uploaded by
Compatibility
Minecraft: Java Edition
26.2
26.1.x
1.21.x
Platforms
Bukkit
Paper
Purpur
Spigot
Required content
Unavailable version
Changes
WARNING FROM ON NOW YOU NEED v3.0.0-beta-3 MINIMUM of UltimateAdvancementAPI for PremiumAdvancement V2.8+ to work.
Changelog
v2.8
Features
- UltimateAdvancementAPI 3.0.0-beta-3 migration - Full migration from UAA 2.8 to 3.0.0-beta-3.
createAdvancementTab(namespace, background)- background texture now passed directly (removed fromRootAdvancement)AdvancementDisplayBuilder- replaces the deprecated v2.8 constructorBaseAdvancementparameter order changed to(parent, key, maxProgression, display)registerAdvancements(root, Set<BaseAdvancement>)- replaces varargs overload for 6+ advancements- All runtime reflection fallback code removed (no more
NamespacedKeyworkaround)
Fixes
/padv giveerror on UAA 3.0 - Fixedadv.getApiAdvancement() == nullcausing"this advancement is not initialized"message. The root cause was UAA 3.0 changingcreateAdvancementTab(String)tocreateAdvancementTab(NamespacedKey), causing silent tab creation failure.- Empty reward messages - Reward confirmation messages (
money-received,commands-received) no longer send empty lines to chat when left blank in the language file. /padv take <tab:adv>not persisting - Fixed prefix mismatch: when using tab-qualified IDs (e.g.new_tab:new_advancement), the DB revoke was using the raw input"new_tab:new_advancement"instead of the internal ID"new_advancement". Also added a player-load safety check that auto-corrects any stale UAA grants.
Known incompatibilities
Unavailable version
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:CyWijK8l:MalyhNlO"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:CyWijK8l:MalyhNlO"
}

