Everything else

Colours

Every colour the plugin draws has a name, and the names live in palette.yml.

accent: '<color:#c9a227>'
good: '<color:#3f9e4d>'
bad: '<color:#b03a3a>'

Write the name in any message or on any screen:

lore-action: '<c:good>Click to teleport'

</c> closes it again:

title: '<c:frame>» <c:screen-homes>YOUR HOMES</c> <c:frame>«'

Changing one line in palette.yml recolours every message and every screen that names it, so the whole plugin can be made to match a server without opening the messages folder.

/chorus reload picks up a change.

What a name may hold#

A value is a whole opening tag, not a bare colour, so one name can stand for a gradient, or for a colour and a weight together:

accent: '<color:#c9a227>'
heading: '<gradient:#6b3fb5:#9b6fd4>'
shout: '<c:bad><bold>'

The last one uses another name. Those are worked out when the file is read, so nothing is resolved twice, and a name that stands for itself is reported in the console rather than followed.

</c> closes whatever the name opened, in the right order: a name that opened two tags closes both.

The names that ship#

Name	Where it is used
`frame`	The brackets, arrows and separators that hold a line together
`muted`	The same, one shade lighter
`accent`	Buttons, and the name of a setting
`good`	It worked, and "click to do this"
`bad`	It did not
`brand`	The name of the plugin
`screen-homes` `screen-warps` `screen-kits` `screen-backups` `screen-disposal`	Titles at the top of a screen
`heading-info` `heading-money` `heading-staff` `heading-server` `heading-kits` `heading-warps`	Headings in chat
`sign-owner` `sign-price`	Chest shop signs

Nineteen names in all. Add your own by writing a new line: any name works.

A name that is not there#

It is left exactly as written, so <c:red> still reaches MiniMessage and still means red. That also means a typo shows up on screen as the tag itself rather than as a wrong colour.

Where names work#

Every message, every screen, custom commands, kit claim and fail actions, and motd.txt.

Kit item names and kit lore are the exception. Those still take literal colours — a MiniMessage tag or an &-code — and do not read palette.yml.