Tags
Creators
Details
v2.2
Compatibility
Required content
Changes
Changelog
v2.2
Features
DEATH Trigger - Expanded Death Causes & Entity Types
The DEATH trigger now supports 15 built-in death causes and custom entity type matching:
- New causes:
DROWNING,VOID,EXPLOSION,STARVATION,POISON,WITHER,LIGHTNING,SUFFOCATION,MAGIC,FIRE EXPLOSIONmatches bothENTITY_EXPLOSION(creeper) andBLOCK_EXPLOSION(TNT)- Set
deathCauseto any entity type (e.g.ZOMBIE,ENDERMAN,CREEPER) for mob-specific deaths - In-game GUI: left-click cycles through all built-in causes, right-click opens chat input for custom entity/DamageCause
- Web editor: "Custom..." option in Death Cause dropdown (v2.2+ only) with text input field
Broadcast Tooltip (Hover)
When a custom broadcast message is configured, %advancement% now automatically shows the advancement description as a
hover tooltip (same as vanilla [Title] behavior). If the template already wraps %advancement% in a <hover:> tag,
the auto-hover is skipped and the user's custom hover is respected.
MiniMessage <hover:show_text:'...'> and <click:open_url/run_command/suggest_command:'...'> tags are now fully parsed
via Adventure's native MiniMessage engine, so hover/click works in custom broadcasts alongside colors, gradients, and
formatting.
Fixes
- RAID_WIN triggered for all players - now only triggers for players in
raid.getHeroes()(actual raid participants) - Duplicate broadcast message - when a custom broadcast is configured, the API's built-in chat announcement is now suppressed (was causing double messages)
&ecolor code leak in broadcast - MiniMessage titles with unclosed<rainbow>tags no longer capture trailing&efrom the broadcast template- Reload crash after duplicate advancement IDs -
unregisterUI()now properly cleans up partially-initialized tabs, preventing permanentAdvancementTab is already initialisedstate - Cross-tab connections - advancements referencing a target in a different tab now fall back to root with a clear
warning, preventing
AdvancementTab is already initialisedcrash on reload - Web editor broadcast preview -
<hover:>and<click:>tags are now stripped from the preview (rendered in-game only), so they don't appear as raw text
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:gkSA2ktn"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:CyWijK8l:gkSA2ktn"
}

