[Feature] Support for Yggdrasil (authlib-injector) accounts

[b33-stinger]

A strong selling point from the old PollyMC was the yggdrasil account support. that way you can easily play with custom names and skins on offline servers with friends. I would really love this feature here too!

[corecommit]

The codebase already has the underlying Yggdrasil token system in place for official Minecraft auth, but adding a proper authlib-injector account type with a custom auth server URL and credentials is still needed. I'm working on it now. Will report back here when it's ready!

[corecommit]

This is now implemented and merged in v9.0.10. I haven't been able to fully test it myself yet — could you grab the latest release and give it a try? Let me know if it works or if anything needs fixing.

[b33-stinger]

Yes i can see and debug it a little. Also if you want a yggdrasil server yourself to test it on unmojang/drasl is a very easy to setup project

[corecommit]

Thanks! Let me know how it goes — and I'll check out drasl for testing.

[b33-stinger]

Okay so from what i have checked so far:

Issues

• Accounts imported from the old PollyMC do not work because the Authlib URL is not imported.
• PollyMC-Continued accounts are not compatible with PollyMC, and vice versa.
• The Cancel button in the credentials dialog does not work (at least under swayFX).
• Accounts do not fetch player skins.

Working

• Accounts can successfully join servers using their correct usernames!

How to get skins working:

1. When sending a request to authlib-injector/authserver/authenticate the server responds with auth data but also with an id.
2. Send a request to authlib-injector/sessionserver/session/minecraft/profile/[ID] (obv replace [ID] with the actual id) and the server will respond with something like this:

{
    "id": "user_id",
    "name": "username",
    "properties": [
        {
            "name": "textures",
            "value": "base64 json skin data"
        }
    ]
}

from this point on i don't really know how to use the skin data 😅

Also, when authenticating a user, the server responds with an additional json list called availableProfiles which contains all profiles registered under the same account. Maybe you could create a little popup menu (when profiles length > 1) and ask the user if they want to import additional profiles (with the same password, just a different name). Though i don't know if that's generic authlib behavior or just the drasl api (i'm currently using)

[corecommit]

I'll fix these and let you know when it's ready.

[b33-stinger]

the PollyMC vs PollyMC-Continued compatibility can be fixed by replacing auth-server-url with authlibInjectorUrl in AccountData.cpp

[corecommit]

the PollyMC vs PollyMC-Continued compatibility can be fixed by replacing auth-server-url with authlibInjectorUrl in AccountData.cpp

Thanks! I will look into it

[b33-stinger]

I have the found the problem for the skins not loading, it's because authlib-injector.jar is not found with getJarPath() (i didn't notice that at all). That's because applicationDirPath() and m_rootPath are paths pointing to the AppImages mount point (/tmp/.mount_Pollyxxxx) rather than static paths like PollyMC used (~/.local/share/PollyMC/libraries/moe/yushi/authlibinjector/<version>/), which means you have to include the jar when compiling the AppImage.
I think it would be a better idea to do what PollyMC did and use a static path to make it alot easier to update the authlib file

[b33-stinger]

I'm currently working on adding a setting for the authlib path and some other options. Will PR when done

[corecommit]

To be clear, I actually didn't fork PollyMC from fn2006's repo

I forked Prism Launcher and then made changes to make it exactly like PollyMC