Drasl isn't Piracy

Drasl is a third-party re-implementation of Mojang's authentication protocol, dubbed Yggdrasil. It lets you play minecraft, use skins and custom capes, maintain several in-game accounts/nicknames and several other features.

It also has mechanisms that let you verify account ownership on other login servers, including Mojang's official servers. It has been explicitly vetted as okay by Mojang's Legal Team in relation to the EULA as long as account ownership can be verified.

Despite this, people often write of Drasl, FjordLauncher, and the request to add Third-Party Yggdrasil Server support is often rejected under the premise of enabling piracy, or breaking the EULA by implementing this feature.

Your Concern is Valid

First off, let me clarify that your concern is valid.

Making projects in and around Minecraft often requires you to abide by the EULA, or else risk getting in "friendly contact" with Microsoft's or Mojang's legal team.

So, it's totally understandable that you, as the maintainer of a launcher or perhaps a mod, don't want to implement support for third-party yggdrasil implementations in fear of possible repercussions.

Though, your fear isn't necessary, because if implemented right...

These projects are EULA-Compliant.

If you look at FjordLauncher's README, near the top of the README it reads:

I plan to someday try again to upstream these changes, since I believe most Prism Launcher users and developers agree that alternative authentication servers should be supported, with appropriate safeguards against piracy.

Emphasis mine, the FjordLauncher project (which is under the same leadership as Drasl) clearly states that safeguards against Piracy can stay in the launcher, just like with Offline Account support.

Additionally, the Drasl developers (hereby referred to as Unmojang) have contacted Mojang's legal team asking about whether or not a project like Drasl would be against the EULA. Their response was as follows:

The use of a Custom Authentication Server may or may not violate the Minecraft End User License Agreement (EULA), depending on several factors. As long as you ensure that players are using legitimate Microsoft accounts and a valid copy of Minecraft, the use of a Custom Authentication Server may not be problematic.

That is to say, Mojang Enforcement already confirmed that Drasl is a-okay under the EULA, as long as it is used in a context with mechanisms in place to check for legitimate copies. This is implemented both in FjordLauncher (requires Microsoft login) and also in Drasl itself, as it can use skin verification against Mojang servers to verify that you do in fact own a valid copy of Minecraft.

This mechanism can easily be tried out against https://drasl.unmojang.org, where to register you must complete a skin-based challenge to prove ownership of a paid Minecraft account.

Why would anyone implement support, regardless?

There is a few major reasons, at least for me. A longer list is found in Drasl's README, but these are points which I find particularly important.

1. It fixes old, defunct Minecraft versions basically automatically.

With Loki, Unmojang's Java-Agent that allows any version of Minecraft to work with Drasl and other Yggdrasil servers, online functionality can be restored for really old versions of Minecraft, down to Minecraft "Late Classic".

Not only can you get online, but Drasl 4.0.0 and later also implements the Classic Protocol, used before "Late Classic", making even more versions of Minecraft playable.

2. It leaves you unaffected of Ban Waves and Chat Reporting.

Chat Reporting and the recent (as of July 2026) waves of high-profile content creators being banned (more here) are an example of something that you can entirely avoid by using a third-party login server, like drasl.unmojang.org. Because your client won't "phone home" to Mojang and your account won't match an existing Mojang UUID, any reports sent about your behavior to Mojang would be invalid.

This leaves you free to enjoy the game without fear of being falsely banned. This does not mean reporting doesn't work anymore but your main MC account is safe.

3. Your players can have several player accounts, i.e for automation, camera accounts or else.

Many people, especially content creators, use secondary accounts to record timelapses, show things off in spectator, or to demo automation projects that rely on player accounts.

Whatever it is, as a Drasl Admin you can give people more than 1 player account they can log into at a time.

4. Transparent and HD Skin support.

Drasl doesn't follow the same limitations as vanilla Minecraft when it comes to skin files, or at least it doesn't have to. If your client is configured to support it, Drasl can serve high-resolution skins or skins with transparent layers completely as-is, which means more customization options for you.

5. Censorship Circumvention.

There are some countries, like russia, where even after having bought the game, playing online can be challenging or impossible because of sanctions from Mojang/Microsoft's side, or blocks from Russia's side.

Both of these issues are fixed when using a third-party Yggdrasil server, as it lets you log in and join servers using the same Yggdrasil server without requiring a working connection to Mojang. The launcher can still verify ownership regardless.

There are many other valid reasons for hosting or using a third-party auth servers, and most of them aren't related to or enabling piracy.

This doesn't mean people don't use these tools to pirate the game, however Drasl or launchers supporting third-party Yggdrasil servers don't enable this.

If they did, then Mojang wouldn't have added official commandline arguments to change the desired Yggdrasil server, starting from Minecraft 1.16.x. Additionally there are plenty easier ways of pirating the game that don't involve setting up Drasl, that pirates will feel drawn to more.

These arguments, for what it's worth, are as follows:

-Dminecraft.api.env=custom
-Dminecraft.api.auth.host=https://drasl.example.com/auth
-Dminecraft.api.account.host=https://drasl.example.com/account
-Dminecraft.api.profiles.host=https://drasl.example.com/account
-Dminecraft.api.session.host=https://drasl.example.com/session
-Dminecraft.api.services.host=https://drasl.example.com/services
-Dminecraft.api.discovery.host=https://drasl.example.com/discovery/minecraft/client

These commandline arguments are available starting from Minecraft 1.16 and later.