Content generated with AI — it may contain mistakes.

ExyliaArmorTrims/GuidesUpdated in v1.5.1

Choose how trims are worn

Where a piece's trim comes from — the item or the player — and what the trim item and remover do.

Page 5 of 214 min read

Decide whether trims belong to the armor (traded, lost on death, sold as items) or to the player (kept through the menu), and learn to hand out trim items and removers.

Before you start#

You only need the plugin installed. The default, both, already works for most servers, so change it only if you want one of the two ways on its own.

Steps#

Pick the mode

Open config.yml and set behaviour.mode:

  • item: trims travel on the armor. Trade them, lose them on death, sell them as items. No menu and no per-player choices table.
  • menu: trims belong to the player and land on whatever they equip. Trim items do nothing.
  • both: the default. An engraved piece is drawn with its own trim, and the player's menu choice fills the pieces that carry none.

Reload

Run /armortrimsadmin reload.

Give a trim item (item and both modes)

Run /armortrimsadmin give <player> sentry/netherite 1.

Apply it

The player picks the item up on the cursor and clicks a piece of armor in their own inventory. The piece keeps everything it had and gains the trim.

Take a trim off

Run /armortrimsadmin remover <player>, and the player drops the remover onto the trimmed piece the same way. The trim comes off and is handed back to them as a trim item.

Check that it works#

After applying, the piece shows the trim to the wearer and to everyone around, and the trim item is used up. After the remover, the piece is bare again and a trim item is in the player's inventory. If nothing happens, check the mode: in menu mode items do nothing, and in item mode /armortrim answers that the menu is off.

Going further#

Keep items or use them up#

config.yml
yaml
behaviour:
  mode: both
  consume-remover: true
  consume-trim-item: true
  hide-without-permission: true

Set consume-trim-item: false and a trim item is reusable. Set consume-remover: false and one remover removes any number of trims.

Expired ranks#

With hide-without-permission on, the default, a player who no longer owns a trim (by node or crate unlock) stops seeing it, but loses nothing: the value is still on the armor and in their row, and the look returns with the node. Trim items never ask for a permission: holding one is the proof of ownership.

The sound when a trim goes on or off#

config.yml
yaml
effects:
  on-apply:
    sound:
      name: BLOCK_SMITHING_TABLE_USE
      pitch: 1.2
  on-remove:
    sound:
      name: BLOCK_GRINDSTONE_USE

They are full ExyliaLib effects: title, action bar, boss bar, sound, particles and fireworks. Both play for the menu and for the items.

Trim items do nothing else

A trim item or remover is inert, whatever it is drawn as: an ender pearl cannot be thrown and food cannot be eaten. It can only be dropped onto armor. Both are recognised by their data, never by name or material, so renaming them breaks nothing.

Technical details

What each mode reads.

ModeWhere the drawn trim comes from
itemOnly what a trim item wrote onto the armor.
menuOnly what the player picked in /armortrim or the 3D wardrobe.
bothThe armor's own trim, and the menu's choice for armor that carries none. The armor wins.

The trim item. It is applied by dropping it onto a piece of armor in the player's own inventory.

RuleDetail
Armor onlyAnything else is ignored, and the click carries on as normal.
One at a timeA piece that already carries a trim is refused: take it off with a remover first.
PermissionNone is asked.
Consumptionconsume-trim-item decides whether it is used up.

What is written onto the armor is one value, exyliaarmortrims:trim, the pattern/material pair. Armor and trim items written before 1.5.0 may carry a preset id instead; it is read as the look that preset stood for. The vanilla trim and everything else on the item are left alone.

The remover.

RuleDetail
A free slotWithout a free inventory slot nothing happens and it says so: the armor is not touched until the item fits.
Consumptionconsume-remover decides whether it is used up.
Unknown trimA trim the registry no longer knows is refused rather than turned into nothing.

Both items are drawn from trim-item and remover-item: material and glow in config.yml, name and lore in messages.yml. Items given by command that do not fit in the inventory wait and are handed over on the player's next join.

The menu always asks. Whether a player owns a trim, by its node or by a crate unlock, is checked by the menu and the wardrobe; a trim item never checks.

Something missing on this page? Tell us on Discord