Prefixes

A different approach from Tags. Instead of writing meta values, this menu manages LuckPerms group membership. Each prefix corresponds to one group; selecting a prefix removes the player from the other prefix groups and adds them to the chosen one. Mutual exclusion built in.

intermediate

Features: addGroupremoveGroupbulk-actionpermission-ruleexclusive-selection

Requires: LuckPerms

Open: /ame_prefixes Copy

menu.conf

# Prefixes - LuckPerms group-based prefix selector
# Docs: https://abstractmenus.github.io/docs/en/examples/cosmetics/prefixes
# Open: /ame_prefixes
# Requires: LuckPerms

include required(file("./plugins/AbstractMenus/menus/example/_shared/templates.conf"))

title: "&6Choose your prefix"
size: 3

activators {
  command: "ame_prefixes"
}

items: [
  ${borderBlack} { slot: "0-8" }
  ${borderBlack} { slot: "18-26" }

  # Each prefix is a LuckPerms group. Clicking adds the player to that group
  # (and removes them from the others, so only one prefix is active at a time).

  {
    slot: 11
    material: GREEN_WOOL
    name: "&a[Member]"
    lore: [
      "&7The default prefix."
      "&7Free for all players."
    ]
    click {
      actions {
        bulk: [
          { removeGroup: "ame_prefix_donor" }
          { removeGroup: "ame_prefix_admin" }
          { addGroup: "ame_prefix_member" }
        ]
        sound: ${successSound}
        message: "&aPrefix set to [Member]."
        closeMenu: true
      }
    }
  }

  {
    slot: 13
    material: GOLD_INGOT
    name: "&6[Donor]"
    lore: [
      "&7Donor prefix."
      "&7Available for supporters."
      "",
      "&8Requires donor permission"
    ]
    rules { permission: "abstractmenus.donator" }
    click {
      actions {
        bulk: [
          { removeGroup: "ame_prefix_member" }
          { removeGroup: "ame_prefix_admin" }
          { addGroup: "ame_prefix_donor" }
        ]
        sound: ${successSound}
        message: "&6Prefix set to [Donor]."
        closeMenu: true
      }
    }
    denyActions: ${denyNoPerm}
  }

  {
    slot: 15
    material: NETHERITE_INGOT
    name: "&c[Admin]"
    lore: [
      "&7Admin prefix."
      "",
      "&8Requires admin permission"
    ]
    rules { permission: "abstractmenus.admin" }
    click {
      actions {
        bulk: [
          { removeGroup: "ame_prefix_member" }
          { removeGroup: "ame_prefix_donor" }
          { addGroup: "ame_prefix_admin" }
        ]
        sound: ${successSound}
        message: "&cPrefix set to [Admin]."
        closeMenu: true
      }
    }
    denyActions: ${denyNoPerm}
  }

  ${buttonClose} { slot: 22 }
]

_shared/templates.conf

# AbstractMenus example pack - shared templates
# Reusable HOCON snippets referenced from menus via ${blockName} substitution.
# Docs: https://abstractmenus.github.io/docs/en/examples

# Sound presets (Paper 1.21+ registry keys)
clickSound:    "ui.button.click"
openSound:     "block.chest.open"
closeSound:    "block.chest.close"
successSound:  "entity.experience_orb.pickup"
failSound:     "block.note_block.bass"
deniedSound:   "block.anvil.land"

# Deny action snippets (use as: denyActions: ${denyNoMoney})
denyNoMoney {
  sound:   ${deniedSound}
  message: "&cYou don't have enough money."
}
denyNoPerm {
  sound:   ${deniedSound}
  message: "&cYou don't have permission."
}
denyCooldown {
  sound:   ${deniedSound}
  message: "&cYou're on cooldown. Try again later."
}

# Border items (use as: ${borderBlack} { slot: "0-8" })
borderBlack {
  material: BLACK_STAINED_GLASS_PANE
  name: " "
}
borderGray {
  material: GRAY_STAINED_GLASS_PANE
  name: " "
}
borderBlue {
  material: BLUE_STAINED_GLASS_PANE
  name: " "
}

# Navigation buttons (use as: ${buttonClose} { slot: 22 })
buttonClose {
  material: BARRIER
  name: "&cClose"
  click {
    closeMenu: true
  }
}
buttonBack {
  material: ARROW
  name: "&eBack"
  lore: ["&7Return to previous menu"]
  click {
    closeMenu: true
  }
}
buttonNext {
  material: ARROW
  name: "&eNext page"
  click {
    pageNext: 1
  }
}
buttonPrev {
  material: ARROW
  name: "&ePrevious page"
  click {
    pagePrev: 1
  }
}

# Rule shortcut snippets (use as: rules: ${rulesAdmin})
rulesAdmin   { permission: "abstractmenus.admin" }
rulesVip     { permission: "abstractmenus.vip" }
rulesDonator { permission: "abstractmenus.donator" }

# Common decorative header (use as: ${commonHeader} { slot: 4 })
commonHeader {
  material: NETHER_STAR
  name: "&6&lExample Menu"
  lore: ["&7Welcome to the AbstractMenus example pack"]
}

↓ menu.conf ↓ Bundle (.zip)

Bundle includes _shared/templates.conf and INSTALL.txt.

What it teaches

• The addGroup / removeGroup actions for LuckPerms group membership
• Using bulk to run multiple removeGroups + addGroup in one click
• Permission-gated upgrades to higher-tier prefixes

Why bulk

Each prefix selection runs three actions in sequence:

bulk: [
  { removeGroup: "ame_prefix_member" }
  { removeGroup: "ame_prefix_donor" }
  { addGroup: "ame_prefix_admin" }
]

We can’t write removeGroup: ... twice at the top level of an actions {} block - HOCON object keys must be unique. bulk wraps the action sequence, letting each entry be its own action group.

This pattern (remove-all-others, add-this-one) ensures the player is in exactly one prefix group at a time. Without the removes, players accumulate group memberships and end up with multiple stacked prefixes.

Tags vs Prefixes pattern

Two ways to manage chat prefix:

• Tags (lpMetaSet) - flexible, fine-grained, no group hierarchy. Best for purely cosmetic symbols.
• Prefixes (addGroup) - integrates with LuckPerms groups, inherits perms from the group, plays nice with chat plugins that read %luckperms_prefix%. Best when the prefix should also imply other permissions.

Most servers want the latter for the actual chat name color, and the former for an additional decorative tag.

Setup

Create the LuckPerms groups before this menu works:

/lp creategroup ame_prefix_member
/lp group ame_prefix_member meta addprefix 50 "&a[Member] "

/lp creategroup ame_prefix_donor
/lp group ame_prefix_donor meta addprefix 100 "&6[Donor] "

/lp creategroup ame_prefix_admin
/lp group ame_prefix_admin meta addprefix 1000 "&c[Admin] "

The numeric weight (50, 100, 1000) controls priority when a player has multiple prefixes - higher wins. Since this menu enforces exactly one prefix per player, weight doesn’t matter much, but it’s good practice to set them.

Try it

1. Drop the bundle into plugins/AbstractMenus/menus/example/.
2. Create the three groups above.
3. /am reload.
4. Type /ame_prefixes in-game.
5. Click any prefix. Verify with /lp user <you> info (you’ll see one of the prefix groups in your group list).