-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
what is SetSkinURL for authlib-injector auth server #9
Comments
Haha I'm halfway through writing the config docs, it's not important to set that option, currently it's only used for the "challenge skin" feature. |
Ah lol just found it as u said this, i assume itd be /skinlib/upload |
And I can use my authlib injector auth server as fallback to allow either, so i can migrate my players over time before full deprecation of the authlib injector server? |
And maybe u can include this info in the docs. Or say to upload the skin on it yourself and set it to /skinlib/show/ID, where ID is the ID of the challenge skin |
Yes that's intended to work (eventually), though I haven't tested falling back to an authlib-injector server yet. |
Could it possibly work rn? I can test it |
Yeah will do. But no, that wouldn't work since every challenge skin is different, to prevent an attacker from registering a victim's account right after the victim sets their skin. I think a link to the "set skin" page is convenient enough.
Go for it, let me know. I'm guessing some routes may be missing/not standardized on the authlib injector side but we'll see I should probably make a matrix room huh |
Title
The text was updated successfully, but these errors were encountered: