Messages & locale

AtlasRealms ships no messages.yml. Every message lives in plugins/AtlasRealms/locales/en_US.yml, written in MiniMessage.

How the locale is chosen

config.yml’s locale key names the file, without the extension:

locale: 'en_US'

Drop your own file in locales/ — say, tr_TR.yml — and set locale: 'tr_TR' to translate the plugin. Your file does not have to be complete: the bundled en_US fills in any key you leave out, and a missing locale file falls back to en_US with a warning.

Note

A missing message key logs Missing message key: <path> and shows the dotted key itself in place of text, so a gap in translation is never silent.

Command names live here too

Every command literal — create, go, admin, and every subcommand under it — is read from command.*.name in this same file, not hardcoded. A literal must match [a-z0-9_-]+; anything else falls back to the built-in name with a warning. Renaming one takes effect after a restart. See Commands.

Message categories

Prefix	Covers
main.	Generic errors: players-only, player not found, a busy or missing realm record, build progress on the action bar.
realm.status.	The three status labels: open, members, closed.
realm.level.	The four access-level labels: owner, trusted member, resident member, visitor.
realm.flag.state.	The two flag-state labels: enabled, disabled.
realm.flag.<key>.name / .lore	One name and one lore line per realm flag, shown in the flags menu.
event.right.	One refusal line per right, shown when a player is refused an action inside a realm.
event.border.outside, event.portal.*	Border and portal notices.
menu.*	Text shown inside menus: entry names and lore, confirmations, “not your realm”.
command.realm.*	Every player command’s name, description and result messages.
command.realm.admin.*	Every admin command’s name, description and result messages.

See Menus for where menu layout lives — menu text is the name/lore keys above, but a menu’s slots and materials are configured separately, per file.