Configuration

Commands and permissions

Four commands and four permission nodes. The status command is the one players will actually use; the rest are for whoever runs the server.

Commands

Command	Who can use it	What it does
`/trimbound`	Everyone	Shows the usage line.
`/trimbound status`	Everyone	What your own trims are currently doing.
`/trimbound reload`	Operators	Re-reads config.yml, menu.yml and lang.yml.
`/trimbound timings`	Operators	What each trim effect costs per tick on this server.
`/trimbound timings reset`	Operators	Zeroes the timing counters.
`/trimguide`	Everyone	Opens the in-game guide. Also answers to `/armortrims` and `/armortrim`.

Permission nodes

Node	Default	Grants
`trimbound.status`	Everyone	The status command. It only ever reports on the player's own armor.
`trimbound.reload`	Operators	The reload command.
`trimbound.timings`	Operators	The timings command.
`trimbound.trim.<material>`	Everyone	One specific trim, when `permissions.per-trim` is on.
`trimbound.trim.*`	Everyone	Every trim at once. Negate this to make per-trim access fully opt in.

The per-trim nodes are only consulted when permissions.per-trim is set to true in config.yml. While it is off, which is the default, nobody needs them and granting them changes nothing.

trimbound.trim.iron
trimbound.trim.gold
trimbound.trim.diamond
trimbound.trim.netherite
trimbound.trim.redstone
trimbound.trim.emerald
trimbound.trim.lapis
trimbound.trim.quartz
trimbound.trim.amethyst
trimbound.trim.copper
trimbound.trim.resin

Reading the status output

/trimbound status lists every trim material the player is wearing, how many pieces of it, the power that works out to, and whether the special is active. If a pattern is doing something, it says what.

The more useful half is what it prints when a trim is doing nothing. Rather than leaving a gap where an ability should be, it names the reason: not enough pieces, turned off on this server, turned off in this world, or no permission. That covers most of what players end up asking about.

Renaming commands

Command and subcommand names come from config.yml. Each one is a list, so extra entries become aliases.

command:
  - trimbound
  - ft

subcommands:
  status:
    - status
    - mytrims

Renames need a full server restart, or a real Minecraft /reload confirm. The plugin's own reload command cannot rebuild Paper's command tree. If you rename something and then reload, the plugin tells you a restart is still needed instead of letting you think it took effect.

The guide command is separate and lives in menu.yml under commands, with the same restart rule.