Two prefixes are being pulled from one track even though I have it set to "highest_on_track_" (Obviously I added my track names :D)

Config (Prefix stacking part) https://pastebin.com/CssJXUGQ

A couple of examples. Staff and build rank prefixes are in the same track. So, I've no idea why it's grabbing both the builder rank and staff rank. The donator rank is in a different track called vanilla.

Can you show screenshots of your tracks, and the groups the users inherit from

With the ranks, they each inherit from each other. e.g Titan would inherit the permissions of Elite, or Moderator would inherit the permissions of Helper.

Okay, and

the groups the users inherit from

??

You're leaving me to guess what the problem is at the moment.

I need a description of your current setup, along with what you think the issue is, and what you expect to happen / be shown instead of what's happening at the moment.

Everything you've shown so far looks fine to me.

User inherits from the default, novice inherits from the user and so on. It just goes up the list. The thing is, I have 2 tracks. One donator and one for ranks. Now, the issue is, two ranks are being pulled from the same track. This should not be the case since I have it set to highest_on_track_ranks. It should only be grabbing the highest prefix. Eg. if someone was architect, titan and mod, they should only be given the rank Titan and Mod since titan is the highest one they have on the vanilla track and then mod since its the highest on the ranks track.

Does the correct value show for these players when you run /lp user <user> info?

This is an example of someone who is staff, donator and has a build rank. But, they should only have the donator prefix and staff prefix displayed due to it being set to highest on those tracks.

Can you try running it when they're logged in

So, is that correct?

Well yes... They are in all the correct groups. But the way its being displayed in chat is not.

Ah I see, so should be [Admin] [Mega]??

Can you run /lp debug and send the output you get (again, when that player is online)

Yea, the prefix should be [MEGA] [Admin] or basically (Donator) (Staff)

This is the output given with the user online.

You seem to be using an old(ish) version of LuckPerms, can you try updating?

The issue with the debug command has definitely been fixed already. You can grab the latest version here:
https://luckperms.github.io/

(sorry for not replying - it's hard to keep with with notifications. feel free to ping me in future if I miss things :p )

Hey, @lucko I tried updating and once I restarted my server luckperms decided to disable itself every time. I've tried a couple of the new versions and the same thing happened. I had to revert back to the version I had before and then it worked again. This is what came up in my console once I updated. https://pastebin.com/MJD9ACtg

Should be fixed by vvv

https://hastebin.com/raw/xupujukece - /lp debug

Can you give me the name of a player included in that output who doesn't have the correct prefix listed?

Crud haha, forgot about the player being online. Here is the debug with the user online. https://hastebin.com/raw/warovujimi The players username is Luci_MC

It seems they aren't even inheriting the meta prefix, what's server set to here?

Creative, that is the server the chat is on.

Vanilla is our bungee for vanilla. Meaning both our skyblock and creative.

They only inherit from mega on server=vanilla - meaning that prefix won't be displayed on creative.

I don't see what the problem is?

see: https://github.com/lucko/LuckPerms/wiki/Context

Yes, but the bungee contexts won't apply to the backend server.

This is their current displayed chat. Everything works great besides that builder tag being displayed. So, just making it go to server=creative should fix it?

Basically what should happen is, a normal user without staff should have their ranks displayed like
[MEGA] [Architect] :
Once they're given a staff rank it should hide their [Architect] prefix (in lucys case it should take designer) and then add their staff tag [ADMIN]

Hard for me to comment on that without knowing how each of those groups are inherited and how your tracks are setup.

The debug log confirms that this isn't a bug, rather a configuration issue, so I'll close the "issue".

I'm happy to help you sort the configuration, but it's probably easier to do that in Discord or something like that. (also happy to help here if you post the necessary info)