Fix a LuckPerms prefix priority without changing chat formatting
Two ranks can provide competing prefixes even when permissions work. Inspect the metadata priorities first so you can fix the selected prefix without rewriting your chat plugin.
Follow the procedure
- Confirm that the affected chat or TAB integration already displays some LuckPerms metadata. A raw placeholder points to a separate integration problem.
- Run
/lp user PLAYER meta infoand inspect inherited group prefixes. Record the text, numeric priority, source group and applicable contexts. - Decide which existing prefix should win for the player. Do not delete a donor or staff group merely to change its displayed label.
- Use a scoped editor session for the relevant group to adjust that prefix’s priority. Save the session and apply the generated command to the correct server instance.
- Test the same ordinary player with their real combination of ranks. Compare chat, player list and any scoreboard because each integration may choose metadata differently.
- Check a player who has only the edited group as well. This detects a priority adjustment that accidentally hides a label used outside the original report.
Check the result
The intended prefix should appear while the account keeps all its groups and permissions. Confirm the text in every integration you support. If LuckPerms reports the right prefix but one display remains wrong, investigate that display’s cache or placeholder settings instead of changing more metadata.
If the result is wrong
If a different group label disappears, restore the recorded priority in the same context. Avoid adding several direct user prefixes as a permanent workaround; they can hide later rank changes. Keep the original prefix text and priority in the change record so another administrator can reverse the test.