messages.yml & menus

messages.yml

messages.yml is everything the plugin says to a player or an operator — every chat line. It carries a config-version: '1' and is brought forward automatically on update, the same as config.yml.

Menu words are not here. A menu’s title, item names and lore live beside its layout, in its own menus/*.yml file, because a lore line belongs to the icon it describes.

MiniMessage, and five colours

Every line is a MiniMessage string: <red>, <green>text</green>, <#5ee6a8> for any hex colour, <gradient:#a:#b>text</gradient> for a gradient. Legacy &c-style codes are not translated — a &c in a line shows as the two literal characters, and the plugin warns once if it finds one in config.yml.

Message bodies keep to five colours, deliberately, so a hundred lines still read as one plugin:

Colour	Meaning
<red>	it did not happen, and why
<green>	it happened
<yellow>	it happened, with something worth knowing
<gray>	the rest of the sentence
<white>	the one thing in the line worth reading — a name, a number

Placeholders are written <like-this>; each message’s comment in the file lists the ones it takes. Setting a line to '' (empty) turns that one line off — nothing is sent for it.

Message categories

Lines are grouped by feature, in this order: prefix; whitelist, sell, item, my-spawners, returns, log, integrations, stacking, ownership, upgrades, migrate, give, set, types, top, summary, eggs, mining, placing, boosters, tickets, wands; main (the help menu and general lines); anvil; hologram; display.

menus/*.yml

Each menu file is layout and words together — rows, filler, and every square’s item, name and lore in one place. Unlike config.yml, messages.yml and database.yml, the menus/ files carry no config-version and are never merged on update: they are curated content, the same as spawners.yml. A square you emptied to remove a button stays removed.

File	Rows	Opens with	What it is
boosters.yml	6	/atlasspawner trust boosters	The booster, ticket and wand shop.
log.yml	6	/atlasspawner log [player]	Action history for a spawner or a player.
my-spawners.yml	6	/atlasspawner list, /myspawners	Everything you own or may use.
returns.yml	6	/atlasspawner returns	Spawners waiting to be claimed back.
spawner.yml	5, title <type>	right-click a spawner	The single-spawner menu: store, upgrades, collect/sell, whitelist.
ticket-axis.yml	3	using an ANY ticket	Pick which upgrade axis the ticket applies to.
whitelist-add.yml	6	adding a name from a menu	Search and choose a player to whitelist.
whitelist-player.yml	3, title <player>	clicking a name in whitelist.yml	One player’s allowed actions on this spawner.
whitelist.yml	6	/atlasspawner whitelist	Who may use the spawner you are looking at.