loadProfile(name) returns NULL on Bukkit side when using BungeeCord. about fastlogin HOT 7 CLOSED

There are also those 2 errors on Bungee's StartUp (Changes already done and re-applied on every startup?):
http://pastebin.com/4ciGVjhV

from fastlogin.

It seems that when BungeeCord is detected, the plugin doesn't even load the Database in the Bukkit side.

How can I send the request to the Bungee side of the Plugin, then?

from fastlogin.

And this function to get whether a player is Premium or not (Inside AsyncPlayerChatEvent):
plugin.getCore().getStorage().loadProfile(e.getPlayer().getName()).isPremium()

You don't get a NPE on loadProfile. getStorage() returns null if BungeeCord is enabled and this is intended for less configuration work and produce less stress on the MySQL database. So there is only one management component which takes care of it.

There are also those 2 errors on Bungee's StartUp (Changes already done and re-applied on every startup?):
http://pastebin.com/4ciGVjhV

You can ignore those errors. See the logging level. They are just used for debugging. Sadly there is no safe way to drop and create a new index without producing a new error.

How can I send the request to the Bungee side of the Plugin, then?

The plugin currently communicates over plugin-channels and it then sets a bukkit metadata field. You can make use of it. (although it's set before the proxy-key validation)

BTW: I'm thinking of removing proxy-key validation, because if FastLogin started up correctly in BungeeCord it will prevent fake messages from hackers.

from fastlogin.

Could you give me an example on how to request if someone is Premium to the BungeeSide and how to receive the answer?

from fastlogin.

Make an extra BungeeCord plugin and communicate over plugin-channels. Register the channel and define a custom protocol message. Something like

YourPlugin
IsPremium
Playername

read the message on the bungeecord side and then start a database query. You could also use the sessions, because the sessions in BungeeCord only expire on disconnect. After you got a result send the result back over the plugin-channel something like this:

YourPlugin
PremiumCheck
PlayerName
boolean

from fastlogin.

Ok, I think I got it.

from fastlogin.

I solved the problem by Listening for FastLogin "AUTO_LOGIN" plugin messages and adding those users to an ArrayList.

If the list contains the name, the player is Premium (as being Auto-Logged in), otherwise is Cracked. 😝

from fastlogin.