Add second attemp login -> cracked (Fixes #51)

core/src/main/java/com/github/games647/fastlogin/core/FastLoginCore.java

@@ -11,6 +11,7 @@ import java.sql.SQLException;
 import java.util.Map;
 import java.util.UUID;
 import java.util.concurrent.ConcurrentHashMap;
+import java.util.concurrent.ConcurrentMap;
 import java.util.concurrent.ThreadFactory;
 import java.util.logging.Level;
 import java.util.logging.Logger;
@@ -30,9 +31,16 @@ public abstract class FastLoginCore {
     }
 
     protected final Map<String, String> localeMessages = new ConcurrentHashMap<>();
+
+    private final ConcurrentMap<String, Object> pendingLogins;
+
     private MojangApiConnector mojangApiConnector;
     private AuthStorage storage;
 
+    public FastLoginCore(ConcurrentMap<String, Object> pendingLogins) {
+        this.pendingLogins = pendingLogins;
+    }
+
     public void setMojangApiConnector(MojangApiConnector mojangApiConnector) {
         this.mojangApiConnector = mojangApiConnector;
     }
@@ -110,6 +118,10 @@ public abstract class FastLoginCore {
         return false;
     }
 
+    public ConcurrentMap<String, Object> getPendingLogins() {
+        return pendingLogins;
+    }
+
     public void close() {
         if (storage != null) {
             storage.close();

core/src/main/resources/config.yml

@@ -21,6 +21,14 @@
 # For more information: https://github.com/games647/FastLogin#why-do-players-have-to-invoke-a-command
 autoRegister: false
 
+# This is extra configuration option to the feature above. If we request a premium authentication from a player who
+# isn't actual premium but used a premium username, the player will disconnect with the reason "invalid session" or
+# "bad login".
+#
+# If you activate this, we are remembering this player and do not force another premium authentication if the player
+# tries to join again, so the player could join as cracked player.
+secondAttemptCracked: false
+
 # If this plugin detected that a player has a premium, it can also set the associated
 # uuid from that account. So if the players changes their usernames, they will still have
 # the same playerdata (inventory, permissions, ...)