Chatter Styling
Change how players see each other's messages
Add-on for Chatter to change how players see each other's messages.
We can all agree that the classic Minecraft chat format is quite lacklustre to the point where it becomes hard to read. Chatter allows you to tweak the chat format - go ahead and add colour!
Supports popular permission mods (e.g. LuckPerms) for groups, prefixes and suffixes!
Examples
{
// Chat Styles
"chat": [
{
/**
* Reduces the scope of messages to players belonging to the listed groups
* Use 'player' and 'operator' if you do not have a permissions mod
*/
"groups": ["player"],
// Reduces the scope of messages to players with the listed UUIDs (see https://minecraftuuid.com)
"uuids": [],
/**
* The in-game chat message JSON template (see https://minecraftjson.com)
* Use ${username}, ${player}, ${message}, ${group}, ${team}, ${prefix}, ${suffix}, ${world} and ${datetime[:format]}
*/
"template": "[\"\",{\"text\":\"${player}\",\"color\":\"yellow\",\"clickEvent\":{\"action\":\"suggest_command\",\"value\":\"/tell ${username} \"},\"hoverEvent\":{\"action\":\"show_text\",\"contents\":[\"\",{\"text\":\"Click to direct message\",\"italic\":true}]}},{\"text\":\" > \",\"color\":\"dark_gray\"},{\"text\":\"${message}\"}]",
// True if players can use colour codes in their messages, i.e. &[0-9a-fk-or]
"color": false
},
{
/**
* Reduces the scope of messages to players belonging to the listed groups
* Use 'player' and 'operator' if you do not have a permissions mod
*/
"groups": ["operator"],
// Reduces the scope of messages to players with the listed UUIDs (see https://minecraftuuid.com)
"uuids": [],
/**
* The in-game chat message JSON template (see https://minecraftjson.com)
* Use ${username}, ${player}, ${message}, ${group}, ${team}, ${prefix}, ${suffix}, ${world} and ${datetime[:format]}
*/
"template": "[\"\",{\"text\":\"${player}\",\"color\":\"red\",\"clickEvent\":{\"action\":\"suggest_command\",\"value\":\"/tell ${username} \"},\"hoverEvent\":{\"action\":\"show_text\",\"contents\":[\"\",{\"text\":\"Click to ask for support\",\"italic\":true}]}},{\"text\":\" > \",\"color\":\"dark_gray\"},{\"text\":\"${message}\"}]",
// True if players can use colour codes in their messages, i.e. &[0-9a-fk-or]
"color": true
}
]
}Configuration
The styling add-on config file can be found under: config/chatter/style.json5.
Made changes to the configuration? Type /reload to apply the changes immediately!
Chat Styles
By default, the configuration will look something like this, with a placeholder style entry.
{
// Chat Styles
"chat": [
{
/**
* Reduces the scope of messages to players belonging to the listed groups
* Use 'player' and 'operator' if you do not have a permissions mod
*/
"groups": [],
// Reduces the scope of messages to players with the listed UUIDs (see https://minecraftuuid.com)
"uuids": [],
/**
* The in-game chat message JSON template (see https://minecraftjson.com)
* Use ${username}, ${player}, ${message}, ${group}, ${team}, ${prefix}, ${suffix}, ${world} and ${datetime[:format]}
*/
"template": "[\"\",{\"text\":\"${player}\",\"color\":\"yellow\",\"clickEvent\":{\"action\":\"suggest_command\",\"value\":\"/tell ${username} \"},\"hoverEvent\":{\"action\":\"show_text\",\"contents\":[\"\",{\"text\":\"Click to direct message\",\"italic\":true}]}},{\"text\":\" > \",\"color\":\"dark_gray\"},{\"text\":\"${message}\"}]",
// True if players can use colour codes in their messages, i.e. &[0-9a-fk-or]
"color": false
},
// You can add more chat style entries here, just copy the content between {}
]
}Groups
A list of permission groups, where a player must belong to at least one when deciding to style their chat.
Currently, the following permissions mods will be automatically detected:
Full support for permission groups, prefixes and suffixes
Don't have a permissions mod? Rather, use player and operator as group names!
"groups": ["player"],UUIDs
A list of player UUIDs, where a player's UUID must be contained in the given list.
"uuids": ["6694a0c3-b928-429a-bb6d-ed37e3a570a1"],Template
The in-game chat message template will replace the original message, making any substitutions. This field is expected to be valid JSON, just like how the /tellraw command works.
Refer to the templating guide for instructions on substituting player names, etc.
Token
Type
Meaning
Example
${username}
String
The player's username
Axieum
${player}
String
The player's display name
Axieum
${message}
String
The raw message contents
Hello world!
${group}
String
The player's group name
Moderator
${prefix}
String
A group or team prefix, possibly empty
&3[Moderator]
${suffix}
String
A group or team suffix, possibly empty
${team}
String
The player's team display name, if set
Yellow
${team_color}
String
The player's team colour name, if set
yellow
${world}
String
The player's current world name
Overworld
${datetime[:format]}
DateTime
The current date & time
01/01/2004
"template": "[\"\",{\"text\":\"${player}\",\"color\":\"yellow\",\"clickEvent\":{\"action\":\"suggest_command\",\"value\":\"/tell ${username} \"},\"hoverEvent\":{\"action\":\"show_text\",\"contents\":[\"\",{\"text\":\"Click to direct message\",\"italic\":true}]}},{\"text\":\" > \",\"color\":\"dark_gray\"},{\"text\":\"${message}\"}]",
Colour
This flag allows matched players to use colour and formatting codes in their messages.
"color": true
Last updated
Was this helpful?