Trimbound
Configuration
lang.yml
Every message the plugin sends, with colour codes, hex colours and MiniMessage support.
What it controls
lang.yml holds every message the plugin sends to a player or to the
console. Nothing is hardcoded, so you can translate the plugin or match it to your
server's tone without touching anything else.
prefix: "&8[&6Trimbound&8] &r"
use-prefix: true
messages:
no-permission: "&cYou do not have permission to do that."
reload-success: "&aTrimbound reloaded."
use-prefix switches the prefix on or off for every message at once. Set
it to false if you would rather the plugin spoke without announcing
itself each time.
Formatting
| Style | Example |
|---|---|
| Colour codes | &c, &6, &7 |
| Hex colours | &#B255D5 |
| MiniMessage | <gradient>, <bold> |
Messages are parsed as MiniMessage, so angle brackets are read as tags. Avoid
< and > in message text unless you mean them that
way, or the message will not render.
Silencing a message
Set any message to an empty string and the plugin sends nothing at all. This is the clean way to remove chatter you do not want, rather than setting it to a space.
emerald-bonus-loot: ""Placeholders
Messages carry placeholders in curly braces, filled in by the plugin. Which ones are available depends on the message; the defaults in the file show what each one accepts.
status-line: "&7 - &f{trim}&7: {pieces}/4 pieces, &f{percent}% &7power"
timings-total: "&6Total: &f{avg}ms &7per tick"A placeholder the plugin does not recognise is left as written, so a typo shows up in chat rather than turning into an empty gap.
Missing keys
If an update adds a message, it appears in your file on the next load and the rest of your edits are left alone. If the file has a syntax error the plugin says so in the console and keeps using the built in defaults for that session, rather than overwriting what you wrote.