Running it

Troubleshooting

Things that come up, roughly in the order people run into them.

My trim is not doing anything

Run /trimbound status while wearing it. That command exists mostly for this question and it will name the reason: not enough matching pieces, the trim is off in config.yml, it is off in this world, or the player is missing the permission node.

If status does not list the trim at all, the pieces are not matching. All four have to share the same trim material. The pattern can differ; the material cannot.

It worked before the update and now it feels weaker

Partial sets changed how the plugin works. Abilities used to be all or nothing at four pieces. They now scale with the number of pieces, and each trim has one special power that still needs the full set.

If you preferred the old behaviour, set trims.one-piece-percent to 0. Wearing fewer than four pieces then does nothing, which is close to where things were.

The log says a trim feature was disabled

Two features use parts of the server that the normal plugin API does not cover: the Gold trim clearing a piglin's memory, and the Amethyst trim's through-wall glow. If your Paper version renamed something they rely on, the plugin logs one warning, switches off that single feature and carries on.

Everything else keeps working. No config option fixes this. It needs a plugin build that matches your server.

My config was replaced with defaults

It should not have been. A file that does not parse is left untouched, and the plugin runs on defaults for that session while logging what was wrong with it.

If you are on a build older than 0.1.0 then that protection did not exist and a syntax error would overwrite the file. Check for a backup, and check that your editor is not inserting tab characters, which YAML rejects.

Redstone is behaving oddly

Repeaters, comparators, observers, pistons, sculk sensors, daylight detectors and weighted pressure plates are never written to directly by the plugin. They are driven by the powered dust, exactly as they would be by any other source. If one of those is misbehaving, the cause is almost certainly the circuit rather than the trim.

Levers and buttons are deliberately untouched. Walking past will not flip them.

If dust stays lit after a player walks away, that is a bug worth reporting along with the circuit layout. The plugin releases blocks when the player leaves, when the chunk unloads, when the world unloads and when the server shuts down.

Trims fire inside other people's claims

Check that redstone.respects-claims is true. With it on, the plugin asks other plugins before affecting a block, using the same interaction the server fires for a real pressure plate. Any claim plugin that blocks pressure plates will block this too.

If your protection plugin allows pressure plates inside claims by design, it will allow this by exactly the same rule. That is a setting on their side rather than this one.

Can I use this on Spigot

No. The plugin uses Paper APIs for reading trim data, tracking armor changes and several events. Paper 26.1.2 or a compatible build is required.

Does the pattern really matter

By default a pattern moves an ability by up to a quarter, which is noticeable without being decisive. Set trims.pattern-percent to 0 if you would rather players picked patterns purely on looks, or push it to 50 if you want the choice to carry real weight.

Something else

Open an issue with your config.yml, your server version, and what you expected to happen instead. The reload command prints warnings that are usually worth including as well.