0.0.2
Compatibility
Changes
📜 CustomDeathMessages - Changelog v0.0.2
🎉 Minor Update with Major Improvements!
This version refines the foundation of v0.0.1, adding new community-requested features and improving stability and developer experience.
✅ New Features
-
Killer Support in
/cdm test!
The test command now accepts an optional third argument: the killer's name.
Example:/cdm test ENTITY_ATTACK Notch
This allows you to accurately test placeholders like{killer},{killer_displayname}, and{distance}. -
New Placeholder:
{killer_displayname}
Displays the killer’s display name, respecting nicknames, prefixes, and colors set by other plugins (like EssentialsX or LuckPerms). -
New Placeholder:
{distance}
Shows the distance in blocks between the victim and the killer, formatted to one decimal place (e.g., "5.2"). -
Random Message Cooldown System
The plugin now remembers the last random message shown to a player and will avoid showing it again until a different message has been displayed. This prevents annoying repetitions. -
Improved Killer Detection
The plugin can now correctly detect the killer’s name even if it’s an entity (like a Creeper or Zombie) or has a custom name. Entity names are formatted with initial capital letters (e.g., "Zombie Pigman"). -
Centralized System Messages
All console messages, warnings, and command responses are now loaded frommessages.ymlunder thesystem-messagessection. This allows administrators to fully translate the plugin without modifying the code. -
PlaceholderAPI Compatibility in
/cdm test
PlaceholderAPI placeholders are now also expanded when using the test command, providing a more accurate preview. -
Registered TabCompleter
The/cdmcommand now has a functionalTabCompleterthat suggests "test", damage causes, and names of online players, greatly improving usability.
🐛 Bug Fixes
- Fixed an error in
MessagesManager.javawhere the character encoding when loading the default file was not specified, which could cause issues with special characters. It now usesStandardCharsets.UTF_8.
Thank you for using CustomDeathMessages! This update makes the plugin more powerful, flexible, and easier to use than ever before.
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:LrqgmmvZ:MnxR4LY8"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:LrqgmmvZ:MnxR4LY8"
}

