Tags
Creators
Details
v3.2
Compatibility
Required content
Changes
Changelog
v3.2
Features
!!! Updated Support to 26.3! From on now please use MINIMUM UltimateAdvancementAPI 3.0.0-beta-4 !!!
-
MythicMobs filter for the KILL trigger - Restrict a
KILLadvancement to a specific MythicMobs mob, faction, and/or level range. MythicMobs is a soft dependency (optional).- Set the mob's internal name via the in-game GUI (slot 20 of the KILL editor) or the web
editor (v3.2+ gated), or directly in YAML (
mythicMob,mythicFaction,mythicMinLevel,mythicMaxLevel). - Mob names and factions are matched case-insensitively; the GUI validates the mob ID against the installed MythicMobs before saving.
- Kill detection uses
MythicMobDeathEventcombined with the standard BukkitLivingEntity#getKiller()tracking, so the killer is resolved reliably even though MythicMobs' owngetKiller()is not populated at death time. - If MythicMobs is missing, filtered advancements are disabled with a console warning and an
in-game admin notification , mirroring the existing WorldGuard
REGION_ENTERbehaviour.
- Set the mob's internal name via the in-game GUI (slot 20 of the KILL editor) or the web
editor (v3.2+ gated), or directly in YAML (
-
UltimateAdvancementAPI 3.0.0-beta-4 - Upgraded the hard dependency from
3.0.0-beta-3to3.0.0-beta-4(API-compatible and backward-compatible with beta-3). -
Hide custom tabs from the vanilla advancements GUI - New
hide-tabs-from-vanilla-guiconfig option. When enabled, PremiumAdvancements custom tabs are not shown in the vanilla advancements screen (the L key), while all advancement functionality (progression, rewards, placeholders, webhooks,/padvcommands) keeps working. Useful for using the plugin purely as an advancement backend and building a custom GUI with plugins like CommandPanels. -
Silent advancement grant -
/padv give <player> <advancement> --silent(also-s,--NoMessages,--NoFeedback) now grants without sending the "You have been granted..." notification or the admin success message. -
Minecraft 26.3 support - Added Paper/Spigot/Purpur 26.3 to the CI compatibility matrix.
-
Web editor icon library expansion - Added ~150 new icons to the icon picker: all wood types (and their stripped variants), copper doors/bars/chains/lanterns/golem-statue with their oxidation and waxed variants, cut copper stairs & slabs, all 23 pottery sherds, leather/iron/golden/diamond horse armor, 10 banner patterns, 19 smithing templates (armor trims + upgrade), 16 colored bundles, 16 colored ghast harnesses, and misc items (spawner, breeze rod, stick). The icon downloader (
scripts/download_icons.py) now resolves the correct inventory item textures. -
Searchable connection target dropdown - The "Connection Target" field in the web editor is now a single searchable combobox: type directly in the field to filter the advancement list inline, with the first match auto-highlighted , no more scrolling through a long list.
-
Enchanted icon glint - New "Enchanted Glint" toggle (web editor, and
iconEnchanted: truein YAML) that renders the advancement icon with an enchantment glint in the vanilla advancements GUI.
Fixes
-
Placeholder condition missing from the create GUI - The placeholder condition slot (slot 35, the "redstone powder") now appears in the create GUI, not just in the edit GUI of existing advancements.
-
REGION_ENTERtrigger not firing - The region check now uses the player's destination block (PlayerMoveEvent#getTo()) instead of a possibly-staleplayer.getLocation(), and the region handler no longer silently swallows WorldGuard errors (it logs them). Added diagnostic logging. -
DisposedExceptionspam / memory pressure on reload - Replaced per-unitincrementProgression()loops with a single batchedincrementProgression(player, N)call when restoring progression. ArequiredAmount: 350000advancement previously queued 350,000 async UAA progression updates per player on load/complete - if a/padv reloadhappened during the flush, that burst into thousands ofAdvancementTab is disposedwarnings and allocated large amounts of memory. Each path now sends one update instead of N:PlayerDataListener.onPlayerLoadCompleted- completed/in-progress restoration uses a single call.TriggerService.completeAdvancement/completeAdvancementForced- "catch-up to max" uses a single call.TriggerService.recheckDependents- dependent progression sync uses a single call.
Known incompatibilities
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:uqEMUnrd"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:CyWijK8l:uqEMUnrd"
}

