Description

I think somehow the database get corrupted, but somehow can read it. So I removed all files and it start to work, I send you the file and you can try self.

As my old issue #3289 (comment) I think same thing happen there too. this server editor https://luckperms.net/editor/WYakBj7BDS

and what it say ingame and yes I run that command and it say you already set that command.
https://i.imgur.com/b198frm.png

So the problem I experiences it can´t read the players permissions, but the editor can see the permissions set. I use defult settings here (so locally db). my zip not contains any sensitive info at all.
LuckPerms.zip

database
luckperms-2022-07-06-21-13.json.gz

.

Reproduction Steps

don´t know

Expected Behaviour

Should not say your don´t have permission.

Server Details

1.16.5

LuckPerms Version

5.4.21

Logs and Configs

No response

Extra Details

No response

So don´t close this and say I need set lp user broken_arrow1 permission set luckperms.* true I try that several times and it say I already set it.

Use verbose to debug. Might be a issue with uuids?

Use verbose to debug. Might be a issue with uuids?

Is online server. So UUID should not be a issue, fare as I see is it bug in luckperms.

And ofc I use verbose and that not give more info (that only say you have right permission).

I also debug luckperms https://pastebin.com/BDhcEK1G this is the checks it doing for permissions. I don´t know how you set it up but seams not check for * permissions.

Update: Issue fixed.

To clarify:
The user never intended to sync their permissions. He/she handles their permissions separately intentionally despite running a network. This was not the problem whatsoever. UUID's were not the problem either.

The fix:
The user had a relatively old config file. The setting apply-default-negated-permissions-before-wildcards: was set to true by default for him/her. This was changed a while ago. I compared their config, we had a nice talk on discord and setting this to false resolved the problem.

Yes, we could start pointing fingers now. I don't blame either side as it's common to try to sync permissions (and assuming this to be the goal) or configure a network incorrectly, expecting UUID issues. For the average user, this setting isn't easy to spot, nor do they know about the flipping of it, unless you're an idiot like me and dig up old code and change-logs. I'd call this an even case.

~Cheers!