Bukkit

This version has some bugfixes, Improvements and new functionality.

Servers having a large playerbase could have lag issues when someone logged in/out.
The method on checking the player in the profile files is now optimized.

I added a "Custom Chart" to bStats so it shows the AmkMcAuth Registered playerbase (profiles) per 100 players.

Login en Change password commands where preveously logged onto the Server logs.
You can now log in / change password in two ways:

1: normal method using the command: /login [password] 

2: new method using hidden chat message: t\login [password]

By using the t\login the user is not issuing  a console command, but a chat message that will be dropped/hidden by AmkMcAuth.
So users can now Login without spamming the console logs. The t\login is the default method shown in the help message.
Both methots can be used, but it is configurable (in config.yl) what method is preferred, eg. showing up in the help message.

The "kick_if_already_online" flag is now working correctly. if a player is already logged in and an other player is logging in with the same player name this flag wil now correctly kick the already logged in player if this is set to "true".
Is this flag is set to "false" then the new player (with the same name) cannot log in and gets a message that he is already logged in.

Looking at the old RoyalAuth project pages a saw a request for allowing the not logged in players to move for a while before the where put the the saved position. Until now a not logged in players could not move. If players was trying to move, AmkCmAuth resets the position to the saved position. This could trigger the AntiCheat plugins (like NoCheatPlus) trigger for flying, fly-hack eg. 
Now you can configure AmkMcAuth that it is allowing players to move for a certain time before they are reset to the saved position.

An other request i saw was the abillity to configure the maximum amount of playersnames that could be registered from the same Ip-Address.
In this version you can configure this maximum. The default is 50 (users_per_ipaddress: 50), so a maximum of 50 playernames can be registered from the same IP-Adress. If you set this to like 1, only 1 player can be registered from a single IP-Address.

This will make it difficult for hackers/cheaters to register many playernames. 

If you set this to 0, no IP-Checking is done (ignoring the registered users per Ip-Address -check).