/chatcolor
Command to change color
More details about colors

<fcolor:...> is a placeholder that is replaced by values from default_colors or, if the player has their own, by the player's custom colors.
The value of <fcolor:...> can be anything, but the command only allows writing colors of any format and <gradient:...:...>. There can be any number of these values; the maximum count is determined by the highest digit in default_colors.
Each digit represents a specific color. By default: <fcolor:1> is used for the primary color, <fcolor:2> is used for the primary color with emphasis (e.g., a name), <fcolor:3> for local chat messages, and <fcolor:4> for global chat messages.
<fcolor:...> has several states. By default, it is see — colors that the player will see for ALL messages ONLY for themselves, unless replaced by out — colors that ALL players will see for messages from THIS specific player (i.e., that player's personal colors).
Confused? There is an explanation in the image below, or here is an example: A player enters the command /chatcolor see red red red red. This means the player sees all messages as red on their end, but other players see messages according to their own settings. Now, suppose the player enters /chatcolor out green green green green. This means all of this player's messages will appear green to them and to all other players as well. It's important to understand that out overrides colors from see if they exist, meaning the player will also see other messages as green.
In simple terms: see is for personalizing YOUR OWN view, while out is for colors that OTHER players will also see.

You can skip colors using null so they aren't replaced. For example, /chatcolor see null null <red> <red> will only replace <fcolor:3> and <fcolor:4>, leaving the first two unchanged.
If you have the other permission, you can change the colors of other players by adding their nickname at the end of the command, for example /chatcolor see null <red> <red> <blue> TheFaser. You must specify all color slots before the nickname, but you can skip them as described above.
🌍 Localization
Pathlocalizations → language.yml → command.chatcolor
chatcolor:
null_player: "<color:#ff7171><sprite_or:⁉:gui:icon/chat_modified>This player does not exist"
null_type: "<color:#ff7171><sprite_or:⁉:gui:icon/chat_modified>Incorrect type entered"
null_color: "<color:#ff7171><sprite_or:⁉:gui:icon/chat_modified>Incorrect colors entered"
format: "<br><color:#98FB98>│ Your colors: <br><color:#98FB98>│ <fcolor:1>(local) <fcolor:2><player><fcolor:3>: hello world! <br><color:#98FB98>│ <fcolor:1>(global) <fcolor:2><player><fcolor:4>: hello world! <br>"chatcolor:
null_player: "<color:#ff7171><sprite_or:⁉:gui:icon/chat_modified>Игрок не найден"
null_type: "<color:#ff7171><sprite_or:⁉:gui:icon/chat_modified>Тип введён неверно"
null_color: "<color:#ff7171><sprite_or:⁉:gui:icon/chat_modified>Цвета введены неверно"
format: "<br><color:#98FB98>│ Твои цвета выглядят так: <br><color:#98FB98>│ <fcolor:1>(local) <fcolor:2><player><fcolor:3>: привет мир! <br><color:#98FB98>│ <fcolor:1>(global) <fcolor:2><player><fcolor:4>: привет мир! <br>"null_player
Message if the entered player is not found
null_color
Message if the colors are entered incorrectly
null_type
Message if the type is entered incorrectly
format
The format of the message that will be sent
⚙️ Setting
Pathcommand.yml → chatcolor
chatcolor:
enable: true
aliases:
- "chatcolor"
destination:
type: "CHAT"
cooldown:
enable: false
sound:
enable: falseenable
Enables or disables the functionality of the module
aliases
A list of aliases for using the command
For example newcommand, newcommand_ru, ban, me etc.
destination
Where the message will be sent
| Type | Explanation | Requires additional configuration? |
|---|---|---|
ACTION_BAR | Message above the player's inventory | Yes |
BOSS_BAR | Message at the top of the screen | Yes |
BRAND | Message in F3 | No |
CHAT | Message in chat | No |
TEXT_SCREEN | Message anywhere on the screen | Yes |
TITLE | Full-screen message | Yes |
SUBTITLE | Full-screen message (bottom line) | Yes |
TAB_HEADER | Message in TAB (top) | No |
TAB_FOOTER | Message in TAB (bottom) | No |
TOAST | Message in the top right corner (achievement) | Yes |
cooldown
Usage delay
sound
Sound playback
🔐 Permissions
Pathpermission.yml → command.chatcolor
chatcolor:
name: "flectonepulse.module.command.chatcolor"
type: "TRUE"
other:
name: "flectonepulse.module.command.chatcolor.other"
type: "OP"
cooldown_bypass:
name: "flectonepulse.module.command.chatcolor.cooldown.bypass"
type: "OP"
sound:
name: "flectonepulse.module.command.chatcolor.sound"
type: "TRUE"
colors:
SEE:
name: "flectonepulse.module.command.chatcolor.see"
type: "TRUE"
OUT:
name: "flectonepulse.module.command.chatcolor.out"
type: "OP"name
Permission name
type
Permission type
| Type | Explanation |
|---|---|
TRUE | Available to any player |
FALSE | Available to no one, must be granted separately (e.g., using LuckPerms) |
OP | Available to server operators |
NOT_OP | Available to NON-operators of the server |
other
Permission for use on another player
cooldown_bypass
Permission to ignore the cooldown between uses
sound
Permission to use the sound
colors
List of permissions to change specific color types: SEE or OUT
Last updated on
Edit on GitHub
FlectonePulse