v0.4.4 - Yet Another Fix for Velocity
So sorry that this update took so long, I was celebrating Thanksgiving with family and was unable to work on the project!
This update fixes the issue of the plugin disabling itself on Velocity, while copying events around I accidentally copied the disable method into the player join method so whenever a player joined the plugin got disabled. So it has been fixed!
v0.4.3 - Fix for Velocity
This update patches 2 issues with velocity:
- The mysql library wasn't being downloaded properly
- Users wouldn't be authed due to the fact that Velocity hard bakes their url with /session/minecraft/hasJoined into it and it was messing with the authentication.
v0.4.2 - Fixed Update Checker
There was a small oversight with the update checker where it only checked for the newest version, which works great, until I release a patch for a specific loader. So I updated it to check the latest version and loader to ensure that you get update notifications for your server only!
v0.4.1 - Patch for NeoForge and Fabric
This is a small and quick patch to fix the loading of the mod to ensure it is loaded before mixins make their changes.
v0.4.0 - Update Checker
Update Checker
I have added a simple update checker so that you can always be notified when there is a new release! It will notify the staff with the permission alwaysauth.admin and notify console when the server is started.
This feature can be disabled within the config by disabling check-updates
Other Things
I aso removed some annoying debug messages that were left over from me testing the config system. As well as some other non-necessary messages
0.3.0 - Authentication & New Versioning Scheme
Authentication
Firsts things first, Authentication! I've added a simple secret key that is required to access the AlwaysAuth auth server instance, this will stop people from creating fake authentication requests.
On top of this the database will now have the ip address encrypted with the same secret key, this will ensure any database leaks do not leak people's ip's (unless someone got a hold of your secret key as well).
New Config Options
The config is setup to auto update, so you shouldn't have to regenerate it or anything. But just so you know there are two new values:
authentication-enabled=true
secret-key=GENERATED ON STARTUP
Standalone Servers
If you are using a standalone instance for multiple servers, simply all the servers need to match the standalone instance's secret key, and then they will be able to connect to the standalone server.
Disabling Authentication
If you so choose you can disable authentication which can leave you open to possible false authentication attacks on your server, this is highly not recommended but left as an option if you so choose too for whatever reason.
Note this will not disable the database IP encryption.
New Version Scheme
I will be implementing (properly) the SemVer format which follows the
Major.Minor.Patch format, so right now we are on Major version 0, Minor version 3,
and Patch version 0.