-
Notifications
You must be signed in to change notification settings - Fork 551
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
Exception while requesting skin jphipps3 #4046
Comments
you are using an outdated version, update to latest version on https://blob.build/ |
Oops, sorry, didn't notice. I'll update and see if that fixes it. Edit: Yeah I am? DEV 1104, and the commit number is the same as is on the download site. |
...the issue isn't resolved. i have the most up to date version |
1104 is not the latest on the build site. 1104 is the most recent on the discord, but not blob build |
that is a site |
Safari's bugging I guess. Said server not found. And I got my version off https://thebusybiscuit.github.io/builds/TheBusyBiscuit/Slimefun4/master/ . Is that not where I'm supposed to be downloading it from? That's what the github links to. I'll edit once I try the new version. |
It is not where you are supposed to be getting it too but good point ill make a PR to update the github page |
1112 is the latest on https://blob.build |
Looks like it was fixed after updating to the version on https://blob.build/ , sorry for the confusion. |
❗ Checklist
📍 Description
I've noticed this on a few servers (all 1.19.4, one hosted by Minehut, another running on Pufferpanel and a third on Pterodactyl), but occasionally when Slimefun attempts to cache skins for the custom heads, it runs into an issue where it can't find jphipps3's skin. This is the error:
This error probably happens because the user doesn't exist.
📑 Reproduction Steps
💡 Expected Behavior
No errors put in console.
📷 Screenshots / Videos
No response
📜 Server Log
No response
📂
/error-reports/
folderNone
💻 Server Software
Paper
🎮 Minecraft Version
1.19.x
⭐ Slimefun version
🧭 Other plugins
There's a chance it's one of the addons that are creating the issue, but it would say that addon's name instead of just Slimefun, right?
The text was updated successfully, but these errors were encountered: