Premium players sometimes do not register.. about fastlogin HOT 16 CLOSED

Is there a possibility to check if the user is in the FastLogin database instead of the AuthPlugin database? Because I have seen ~5 players that didn't exist in the FastLogin database but they did exist in the AuthMe database. So they still need to use /login password and the didn't have a skin.

FastLogin does that to protect cracked players from stealing their account. Do you mean those should have been auto registered?

from fastlogin.

Yes those accounts should be autoregistered, they are premium (for what NameMC says), but they only got added to the AuthMe database. And because FastLogin checks if the player is registered there it won't make a request to Mojang so those accounts stay "locked" for the owners until I add them manualy.

from fastlogin.

Maybe they were registered even before FastLogin knows those players

from fastlogin.

No they are not, I installed AuthMe & FastLogin together, my server was premium only before I stared using FastLogin and both database where empty :)

from fastlogin.

I could be caused by an old version. Are they new players, because FastLogin doesn't remove anything?

from fastlogin.

Well, the player will get autoregistered (They have an account) but they don't know the password. And the player isn't added to the FastLogin database. So the autoregister thing works? But the autologin doesn't because the player doesn't exist in the FastLogin database.

from fastlogin.

FastLogin only inserts the player record if it got a success notification from bukkit.

Are those new players?

from fastlogin.

Kind off, they have been in that lobby map before but then the lobby didn't have a account on AuthMe because I didn't have that plugin.

from fastlogin.

So I mean new authme players?

from fastlogin.

Yes they are new AuthMe players, but if I'm the only one with this problem I can make a small work around for myself. And it only seems to happen to ~5 players and my server has 1050 players registered since I'm using fastlogin.

(My idea (for myself (isn't a good idea for a public plugin I think.);
When a player joins the server and they didn't login within 10 seconds > send a request to mojang that asks if the user is premium, and if he is I'll add them manual to the fastlogin database using a SQL query. I think that should work, but it isn't the best solution :P

from fastlogin.

And it only seems to happen to ~5 players and my server has 1050 players registered since I'm using fastlogin.

Report me if it happens again for a new player. I'll look into it maybe I find something.

When a player joins the server and they didn't login within 10 seconds > send a request to mojang that asks if the user is premium, and if he is I'll add them manual to the fastlogin database using a SQL query. I think that should work, but it isn't the best solution :P

The problem is you have to validate that it's really the owner of that premium account. This can only be done during the login phase.

from fastlogin.

The problem is you have to validate that it's really the owner of that premium account. This can only be done during the login phase.

I know, but I think fastlogin handles that? if FastLogin thinks a premium player is cracked (and some random player joined using that playername) and my plugin will make that player (the name & UUID from mojang) premium by adding them to the fastlogin database. And kicking them after its done.

And if that player joins again (cracked) he won't be able to login because he is set as premium within fastlogin. So only the owner will be able to play after the manual insert?

(Namecheck & Autoregister == true)

from fastlogin.

This means you want to make premium players be able to steal the account of a cracked one (same username)?

from fastlogin.

Oh no, I'll make a get request to Mojang first to check if the name is premium :) And if he is I'll add him.

from fastlogin.

But this means cracked player accounts who uses premium usernames are insecure. Examples

New premium player bough that name
Premium player changed his/her name to that cracked player

from fastlogin.

Hmm indeed, I think that chance is small on my server. I only have 19 players as cracked (Authme rows - Fastlogin rows) So that isn't a big problem.

But I think i can do;
Runnable (10 seconds)
Didn't login yet? >
Request UUID from mojang >

Player is cracked > Add him to my own database (only for cracked players)

Player is premium > Check if that name exists in my own database if not >
Register player in the FastLogin database and if he is in my own database just return and do nothing.

EDIT:
I think i can lower the waiting time to 5 seconds, so all cracked players will be added to the "cracked" list.

from fastlogin.