Authentication with Alpha/Beta servers

Beta/Alpha (Legacy) Minecraft servers frequently require users to verify their ownership of a username in order to play. The verification of usernames allows server owners to effectively block cracked users who are primarily made up of Griefers, Hackers and rule-breakers while allowing normal players to connect.

Beta Evolutions (BetaEVO)

Beta Evolutions is a mod for Beta 1.7.3 which provides various fixes for skins, capes, sounds and authentication allowing for players to easily authenticate with servers. Multiple versions of Beta Evolutions are available, with a Beta Evolutions Authentication Fix being available for those who want to authenticate, without causing compatibility issues with other mods.

Supported Launchers

The following launchers support authentication with servers:

MineOnline by CraftCodie
BetaEVO Launcher by JohnyMuffin
More to come





Single Server Registration (SSR)

SSR allows you to register an account on a server allowing you to play via an in-game login system by verifying your ownership of the Minecraft account on a modern Minecraft server. This option is good for those who want to avoid mods/launchers and play quickly.



FAQ

Unfortunately, Mojang has failed to maintain the authentication servers for Beta/Alpha versions meaning that the Legacy community has had to make alternatives to verify users outside of the typical authentication system to increase the safety of servers of otherwise cracked servers.

Launchers that provide authentication use the Beta Evolutions (Auth) method by automatically authenticating with Nodes when the game starts, or the user connects to a server.

Beta Evolutions (Auth) is a protocol allowing for clients to authenticate with Nodes (Beta Evolution servers) using the Mojang verification API similar to how a client would normally authenticate with a server. From this point, servers can verify a user is authenticated by contacting a Beta Evolutions node.

If you are a developer, and would like to see the code that runs client side, please click here.

SSR allows users to verify their ownership of a Mojang account by connecting to a modern server that uses standard Mojang authentication proving a users ownership of an account. A user is then added to an exception list of the Legacy server allowing them to connect with authentication, and verify themselves via a login command with a password provided.

This method is unrecommended if Beta Evolutions (Auth) is available to you as you need to do SSR with every server you wish to connect to, and it only proves your ownership of the account once compared to every 24 hours with Beta Evolutions. 

Beta Evolutions (Auth) works similar to how the client normally authenticates with a release server, meaning servers don’t get access to anything sensitive such as your credentials or your account token. For the process of authentication to work, your username and IP are stored for the duration of your authenticated period (24-48 hours), however, this is no additional information that a server wouldn’t already get by you connecting.

SSR verifies the user by them connecting to a modern server, meaning, privacy is the same as if you were connecting to any normal modern server.

Supporting Beta Evolutions (Auth) is incredibly easy with addons for authentication plugins such as AuthMe already existing. SSR is a bit more difficult, however, assistance can be rendered with the implementation. If you would like to implement these, please contact Johny Muffin on Discord (Johny Muffin#9406) or via email at [email protected].

The website was designed with Mobirise