Content generated with AI — it may contain mistakes.

ExyliaChatCosmetics/The catalogueUpdated in v1.3.0

Tags

Add, edit and show the small mark in front of a player's name: from the shipped 180 tags to your own sprites and heads.

Page 5 of 305 min read

A tag is one small mark in front of a name, picked by the player from a menu. You get 180 of them already, in seven tabs, and a few lines of YAML add your own.

A tag is not a rank: a rank says what somebody is, a tag is one thing they liked. Keep each one to a single glyph, sprite or head, with no brackets and no words.

Before you start#

  • Tags appear in chat only when your chat format has a {tag} piece. The shipped default.yml has none, so see Formats first.
  • Sprites and <head:> need a Minecraft 1.21.9 client. Plain symbols work everywhere.

Show tags in chat#

Add the piece

Open your format file in lang/<language>/chat/formats/ and add {tag} before the name, as described in Formats.

Reload

Run /cca reload.

Equip one

Run /cc tags, click a tag, then write in chat. The tag now sits in front of your name.

Add your own tag#

Open the file

Edit lang/<language>/cosmetics/tags.yml (in your language folder).

Write the entry

Copy the example below, change the id (mvp) to a new one, and set what it draws in display.

Reload and test

Run /cca reload, then /cca give <player> tag:mvp and open /cc tags.

yaml
tags:
  mvp:
    category: premium
    name: '{primary}&lMVP'
    display: '{highlight}✦'
    icon: GOLD_INGOT
    description: 'Reserved for the {highlight}top players.'
    priority: 1

An entry needs display or head. With neither, it is reported in the console and skipped. By default a player needs the permission exyliachatcosmetics.tag.item.<id> (or exyliachatcosmetics.tag.category.<category>) to own it, or you hand it out with /cca give. Set permission: false and only grants own it.

Check that it works#

  • /cc tags lists your tag under its category.
  • After you equip it, a chat line shows the mark before your name.
  • No entry in the console report, which names the file and the key that is wrong.

The seven tabs#

TabCountWhat it holds
SYMBOLS24plain characters: hearts, stars, arrows
ANIMATED31sprites the client animates by itself
PARTICLES24particle textures, drawn still
ICONS24item and block textures
INTERFACE20HUD sprites: hearts, hunger, effect icons
FLAGS43country flags, each one a head skin
PREMIUM14the ones worth keeping behind a permission

Delete the tabs you do not want and the menu redraws around what is left.

Draw sprites and heads#

Plain characters are the safe choice. Everything below needs a 1.21.9 client; an older one shows the text it is written in instead of failing.

WrittenDraws
<sprite:'minecraft:block/sea_lantern'>a block texture
<sprite:'minecraft:items':'minecraft:item/diamond'>an item texture
<sprite:'minecraft:particles':'minecraft:heart'>a particle
<sprite:'minecraft:gui':'minecraft:hud/heart/full'>a HUD sprite
<head:'Notch'>a real account, by name
<head:'entity/player/wide/steve'>a skin the game ships with

Put <white> in front of every sprite, as the shipped file does. Without it the sprite takes the colour around it and comes out tinted. A colour there instead of <white> tints it on purpose.

A wrong atlas is the usual reason a sprite draws nothing. Particles and GUI ids drop their folder ('minecraft:heart', not 'minecraft:particle/heart'); blocks keep block/ and items keep item/.

Tags that move#

The client animates some textures by itself (fire, lava, portals), and the ANIMATED tab is exactly those. Nothing to configure.

animation: is the other kind. It repaints letters frame by frame, so it moves symbols and not sprites. Use ids from Animations, for example animation: shine.

Make a flag or head tag#

A skin nobody wears, like a flag, goes in the entry's own head: key. It takes the base64 value, the texture hash, or the full texture URL from a head site. The head is drawn before the display. The menu icon takes the same value as basehead-<value>.

yaml
  flag_argentina:
    category: flags
    name: '{primary}&lARGENTINA'
    head: 'eyJ0ZXh0dXJlcyI6eyJTS0lOIjp7InVybCI6…In19fQ=='
    icon: basehead-eyJ0ZXh0dXJlcyI6eyJTS0lOIjp7InVybCI6…In19fQ==
    description: "Argentina, drawn as a head."
    priority: 1

Spacing around the tag#

tags.format in config.yml decides how every tag sits around the name. It is %tag% by default: the tag, then a space. An entry can set its own format: for a tag that needs no space or a bracket. Put the spacing there, not in display.

Entry keys
KeyMeans
displaywhat is drawn; palette tokens, & codes and MiniMessage work
heada skin drawn as a head just before the display
formathow the tag sits around the name, overriding tags.format
animationan id from animations.yml
category, name, icon, description, priority, permission, requirement, hidden, metadatathe shared fields, see the catalogue
Why heads need ecc_head

Menu lore and placeholders are plain strings, and no standard MiniMessage tag can write down a skin. So the plugin adds ecc_head, which carries the skin through a string and rebuilds the head on the other side. A head given as an account or a game skin needs none of this.

If a head still arrives as a bare <head>, with its skin lost, it is removed. A placeholder then returns the rest of the line without the head, never a stranger's face.

Something missing on this page? Tell us on Discord