Correctly specify non_email_login for standardized launchers

[hykilpikonna]

This authlib standard requires all servers to have feature.non_email_login = true if it doesn't require the log-in username to be an email.

Drasl doesn't require the username to be an email, but did not add this field, which defaulted to false.

HMCL (launcher) queries Drasl, and see this missing field, and think that this server require usernames to be email, so it forces users to input an email.

Finally, users can't log in via HMCL because their username is not an email.

References:

• [-] Remove username=email requirement for custom authlib servers HMCL-dev/HMCL#5668
• Standard specification: https://github.com/yushijinhun/authlib-injector/wiki/Yggdrasil-%E6%9C%8D%E5%8A%A1%E7%AB%AF%E6%8A%80%E6%9C%AF%E8%A7%84%E8%8C%83#%E5%8A%9F%E8%83%BD%E9%80%89%E9%A1%B9

[Copilot]

Pull request overview

Updates Drasl’s authlib-injector metadata to comply with the authlib-injector “standardized launcher” requirement by explicitly advertising that the server supports non-email usernames, preventing launchers (e.g., HMCL) from forcing email-only login.

Changes:

• Add feature.non_email_login to the authlib-injector meta JSON schema.
• Set feature.non_email_login = true in the /authlib-injector response.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[evan-goode]

Thanks, I've been meaning to do that.