-
Notifications
You must be signed in to change notification settings - Fork 61
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
Skin won't update/Force update skin (continued) #80
Comments
Interesting. I'm seeing this too, maybe the new skin api has a rate limit? |
Turns our img-1 wasn't receiving any requests due to internal networking not working. I've fallen back to public IP's and I'm seeing images resolve now. I'm going to try and clear the invalid cache so we can get these images working again. |
Great! Also, does this mean that the 3D part of the skin (I am not sure if I named it correctly, I mean the right hand side of the skin image) will display now? |
Skin API does have a rate limit of 1 request per 2 seconds. |
@MisterFixx That's not what I'm seeing, have any sources? |
Check where it shows the online users on the right hand side of http://explosivenetworks.net/, barely anybody has a skin there (at the time of this post) but they certainly do have a skin in-game. :) |
@clone1018 I should have explained myself better, the skin API (textures.minecraft.net) does not have a rate limit, but the session server that is used to get the texture url has a rate limit basiccly what it means that if you try sending more then 1 requesr per 1.5 seconds you'll get a 429. |
@MisterFixx So what I'm seeing is our servers hitting skins.minecraft.net about 30 times a second each. I'm not seeing any rate limiting or any responses besides 404 and 200. |
@MisterFixx Can you join me in http://webchat.esper.net/?nick=&channels=axxim |
Seemingly have finally crushed the performance related bugs and this I am confident is now solved. Enjin have since switched provider anyway... |
My head does not display my skin (Username: "Heartburst_") on the Enjin website. Since the last issue (79) was closed, a few heads of others in the community that were working properly are now back to Steves.
The text was updated successfully, but these errors were encountered: