Messages & Sounds

Player-facing language is split across focused files under language/messages/:

File	Content
core.yml	Prefix, action bar, shared errors, progression, and shared visual fragments
commands.yml	Player/admin help and administrative feedback
gameplay.yml	Combat, enchants, swords, armor, crystals, stages, and rebirth
items.yml	Bound item names, lore, and reusable item fragments
menus.yml	Dynamic menu wording and admin setup-menu text
setup.yml	Visual setup prompts and results

Text formatting

MiniMessage and familiar & color codes are supported:

prefix: '<dark_gray>[<gradient:#58e6ff:#a66cff><bold>Dungeons</bold></gradient><dark_gray>] '
no-permission: '<red>You do not have permission to do that.'

Runtime placeholders use angle brackets, for example <player>, <amount>, or <zone>. Do not rename the YAML key or placeholder token. Missing required placeholders can remove useful information from a message even when the file still validates.

The shared prefix is added to normal chat messages. Item, menu, hologram, and reusable fragment entries are generally rendered without it.

Action bar

language/messages/core.yml: actionbar supports configured currency gain and per-minute values:

<money_gain>
<money_minute>
<rebirth_bar>
<rebirth_percent>

Each configured currency also exposes <currencyId>_gain and <currencyId>_minute. Visibility and update interval are controlled in settings/visuals.yml.

Sounds

Event sounds are configured in language/sounds.yml:

sounds:
  attack-critical:
    sound: ENTITY_PLAYER_ATTACK_CRIT
    category: PLAYERS
    volume: 0.55
    pitch: 1.35
    enabled: true

category defaults to PLAYERS, and enabled defaults to true. Volume supports 0 through 4; pitch supports 0.5 through 2.

To silence one event:

sounds:
  ability-no-proc:
    enabled: false

Enchant-specific proc sounds and particles are configured inside each content/enchants/*.yml file rather than the shared sound catalogue.