search

kyngs / LibreLogin

Open-source, multiplatform, and highly customizable authentication plugin with outstanding features and API.
Mozilla Public License 2.0
169 stars 55 forks source link

UUIDs became completely messed up (using "mojang" type of UUID creation) #43

Closed RealKomander closed 1 year ago

RealKomander commented 1 year ago

So basically I have a whitelisted server in my network and when I try adding new players to it, it adds them with wrong UUIDs (cracked probably, but have no way of checking that) even though all of these players are mojang-authorized. I tried experimenting with it, but it didn't matter: /autologin doesn't help, neither does /cracked. When I try adding them via UUID through console, it thinks that the UUID is a nickname and adds a player with this name and gives it another UUID. I don't know what the hell is going on, I'm stupid as well, hopefully I'm the only one experiencing this

2023-02-04_15h10_11 2023-02-04_15h11_11 2023-02-04_15h12_33 2023-02-04_15h13_01

kyngs commented 1 year ago

The whitelist command is used to add names, not UUIDs. When you attempt to use UUID in it, it will just consider it a name. If you set the "MOJANG" UUID creator, new players which have premium nicks will get premium UUIDs.

Remember, that the configuration option only affects new players, therefore if you had a different setting and someone joined, they will keep their UUID even if you change the option afterward. You can remove a player from the database using /librepremium user delete , then if they join, their UUID gets generated according to the new option.

RealKomander commented 1 year ago

It is already set to 'MOJANG'

kyngs commented 1 year ago

Was it always set like that? Was it set like that when the users that are "bugged" first connected?

kyngs commented 1 year ago

Also, the player "VANFUL" does not have a registered account.

RealKomander commented 1 year ago

Was it always set like that? Was it set like that when the users that are "bugged" first connected?

Yes, it was set like this from the very beginning.

Speaking about VANFUL - yeah, this is really confusing. I can't find him on nameMC, but he can easily play on any online server

He's not the only one experiencing it though, it happens to everyone, he was just the last player I added

kyngs commented 1 year ago

Was it always set like that? Was it set like that when the users that are "bugged" first connected?

Yes, it was set like this from the very beginning.

Speaking about VANFUL - yeah, this is really confusing. I can't find him on nameMC, but he can easily play on any online server

He's not the only one experiencing it though, it happens to everyone, he was just the last player I added

API says that he indeed has an account, probably a bug in namemc. As you have shown in this image, he indeed does have the correct UUID (https://api.mojang.com/users/profiles/minecraft/VANFUL) image

However, if you have online-mode set to false, the whitelist will treat the names you will give to it as if they were cracked. No matter whether they are or not.

You can set librepremium to operate in cracked mode, then it should work correctly. Remember what I said earlier about it only affecting new players.

kyngs commented 1 year ago

Closing due to inactivity.