Ever since Minecraft 1.3.1 and Minecraft 1.3.2 came out, I've been having a skin bug. This skin bug is where it doesn't load your skin that you uploaded to Minecraft .net, and instead you have a steve skin. This glitch is in both Multiplayer and Singleplayer. In Multiplayer, the glitch is where you can't see others skins and instead they're steve, and your own skin is steve. If there is any news of Mojang fixing this in the next patch or any way to solve this issue, please tell me. Thank you
When I have had this issue, I noticed in the terminal that java got an HTTP 503 error (temporarily unavailable) when trying to download my skin (or sometimes for other players when in SMP). So it appears to be a problem when skin servers get too busy as the game gets more popular. The only real fix they could do for the client would be to have it attempt to get failed skins again after a time. Not sure if it already does that or needs a long time delay, because occasionally I see that repeatedly failing.
The skin server is ... needing an upgrade. It's not a version specific issue, no patch will help. I'm sure they'll get it sorted out.
Well, it is a version specific issue in that 1.3 switched to a new skin server pool. The new skin server pool is an Amazon server pool... not sure about the old one. The old one appears to work fine, but the new one hasn't worked right yet. It's flaky, works one run, then fails the next, and can serve up out of date skins as well.
Well, it is a version specific issue in that 1.3 switched to a new skin server pool. The new skin server pool is an Amazon server pool... not sure about the old one. The old one appears to work fine, but the new one hasn't worked right yet. It's flaky, works one run, then fails the next, and can serve up out of date skins as well.
Ahh. So Amazon needs to fix their **** then! I think they should implement an option to tweak the server in which you get skins. Like say you play on two servers. One is not normal run of the mill server.. cool your normal skin would work fine (mine is Hannibal Lecther) . But the other is an RP based server where Dr. Lechter would not fit, so you upload a skin to their server and when you log in, you get that skin instead. Kind of like what's going on with the texture packs. Furthermore, you should be able to put a skin file in a local folder (like the way we do with texture packs) for SSP.
This would take a HUGE load of of the current skin servers...
Ahh. So Amazon needs to fix their **** then! I think they should implement an option to tweak the server in which you get skins. Like say you play on two servers. One is not normal run of the mill server.. cool your normal skin would work fine (mine is Hannibal Lecther) . But the other is an RP based server where Dr. Lechter would not fit, so you upload a skin to their server and when you log in, you get that skin instead. Kind of like what's going on with the texture packs. Furthermore, you should be able to put a skin file in a local folder (like the way we do with texture packs) for SSP.
This would take a HUGE load of of the current skin servers...
Skin won't work on me too... 1.3.2 version minecraft, but when i'm back-up to 1.2.5 - skin works fine. Lol what the hell? login in-out or re-upload skin on site = NOT help. I have always steve now -.-
i have this problem as well, but i highly doubt its a version specific issue. however, i logged in today and noticed that the Steve hadnt decided to annoy me today and i got my regular skin back.
It's version specific because before 1.3 skins were downloaded from s3.amazonaws.com and in 1.3.x they are downloaded from skins.minecraft.net Since these are NOT the same servers, the fact that skins.minecraft.net is flaky has no impact on 1.2.5 or earlier MC.
It's version specific because before 1.3 skins were downloaded from s3.amazonaws.com and in 1.3.x they are downloaded from skins.minecraft.net Since these are NOT the same servers, the fact that skins.minecraft.net is flaky has no impact on 1.2.5 or earlier MC.
ah. still, its not quite fair to be blaming it on 1.3, as the skin servers are not part of the in-game changes.
Pics of the glitch are below:
by c0yote
I tried it with terrible results. I gave my wife my glasses for a second, a creeper showed up and now my wife is pregnant.
Stupid 3D..
Well, it is a version specific issue in that 1.3 switched to a new skin server pool. The new skin server pool is an Amazon server pool... not sure about the old one. The old one appears to work fine, but the new one hasn't worked right yet. It's flaky, works one run, then fails the next, and can serve up out of date skins as well.
This would take a HUGE load of of the current skin servers...
I was wandering about this glitch myself and used MS Network Monitor to see where the request is going. It turns out the skins will now be located at http://skins.minecraft.net/MinecraftSkins/ instead of http://s3.amazonaws.com/MinecraftSkins/. Mojang probably hasn't migrated the skins yet.
50.17.228.159 skins.minecraft.net
If that doesn't work then ping s3.amazonaws.com and use that ip address instead.
^^^
It's version specific because before 1.3 skins were downloaded from s3.amazonaws.com and in 1.3.x they are downloaded from skins.minecraft.net Since these are NOT the same servers, the fact that skins.minecraft.net is flaky has no impact on 1.2.5 or earlier MC.
ah. still, its not quite fair to be blaming it on 1.3, as the skin servers are not part of the in-game changes.
It is a code change when you change
to
oh.
*knows nothing about code in the first place*