New Configuration, Ensure auth server and more
Reduced java version requirement
AuthmeVelocity can now be run on Java versions 11 through Java 17
Performance Improvements
Continuations are now used in more events, especially AwaitingEvents to define at what time their processing should end
Configuration Changes
- The configuration format has been changed from hocon to toml
- We have stopped depending on Configurate 4 and reduced the plugin weight by approximately 500kb
- The configurations are not compatible with each other, but it is easy to migrate values between them
API Changes
- The use of singletons throughout the plugin has been eliminated
- Now to access the API you need to use the
ProxyServer.getPlugin("authmevelocity")
method, which returns anOptional<PluginContainer>
from which you have to get theAuthmeVelocity
instance withPluginContainer#getInstance
and cast the resulting value, from there, you simply invoke anAuthmeVelocity#getAPI
. - New proxy events have been added:
ProxyForcedUnregisterEvent
andProxyUnregisterEvent
, which are executed when an administrator unregisters a user and when the same user is unregistered, respectively
Added Ensure first server is an Auth server configuration
These options will make sure that the first server a player connects to is an auth server, otherwise it will try to connect to an auth server and if it fails to do so, it will expel the player
What's Changed
- 2.0.0 | Improved Organization, API changes by @4drian3d in #25
- Bump maven-compiler-plugin from 3.9.0 to 3.10.0 by @dependabot in #26
Full Changelog: 1.4.0...2.0.0