Tags
Creators
Details
Licensed ARR
Published 7 months ago
Updated 3 months ago
All versions
1.5.0-RELEASE
Release
DeathAnnouncer v1.5.0-RELEASE3 months ago 296
Compatibility
Minecraft: Java Edition
26.1.x
1.21.x
1.20.x
Platforms
Bukkit
BungeeCord
Folia
Paper
Purpur
Spigot
Velocity
Changes
New Features
- Multi-Display System: Introduced native support for broadcasting death messages via Action Bar, Title Screen, and BossBar using the Kyori Adventure API.
- Player Preferences: Added the
/dr togglecommand, allowing players to individually hide or show death messages on their screen/chat. - Universal Placeholders: Implemented the new
PlaceholderContextengine to support advanced native variables (like{ping},{biome},{x}) and PlaceholderAPI globally across all text fields, hover events, and Discord webhooks. - Advanced Filters: Implemented Entity and Cause filter systems, giving administrators precise control to restrict death announcements to specific mob types or damage causes.
Updates
- Configuration Revamp (v4): Completely redesigned
config.ymlfor a cleaner, professional layout. Consolidated theforce-broadcastandvanilla-messagessettings into a unifieddisplaysection. - Language Files: Cleaned up localization files by removing ASCII pollution and adding a sleek, translated Placeholder Guide header for all supported languages.
- Command Optimization: Enhanced
Main.javawith a smarter TabCompleter (StringUtil.copyPartialMatches) and centralized player toggle tracking. - Proxy Safeties: Added strict internal checks to automatically disable local screen displays (Title/BossBar/ActionBar) when Proxy Mode is active, preventing sync errors.
- Smart Auto-Migration: Upgraded the
ConfigMigratorto seamlessly transfer user settings (MongoDB URI, Discord URL, etc.) from version 3 to version 4 without data loss.
Fixes
- Discord Webhook Translation: Fixed an issue where the webhook could throw an
ArrayIndexOutOfBoundsExceptionon custom language files and optimized it to parse variables outside the embed.
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:ut0pSwR9:tsvE75sh"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ut0pSwR9:tsvE75sh"
}

