Using the skin from SkinsRestorer, if there's no skin on Ely.by about chrly

[erickskrauch]

Hello. Thanks for the well described issue 👍

For internal reasons, the production of the Ely.by is now using Chrly 4.1.1-ely, which still uses outdated and broken links to Mojang skins. In subsequent versions, we have fixed it, but unfortunately, we can't use newer versions yet.

I really need to finalize the event_dispatcher_refactoring branch and fix #13 to migrate to the latest version of Chrly in our production.

I think I can do it in the next few days. Chrly will no longer use outdated and broken links for the unknown usernames. A little later we'll also restore the proxy of signed skins, so you won't need a skin restorer either.

[erickskrauch]

@Brikster, we had to roll back the latest version of chrly to 4.1.1-ely because it caused problems with the existing authlib implementation. We have made the necessary fixes and are waiting a week for the update to reach all users. Tomorrow we'll enable the latest version again which will solve the problem.

[erickskrauch]

@Brikster, please check the behavior now. At the moment, the production uses the latest version of Chrly from the master, with all fixes, including the elimination of the old Mojang's API.

[Brikster]

Now on production:

And client gets null textures: https://hastebin.brikster.ru/uqirakivek.shell

[erickskrauch]

🤔
Ok, I'll investigate it deeper.

[erickskrauch]

@Brikster, for now, all TL users should already receive the update. Please check your cases. Everything should work exactly as you described.

[erickskrauch]

I'm gonna close this issue. If there's still a problem, please let me know.