Tags
Creators
Details
All versions
v2.5
Release
Premium Advancements | Custom Achievements v2.53 months ago 37
Uploaded by
Compatibility
Minecraft: Java Edition
26.2
26.1.x
1.21.x
Platforms
Bukkit
Paper
Purpur
Spigot
Required content
Any compatible version
Changes
Changelog
v2.5
Features
- LISTEN_MUSIC trigger - Fires when a player inserts a music disc into a jukebox. Supports filtering by specific music disc via the existing item/material system.
- PLAYTIME trigger - Cumulative play time in minutes across all sessions. Checked every 30 seconds. Uses
amount. - LOGIN_STREAK trigger - Consecutive daily logins. Streak resets to 0 if a day is missed. Uses
amount. - BIOME_ENTER trigger - Enter a specific biome (e.g.,
MUSHROOM_FIELDS,BADLANDS). Filter by biome name via entity filter. - VANILLA_ADVANCEMENT trigger - Chain custom advancements on vanilla advancement completion. Filter by exact advancement key (e.g.,
minecraft:story/mine_diamond). - REGION_ENTER trigger - Enter a WorldGuard region (requires WorldGuard on the server). Filter by region name.
- Trigger list condensed - In-game GUI now shows first 17 triggers with "and X more triggers" count; current trigger moved to bottom.
- 53 total triggers - Up from 48, covering the most requested trigger types.
Fixes
- PlaceholderAPI support in webhooks - Custom and vanilla advancement webhooks now resolve PlaceholderAPI placeholders (e.g., nicknames from nick plugins, prefixes from LuckPerms) via
PlaceholderAPI.setPlaceholders() - Vanilla broadcast preview colors - Chat preview after setting a vanilla broadcast message now renders all color formats (
&#RRGGBB,<rainbow>,<gradient>,&codes) instead of showing raw codes - GUI lore colors - "Current broadcast" in the vanilla advancements GUI now displays formatted colors via
AdvancementManager.translateAll() - Vanilla GUI navigation - Added Back button (slot 49) to return to tab selector; empty navigation slots now filled with glass panes
- ConfigUpdater language files - Language files are now always replaced on version bump (with backup) to apply value changes like new triggers in
trigger-types
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:FItqEKZr"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:CyWijK8l:FItqEKZr"
}

