AquaTags

Cosmetic prefixes and suffixes players pick themselves, from a GUI you design in YAML. Tags are granted by permission, so any rank plugin already knows how to hand them out. Selection is persisted per player and exposed through PlaceholderAPI so your chat plugin, tab list and scoreboard all show the same thing.


Base command	`/tags`
Aliases	`tag`, `aquatags`
API	Bukkit `1.16+`, Java `17+`
Folia	Supported
Depends	AquaCore `2.0+`
Soft-depend	PlaceholderAPI
Storage	SQLite (default) or MySQL

How it works

Define a tag

Each tag is an entry in tags.yml with a display string, an icon and a permission node.

Grant the permission

aquatags.tag.vip unlocks the vip tag. Any permission plugin works.

/tags shows every tag; the ones they cannot use are rendered greyed out with a configurable “locked” lore.

Selection is stored

The choice survives restarts and server switches when you point every server at the same MySQL database.

Everything else reads the placeholder

%aquatags_prefix% in your chat format, tab list or scoreboard.

Example

tags.yml


tags:
  vip:
    display: "&#38ecff[VIP]"
    permission: aquatags.tag.vip
    icon: DIAMOND
    slot: 10
    lore:
      - "&7A clean blue tag."
      - ""
      - "&#38ecffClick to equip"

chat-plugin-format.yml


format: "%aquatags_prefix% &f{player}&7: &f{message}"

Sections

Commands — Player and admin commands.
Configuration — Tags, GUI layout and storage.