
Vault Suffix retrieval inconsistency
Closed this issue · 11 comments
PlaceholderAPI suffixes do not work. My current highest priority suffix is the number "2": http://i.imgur.com/MljAUya.png output of /lp user (user) info
But my suffix is "1" which is a lower priority suffix.
Output of /papi parse %luckperms_suffix% is "1", which is a suffix I do have, but is lower priority.
I believe the ranks for suffix and prefixes and so on is reversed, it goes from low to high meaning rank 1100 is owner and 1 is default...
@BiGUNMAN Use the Vault placeholders instead.
@lucko Vault placeholders also display "1" instead of "2".
@lucko Here's output of /lp user (user) meta info: http://i.imgur.com/onB6mE7.png
Here's /lp info: http://i.imgur.com/rZ3sxm5.png
Kinda inconsistent?
Yeah - very strange. I assume re-logging doesn't help? There's no reason why that data would be applying if you don't even have it.
@lucko Hi, this is still an issue, could you reopen it? I can try and provide more information, idk what else you'd like to know. Take note, the suffix is in a non-primary group the user has. There are no suffixes overriding it, the priorities are set properly (with a lower number being a lower priority). It seems the meta isn't displaying the correct data but /lp user (user) info does.
There absolutely must be a reason why the other is taking priority.
Can you try setting the vault-server
config option to the same as server
. (make it "survival")