Fix disconnect reason documentation when cracked users joins (Fixes #9)

This message changed a couple of versions ago

README.md

@@ -123,8 +123,9 @@ Yes, indeed. Therefore the command for toggling the fast login method exists.
 of a cracked player that has the same username. The player have to proof first that it's his own account.
 2. We only receive the username from the player on login. We could check if that username is associated
 to a paid account but if we request a online mode login from a cracked player (who uses a username from
-a paid account), the player will disconnect with the reason bad login. There is no way to change that message
-on the server side (without client modifications), because it's a connection between the Client and the Sessionserver.
+a paid account), the player will disconnect with the reason "bad login" or "Invalid session". There is no way to change
+that message on the server side (without client modifications), because it's a connection between the Client and the
+Sessionserver.
 3. If a premium player would skip registration too, a player of a cracked account could later still register the
 account and would claim and steal the account from the premium player. Because commands cannot be invoked unless the
 player has a account or is logged in, protects this method also premium players

bukkit/src/main/resources/config.yml

@@ -16,7 +16,7 @@
 #
 # Furthermore the premium player check have to be made based on the player name
 # This means if a cracked player connects to the server and we request a paid account login from this player
-# the player just disconnect and sees the message: 'bad login'
+# the player just disconnect and sees the message: 'bad login' or 'invalid session'
 # There is no way to change this message
 # For more information: https://github.com/games647/FastLogin#why-do-players-have-to-invoke-a-command
 autoRegister: false
@@ -49,4 +49,16 @@ premiumUuid: false
 # This means this plugin doesn't need to create a new connection to the Mojang servers, because
 # the skin data is included in the Auth-Verification-Response sent by Mojang. If you want to use for other
 # players like cracked player, you have to use other plugins.
-forwardSkin: true
+forwardSkin: true
+
+# Database configuration
+# Recommened is the use of MariaDB (a better version of MySQL)
+driver: mysql
+host: localhost
+port: 3306
+database: FastLogin
+username: myUser
+password: myPassword
+# If you use an existing database which will be used by other programs too
+# you define here a prefix, to prevent conflicts.
+tablePrefix: ''

pom.xml

@@ -83,4 +83,20 @@
             </resource>
         </resources>
     </build>
+
+    <dependencies>
+        <!--Database pooling-->
+        <dependency>
+            <groupId>com.zaxxer</groupId>
+            <artifactId>HikariCP</artifactId>
+            <version>2.4.5</version>
+        </dependency>
+
+        <!--Logging framework implements slf4j which is required by hikari-->
+        <dependency>
+            <groupId>org.slf4j</groupId>
+            <artifactId>slf4j-jdk14</artifactId>
+            <version>1.7.20</version>
+        </dependency>
+    </dependencies>
 </project>

universal/pom.xml

@@ -29,6 +29,7 @@
                     <artifactSet>
                         <includes>
                             <include>${project.groupId}:*</include>
+                            <include>com.zaxxer:HikariCP</include>
                         </includes>
                     </artifactSet>
                 </configuration>