styles.yml

Recolor and rebrand every menu, lore line, and message from one file using named tokens, hex, gradients, and rainbows.

styles.yml defines the colors of the plugin. You set up named color tokens once, then reference them everywhere: menus, item lore, chat messages, and the other config files. Change a token here and it updates everywhere that token is used, so you can rebrand the whole plugin in seconds.

The file lives at plugins/zEvolutiveTools/styles.yml. After editing it, apply your changes with:

/et reload

Why use tokens

A token is a name for a color, like primary or currency. Instead of writing the same hex code in fifty places, you write <primary> and define what primary looks like once. Later, switching your whole theme is a single edit.

# define it once
styles:
  primary:
    type: gradient
    from: "#a855f7"
    to: "#06b6d4"

# use it anywhere, in any config or message
title: "<primary>Evolving Pickaxe</primary>"

Color formats

You can mix any of the formats below in the same string, anywhere in the plugin. They are processed in this order:

Named style tokens (defined in this file)
Extended palette codes (&s0 to &q4)
Hex (&#RRGGBB, #{RRGGBB}, <#RRGGBB>)
Gradient, rainbow, and solid tags
Legacy & codes

Tokens defined in the styles: section, used with opening and closing tags like XML:

<primary>Hello</primary>
<currency>1,234</currency> <muted>Crystals</muted>

For solid-color tokens the closing tag is optional. The color sticks until the next color tag, just like a legacy & code.

A six-character hex code. Sets a solid color until the next color tag. Three spellings, all identical, so paste whichever one you already use:

&#a855f7Purple text
#{a855f7}Purple text
<#a855f7>Purple text

&#fcd34dGold then &#ef4444Red
&#a855f7&lBold purple

Most useful for gradients and rainbows that the hex forms do not cover.

<SOLID:RRGGBB>text

Solid color. Sticks until the next color tag.

<GRADIENT:a855f7>Evolving Pickaxe</GRADIENT:06b6d4>

A two-color gradient across the wrapped text.

<GRADIENT:#a855f7:#06b6d4>Evolving Pickaxe</GRADIENT>

The same gradient in MiniMessage spelling, if that is what you are used to.

<RAINBOW1>Quest Complete</RAINBOW>

A rainbow effect. The number is just an id, so you can run several independent rainbows on one line.

On top of the 16 legacy colors there are 125 named colors, each with a short code from &s0 to &q4.

&t7Coral text
&u1Cyan text
&v8Dodger Blue text

They work anywhere a legacy code works, including inside gradients and menu titles.

Standard Minecraft formatting codes. They work everywhere, including inside the formats above.

Formatting

Code	Effect
`&l`	Bold
`&o`	Italic
`&n`	Underline
`&m`	Strikethrough
`&k`	Obfuscated (scrambled text)
`&r`	Reset (only valid in Minecraft chat)

Colors

Code	Color	Code	Color
`&0`	Black	`&8`	Dark Grey
`&1`	Dark Blue	`&9`	Blue
`&2`	Dark Green	`&a`	Green
`&3`	Dark Aqua	`&b`	Aqua
`&4`	Dark Red	`&c`	Red
`&5`	Dark Purple	`&d`	Light Purple
`&6`	Gold	`&e`	Yellow
`&7`	Grey	`&f`	White

The whole styles: list belongs to you. Styles you add, change, or remove are kept exactly as written across reloads and plugin updates. The trade-off is that styles shipped with a later version only appear in a fresh file, so delete the list if you ever want the defaults back.

Defining a style

Each entry under styles: has a unique name and a type. Three types are supported.

styles:
  success:
    type: solid
    color: "#22c55e"
    bold: false        # optional, default false
    italic: false      # optional, default false
    underline: false   # optional, default false

styles:
  primary:
    type: gradient
    from: "#a855f7"
    to: "#06b6d4"
    bold: false        # optional
    italic: false      # optional
    underline: false   # optional

styles:
  party:
    type: rainbow
    saturation: 100    # optional, used as the rainbow's id
    bold: false        # optional
    italic: false      # optional

Style names must be lowercase with no spaces. Hyphens are allowed. Add as many as you like, then run /et reload to apply.

The default theme

The plugin ships with a purple-to-cyan gradient as primary and warm gold as currency, built around the "evolution" idea. These are the tokens you will see referenced across the configs:

Token	Type	Color	Used for
`primary`	gradient	`#a855f7` to `#06b6d4`	Tool names, section headers
`header`	gradient (bold)	`#a855f7` to `#06b6d4`	Menu headers
`currency`	solid (bold)	`#fcd34d`	Currency amounts, costs, levels
`accent`	solid	`#fcd34d`	Inline accents, tier indicators
`success`	solid	`#22c55e`	Confirmations, positive feedback
`warning`	solid	`#facc15`	Soft warnings
`error`	solid	`#ef4444`	Errors and refusals
`muted`	solid	`#6b7280`	Labels, descriptions
`highlight`	solid	`#e5e7eb`	Lore body text on dark backgrounds

Rebranding in three steps

Edit the tokens

Open styles.yml and change the colors of primary, currency, and any others to your server's palette. You can change a token's type too, for example turning primary from a gradient into a solid color.

Reload

Run /et reload. Every menu, lore line, and message that uses those tokens updates at once.

Check in game

Open a tool menu and look at an item's lore to confirm the new colors. Tokens flow through to chat messages as well.

For example, to switch to a warm orange brand, point primary at a solid orange:

styles:
  primary:
    type: solid
    color: "#f97316"
    bold: true

When you switch a token from one type to another, swap the color keys too: a solid style uses color, a gradient uses from and to. If you forget, the style still shows (a solid with only from/to borrows from, a gradient with only color uses that color at both ends) and the console tells you which key to rename. A style with no color value at all falls back to plain white until you fix it.

The config-version key at the top of the file is managed by the plugin and used to migrate settings if a key is renamed in a future update. Do not edit it.

Troubleshooting

Seeing raw tags like <GRADIENT:...> in chat means the string was written outside the supported syntax. Re-check it against the formats above.

A tag with an empty color, like <SOLID:>, means a style is missing its color value. Open styles.yml, find the token, and give it a full six-digit hex code.

A console line saying a style "is type 'solid' but still carries the color keys of another type" means the token was switched between types and kept the old keys. The plugin displays it anyway using the key it found, and names the key to rename. See Troubleshooting for more.

styles.yml

On this page