
ALL Death Messages
Category-based death messages for every entity.
Screenshots





About this Mod
All Death Messages
Overview
Enables death messages for several categories of mobs, and add colours to their names in death messages. Messages use the same texts as vanilla death messages.
For each category, separate kill and death gamerules are generated.
Custom mob categories must be defined in a config file. There is currently no config screen.
Message Triggers
Built-in categories based on mob properties. Custom categories are based on entity types.
A death message will appear if its victim belongs to an enabled death rule, or if any of its recent assailant has an enabled kill rule.
A mob may belong to multiple categories; it will trigger a death message if any of them has its rule enabled.
Built-in categories
all: Applies to everything. When enabled, this overrules all other categories.player: Players are excluded from every other built-in categories below.named: Mobs that have been given a custom name.tamed: Includes both tamed pets and tamed mounts. Messages will still be broadcast to all players regardless of ownership.ephemeral/persistent: Mobs that will/won't naturally despawn.passive/hostile: Mobs that are allowed/disallowed in Peaceful difficulty.
Custom categories
Custom categories are defined in .minecraft/config/alldeath-rules.json.
Each key in the root object is used as a category name. The associated value is an array of strings, representing the entity types that can trigger the gamerule.
This example is provided as the default config file:
{
"utility": [
"minecraft:allay",
"minecraft:iron_golem",
"minecraft:snow_golem",
"minecraft:villager",
"minecraft:wandering_trader"
],
"boss": [
"minecraft:ender_dragon",
"minecraft:elder_guardian",
"minecraft:warden",
"minecraft:wither"
]
}
Name Styling
Mob names in death messages can have different colours and styling applied. Styles can be based on the same categories used in gamerules (both built-in and user-defined), or can be based on anonymous lists of entity types that don't correspond to any gamerule.
The way styles are applied is similar to CSS stylesheets, except in Json and in reverse order.
When multiple styles match a mob, they will all be combined, and the topmost style takes priority in case of conflicts.
Styles are defined in the config file .minecraft/config/alldeath-styles.json, as an array of Json Object.
Each object may contain the following properties:
- (Mandatory)
rule: The mobs that will have the style applied- If it is a string, it will be treated as the name of a mob category. (Either built-in or custom.)
- If it is an array of strings, it will be treated as a list of entity types.
- (Optional)
color: A string. Can be either a hex code formatted as#rrggbb, or a built-in colour name. - (Optional)
bold: A boolean - (Optional)
italic: A boolean - (Optional)
underline: A boolean - (Optional)
strikethrough: A boolean - (Optional)
obfuscated: A boolean


Styling Example
[
{
"rule": [
"minecraft:wolf"
],
"color": "yellow",
"italic": false
},
{
"rule": "named",
"italic": true,
"underline": true
}
]
Walkthrough
The topmost style defines an anonymous category for entities of type "wolf". The bottom one refers to the built-in "named" category.
If a wolf is given a name, both styles will be applied:
The "italic" property is taken from the topmost style; its names will not be italicized.
The topmost style does not define a "underline" property, so the lower property is used, and its name will be underlined.

Commands
/alldeathmsg is the root for all subcommands. It requires a permision level of at least 2.
test <entities>Checks which rules apply to the given entities, and preview their styled names.see-enabledLists all currently enabled rulesdisable-all <confirm>Disables all death message rules.set <rule name> <rule type> <boolean>Equivalent to thegamerulecommand, but with a more convenient auto-complete.reload-stylesReloads styles from the config file.
Related mods
Gamerule Menu
Makes the Gamerule menu accessible from singleplayer worlds
Preferred Gamerules
Lets you choose the default values of gamerules
Available Versions
How to Install ALL Death Messages on Your Server
Order Server
Order a Minecraft Java server with at least 3 GB RAM (4 GB recommended).
Set fabric Loader
In the panel under "Egg", select the fabric loader and matching Minecraft version (26.1.2).
Install Mod
Open the mod browser in the dashboard and search for "ALL Death Messages". Click "Install" – done! Alternatively, upload the .jar via SFTP to the /mods folder.
Compatibility
Mod Loaders
Minecraft Versions
26.1.2, 26.1.1, 26.1 (+20 more)
Server-side
✓ RequiredRecommended RAM
4 GB(min. 3 GB)Frequently Asked Questions
ALL Death Messages server crashes on startup – what to do?
Most common cause: wrong fabric version or insufficient RAM. Check the server log (latest.log) for "OutOfMemoryError" or "Mixin" errors. With Mado Hosting: ensure at least 3 GB RAM is allocated and the loader matches the mod version (26.1.2). You can switch loaders with one click in the panel.
Is ALL Death Messages compatible with fabric?
ALL Death Messages officially supports fabric for Minecraft 26.1.2, 26.1.1, 26.1. The Mado dashboard automatically detects incompatible loader combinations.
Server lagging with ALL Death Messages – how to optimize performance?
Recommended RAM: 4 GB (per 8 players). Use /spark profiler to check if ALL Death Messages consumes the most tick time. Common fixes: reduce server view-distance to 8-10, install "performant" or "starlight" as supplementary mods on Forge. With Mado Hosting, your server runs on NVMe SSDs with dedicated CPU cores for minimal latency.
Similar Mods
Rent Modded Server
Install ALL Death Messages with just one click on your server.