Colors & Styles

Every message zResetMap sends is colored the same way: the text runs through Prism, a color engine that understands legacy codes, hex, gradients, rainbows, and a named palette. On top of that, styles.yml lets you define your own tags like <warning> so you are not pasting the same color codes into every message.

This page covers both: the color formats you can type directly, and the style tags you define once and reuse.

The pipeline

When the plugin sends a message, three things happen in order:

  1. Placeholders like {world} are filled in.

  2. Style tags from styles.yml are expanded. <warning> becomes whatever you defined it as.

  3. Prism renders the result: color codes, hex, gradients, and rainbows all turn into on-screen color.

So a style tag is just a shortcut that expands to a Prism template before Prism runs. Nothing you can do with a tag is off-limits in a raw message, tags just save repetition and keep your colors consistent.

styles.yml

The file ships with a handful of tags:

styles-version: 1

styles:
  info: "&b"
  success: "&a"
  warning: "&e"
  error: "&c"
  alert: "&4&l"
  highlight:
    open: "<GRADIENT:FFD700>"
    close: "</GRADIENT:FFA500>"

Drop a tag into any message in a language file and it expands when the message sends:

reset:
  failed: "<error>Reset of {world} failed. Check console.</error>"

Leave styles-version alone. It drives migrations when the plugin updates.

Two ways to define a tag

Shorthand

Give one string. The opening tag becomes that string; the closing tag resets formatting with &r.

warning: "&e"

<warning>watch out</warning> becomes &ewatch out&r.

Long form

Give open and close yourself. Use this when the close needs to be something other than a plain reset, which is exactly the case for gradients.

highlight:
  open: "<GRADIENT:FFD700>"
  close: "</GRADIENT:FFA500>"

<highlight>spawn</highlight> becomes <GRADIENT:FFD700>spawn</GRADIENT:FFA500>, a gold-to-orange fade.

Add your own

Add a key under styles:, then use <yourtag>…​</yourtag> in any message.

styles:
  brand:
    open: "<GRADIENT:00C6FF>"
    close: "</GRADIENT:0072FF>"
  muted: "&8"

Run /zrm reload to apply. Tags are matched by exact name, so <brand> needs a matching </brand> to close.

Color formats

These are the raw formats Prism understands. You can type them straight into a message, or wrap them in a style tag.

Legacy codes

The classic & codes for the 16 colors and formatting.

Colors

&0..&9, &a..&f

Bold

&l

Italic

&o

Underline

&n

Strikethrough

&m

Obfuscated

&k

Reset

&r

Example: &aGreen &land bold.

Hex

Any 6-digit hex color, in whichever form you like:

&#FF8800

ampersand-hash

#{FF8800}

braces

<SOLID:FF8800>

tag form

<#FF8800>

legacy bridge

Example: &#FF8800Sunset text.

Gradient

Fade text from one hex color to another. The text goes between an open and close tag; the close carries the end color.

<GRADIENT:FF0000>this fades red to blue</GRADIENT:0000FF>

Format codes carry through inside a gradient, so &l before it stays bold across the fade. &r ends the run.

Rainbow

Cycle text through the spectrum. The number after RAINBOW is just an id, so you can run more than one independent rainbow on the same line.

<RAINBOW1>rainbow text</RAINBOW>

Named palette

Prism ships 125 named colors, each with a short &-code (&s0 through &q4), for example &t7 for Coral or &q1 for Violet. They expand automatically, so you can use them anywhere a legacy code works.

Quick reference

Format

Example

Legacy

&aGreen &lBold

Hex

&#FF8800, #{FF8800}, <SOLID:FF8800>

Hex bridge

<#FF8800>

Gradient

<GRADIENT:FF0000>fade</GRADIENT:0000FF>

Rainbow

<RAINBOW1>text</RAINBOW>

Named palette

&t7 (Coral), &q1 (Violet)

Style tag

<warning>text</warning> (from styles.yml)

Prefer style tags over raw codes in your messages. If you ever want to recolor everything, you change the tag in one place instead of editing every line.