Tags
Creators
Details
Licensed ARR
Published 10 months ago
Updated 2 weeks ago
All versions
1.6.1-RELEASE
Release
DeathAnnouncer 1.6.1-RELEASE2 weeks ago 72
Compatibility
Minecraft: Java Edition
26.3
26.2
26.1.x
1.21.x
1.20.x
Platforms
Bukkit
BungeeCord
Folia
Paper
Purpur
Spigot
Velocity
Changes
New Features
- Added an owner identification system for tamed pets (wolves and cats) in kill messages.
- Added Wind Charge knockback tracking for fall and void death messages.
- Added accumulated experience levels and points to DeathLog, including the ability to restore them.
- Added an Experience Bottle icon to the DeathLog GUI to view the total saved EXP.
- Added an administrator warning when restored items do not fit into the player's inventory and drop to the ground.
- Added multi-webhook support to separate public broadcast channels from staff audit logs.
- Added automatic audit logging for item restoration actions performed by staff/moderators.
- Added proxy configuration support (BungeeCord/Velocity).
- Added an ignored servers blacklist to prevent death announcements in lobbies and login servers.
- Added DeathLog translations for PT-BR, PT-PT, ES, and IT (customizable via
messages.yml). - Added WorldGuard support with custom flags to disable death messages per region.
Fixes
- Fixed incoming packet validation to block transmission attempts from unauthorized clients.
- Fixed item and weapon names not parsing color codes properly.
API
- Added an event system to the API powered by EventBus.
- Added
PlayerDeathAnnounceEvent,PlayerKillstreakMilestoneEvent, andPlayerInventoryRestoreEvent. - Integrated the
IUserinterface to access player instances without direct server implementation dependencies.
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:hQxDvmfe"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ut0pSwR9:hQxDvmfe"
}

