What Is Complete Deaths?
Death in Minecraft is usually a quiet, forgettable moment—a simple line of text that vanishes from chat almost instantly. But what if every demise could be memorable, funny, or tailored exactly to your server’s personality? That’s where Complete Deaths steps in. Originally created as a lightweight Bukkit plugin, Complete Deaths gives server admins total control over every death message that appears in chat. Instead of “Steve was slain by Zombie,” you can have “A Zombie devoured Steve's brains” or “Zombie Arthur stabbed Steve to death.” The plugin replaces vanilla death messages with a customizable system that supports multiple variations per death type, display names, color codes, and even per-world or per-player muting.
Key Features at a Glance
Complete Deaths packs a surprising amount of flexibility into a small footprint. Here’s what you can do right out of the box:
- Multiple messages per death type – No more repetitive announcements. Each death cause can cycle through a list of messages.
- Display name support – If your server uses /nick or display names, the plugin will show those instead of usernames.
- Color-code support – Use the & symbol to add colors, making messages pop.
- Context-aware messages – Create messages specific to a player, killer, mob type, mob name, weapon name, or any combination.
- Radius limiting – Only players within a configurable number of blocks will see the death message.
- Muting and deafening – Mute death messages for specific players or entire worlds, or deafen players so they stop receiving them altogether.
- World-restricted mode – Death messages only appear to players in the same world.
- Missing message collection – The plugin can log any death category you haven’t defined yet, so you can fill in the gaps later.
Installation and Basic Configuration
Getting Complete Deaths running is straightforward. Drop the JAR file into your server’s plugins folder and restart the server. The plugin immediately takes over death messages using a pre-built list filled with dry humor. If you prefer a more streamlined setup, you can manage your entire server’s mods and plugins through the foxygame.net launcher — a modern, flexible Minecraft launcher that lets you download and install plugins like Complete Deaths directly from its menu, without ever touching a file manager.
Once the plugin is active, all customization happens inside the messages.yml file. Open it and you’ll see categories like drowned, gotfinishedoffbyzombie, or wasslainbyplayer. Each category contains a list of messages. For example:
drowned:
Messages:
- "<player> drowned"
gotfinishedoffbyzombie:
Messages:
- "A Zombie devoured <player>'s brains"
wasslainbyplayer:
Messages:
- "<enemy> was destroyed by <player>."
You can add, remove, or rewrite any message. The placeholders <player>, <enemy>, <weapon>, and <health> get replaced automatically when the death occurs. To make a message specific to a certain scenario, append the condition to the category name. For instance, gotfinishedoffbyzombieusingexcalibur would trigger only when a zombie wields a sword named “Excalibur.”
Config Variables Worth Knowing
Inside config.yml, several settings let you fine-tune behavior:
- UseDisplayNames – Replaces usernames with display names.
- UseCaratForColor – If you need an actual ampersand in a message, use
^for color codes instead. - CollectMissingMessages – Logs death types you haven’t defined; view them with
/deaths list. - WhitelistMode – Only show messages that exist in your config; all others are suppressed.
- RadiusValue – Set a block radius (greater than 0) to limit who sees the death.
- WorldRestricted – Keeps death messages within the same world.
Command Reference
Everything is managed through the /deaths command. Typing it alone shows plugin info and available sub-commands. Here are the most useful ones:
/deaths reload– Reloads messages from configuration without a full server restart./deaths enable/disable– Toggle the plugin’s message handling on or off./deaths muteplayer <name>/unmuteplayer– Mute or unmute a specific player’s death announcements./deaths muteworld <world>/unmuteworld– Control death messages per world./deaths hideplayer <name>/unhideplayer– Prevent a player from seeing any death messages./deaths hideworld <world>/unhideworld– Deafens an entire world./deaths list– If CollectMissingMessages is enabled, shows unmatched death categories since the last restart.
Developer API
For server owners who also run custom plugins, Complete Deaths exposes a simple API. You can programmatically check if the plugin is disabled, toggle global muting, mute individual players or worlds, and enable or disable custom messages on the fly. The methods include isDisabled(), setPlayerMute(String player, boolean), setWorldMute(String world, boolean), and toggleCustomMessages(boolean). This makes it easy to integrate death message control into larger server management tools.
Conclusion
Complete Deaths transforms one of Minecraft’s most overlooked features into a canvas for creativity. Whether you run a hardcore survival server, a roleplay community, or a minigame hub, personalized death messages add a layer of polish that players notice and appreciate. The plugin’s lightweight design, combined with its deep customization—from color codes and display names to per-world muting—makes it a must-have for any admin who wants every death to tell a story. Give it a try, tweak the messages to match your server’s vibe, and watch the chat come alive (even when someone doesn’t).