Description

I have no idea how or why, but it didn't happen, and it's not happening now. It happened yesterday, and only once, but it was enough to make a man a fortune.

What's the problem? I have a reward system in DeluxeMenu, when a player has played for 5 minutes they can take that reward, after that they are granted rewarded.1, and they can't take it anymore. But when giving permission, the plugin wrote that it already existed, but in fact it was not. Also, the player bought essentials.msg, which was "issued", but in the morning, comparing the log and the player's rights in /lp user permission info, I realized that the right to the command, which he bought, he did not have. From this I concluded that the problem is in luckperms. Here is my DeluxeMenu file https://paste.md-5.net/velavamuto.bash

Server Details

This server is running FlamePaper (1.0.2) for 1.8.8 by LinsaFTW

LuckPerms Version

Running LuckPerms v5.4.64

Logs and Configs

https://gist.github.com/Regomy/83a1c4bf1689822c0faf21706940cedc

Found this in the logs: https://paste.md-5.net/emusarofom.cs
But I don't use bungeecord or velocity. @lucko please helpp

Found this fragment AuthMe kicked out the player, because of the wrong nickname, but luckperms still changed his uuid. https://paste.md-5.net/nulihusicu.cs

In general, the problem is that AuthMe does not let the player with the nickname CAT, if he was registered cat. But luckperms still changes his uuid, and it turns out that if you log in with cat again, the rights will not be given.

up

@lucko please help me

These symptoms sound like improper data saving, most likely due to improper shutdown of the server. Can you check shutdown and startup logs for any errors pertaining to LP?

These symptoms sound like improper data saving, most likely due to improper shutdown of the server. Can you check shutdown and startup logs for any errors pertaining to LP?

Perhaps I would have answered you, but why were others doing well? For example, this player tried from other accounts, but there was no such bug.

Please stop mentioning Luck, it won't affect response time.

Offline mode causes a ton of issues, especially with UUIDs. LP is not changing the UUID (under normal circumstances that should never be done by any plugin). At one point a user with a given name logged in with an online mode UUID, but are now connecting with an offline mode UUID. LP's now confused and doesn't know which "player" to modify, since LP, like most sane plugins, stores data under UUIDs, not names.

Like most offline mode problems, this can be solved by switching back to online mode and not supporting piracy.

Please stop mentioning Luck, it won't affect response time.

Offline mode causes a ton of issues, especially with UUIDs. LP is not changing the UUID (under normal circumstances that should never be done by any plugin). At one point a user with a given name logged in with an online mode UUID, but are now connecting with an offline mode UUID. LP's now confused and doesn't know which "player" to modify, since LP, like most sane plugins, stores data under UUIDs, not names.

Like most offline mode problems, this can be solved by switching back to online mode and not supporting piracy.

Unfortunately, this will not solve the problem, and I will leave 99% of the players, because all play with pirate. Another 1 argument would be the fact that many use luckperms on the pirate, and maybe even with authme, so I hope you will come to your senses, and be able to fix it.

This is not an issue a) from LuckPerms b) LuckPerms can resolve.
LuckPerms is not changing the player UUID, so there is nothing LP can change about that behaviour.

many use luckperms on the pirate, and maybe even with authme

Yes, that is true, and for many of those, it works fine.

LuckPerms works by identifying players with their UUID, and in offline mode those two usernames correspond to two different IDs, so they are effectively two different players. It does not change a player's username or ID, nor should it have to guess.

This is not an issue a) from LuckPerms b) LuckPerms can resolve. LuckPerms is not changing the player UUID, so there is nothing LP can change about that behaviour.

many use luckperms on the pirate, and maybe even with authme

Yes, that is true, and for many of those, it works fine.

LuckPerms works by identifying players with their UUID, and in offline mode those two usernames correspond to two different IDs, so they are effectively two different players. It does not change a player's username or ID, nor should it have to guess.

The problem is in your plugin! In the logs you can see that it RECORDED the uuid of the player, because of the nickname, when authme did not let the player with the "wrong nickname" to the server.
These are errors, and let's at least look at the logs, as the player nayupala more than 10 yolam, ok, yes! What kind of support that sends on all 4 sides, just wrote that luckperms does not work with uuid. And in the logs what? Magic luckperms from another world?