Effects

Every skin may declare an effects block. All of it is optional, and a skin with none simply looks different and does nothing else.

skins:
  inferno:
    effects:
      on-equip:
        sound:
          name: ITEM_ARMOR_EQUIP_NETHERITE
          volume: 0.8
          pitch: 1.2
        title:
          text: '{warning}&lINFERNO'
          subtitle: '{letters}The armour burns'
      on-unequip:
        sound:
          name: BLOCK_FIRE_EXTINGUISH
      ambient:
        particle: 'FLAME|5|0.3|0'
        sound: ''
        interval: 1.0
        radius: 32.0
      set:
        on-complete:
          sound:
            name: ITEM_FIRECHARGE_USE
            volume: 1.0
            pitch: 1.4
        on-break: {}
        ambient:
          particle: 'FLAME|4|0.4|0.01'
          sound: ''
          interval: 0.25
          radius: 32.0

on-equip and on-unequip

Both are standard ExyliaLib effects, so each one may carry any combination of six sections. They are played to the wearer.

A section that says nothing is left out of the file entirely, which is why the default skins.yml shows no sound: block under on-equip. Write the section by hand and it is read from then on. The full reference lives in the ExyliaLib effects module.

ambient

Repeated for as long as the piece is worn.

Both lines are pipe-separated, and a namespaced key survives because the colon is never a separator: minecraft:flame|10|0.4|0.01 is valid. The particle line also accepts the longer NAME|count|dx|dy|dz|speed form when you want the spread to differ per axis.

Where it plays

At the wearer's feet plus the height of the piece the skin is on, so four skinned pieces are four different heights:

What it costs

One repeating task per worn piece that declares an ambient, bound to the player's entity so Folia is happy and so it dies with them. It is cancelled the moment the piece comes off, the skin changes, or the player quits; nothing survives a plugin disable.

Set bonus

effects.set fires when a player wears every piece the skin fits with that same skin. For a skin with an empty pieces list that means all four; for golden_sentry, which fits only the helmet and the chestplate, two pieces complete the set.

The set is judged from the topmost skinned piece downwards: whatever skin sits in the first occupied slot is the only one that can complete. Three inferno pieces and an ocean helmet complete nothing.

What the defaults ship

Every shipped skin now carries the full show: a sound as it goes on, a particle around the body while the set holds, an action bar line — ✦ Full set » <NAME> — when it closes and ✧ Set broken when it ends.

Every one of them uses a radius of 32 blocks, an equip sound at volume 0.8 and a completion sound at volume 1.0, pitch 1.4, category PLAYERS. on-break is the same everywhere: BLOCK_BEACON_DEACTIVATE at volume 0.7 with the broken-set line.

Applying and removing

Putting a skin on and taking it off play their own effect, and those two live in config.yml rather than on the skin, because they belong to the system:

effects:
  on-apply:
    sound:
      name: BLOCK_SMITHING_TABLE_USE
      volume: 1.0
      pitch: 1.2
  on-remove:
    sound:
      name: BLOCK_GRINDSTONE_USE
      volume: 1.0
      pitch: 1.0

Both are full ExyliaLib effects, both are played to the player who did it, and both only fire on a successful drag in the inventory — a refused apply plays nothing, and the API plays nothing either.