Minecraft Forums

thought this was a little interesting but for some reason the 1.3.1 client doesn't want to accept custom skins. minecraft.net will upload the skin fine and will give you confirmation (once traffic eases up) but 1.3.1 wont download/update the skin or load it in-game. i reverted to the w27 snapshot (my fav) and my skin showed up fine. the second i updated to 1.3.1 again, skin reverted to default.

mainly i'd like to know if there is a manual way that i can use my custom skin before this bug gets fixed (modifying jar files is not my strong suit) because i would like to start my new LP

My skin is the default steve skin and ive kept trying to change it back to my skin but it wont working, it was working fine a couple hours ago but it just gave out and wont work

Same thing happens to me, My skin is fine when I play 1.2.5, but when I go to 1.3.1 it reverts to stupid steve.

Same here but with a twist. I can play 1.3.1 fine in single player. Though when my users and myself log onto my server we are all wearing the default skin. I'm curious to know if you guys have checked it on single player and multiplayer? Im sure there will be a fix for it soon enough.

I sometimes got this in late 1.2.5 (say, a little before 1.3.1 came out). It seems that the client needs a while to be able to load up the skins from the main server that handles that. If you notice that someone has their skin working, reset by relogging or killing yourself, and your skin should work. However, the time it takes for you to be able to load skins can take several minutes.

this was in single player without lan. in the span of 5 minutes (after i uploaded my skin) reinstalled 12w27a snapshot, loged in and my skin was ok, restarted minecraft and checked force update and logged in and my skin was steve. haven't tried multiplayer

note: this is on an account i just bought earlier today (needed a new name for my let's play) im thinking now that my account maybe wasn't validated for all the extra features when i tried earlier. still having the issue

I'm suddenly having the same issue. It's been fine before. I tried uploading a new skin, to see if that would fix it, but it didn't. Anything else I can do? Kind of frustrating, because I don't like looking like caveman Steve! Hehe

Temporary fix for you singleplayer dudes: mod your jar so that steve is your skin. Only problem is that multiplayer will have everyone look like you.

I think I know why. Its because 1.3.1 has a new skin server unlike 1.2.5

and this new skin server isnt very stable at the moment.

my skin will not work if i have any mods installed. i guess that means its a problem with minecraft itself.

edit: nevermind, its not working regarldless of mods now

I got the same problem...

Yeah it's annoying to see a bunch of people in the MineZ hallway all wearing Steve, including me :/

i got mine working this morning but when i went to record my first episode i realized halfway through that it was steve again. doing some off-camera work right now and my skin is all good

Yep noticed this as well, on my screen I was my custom skin. However on my friends screen in LAN play I was the default Steve.

This might have something to do with the new 1.3.1 launcher. I had recently switched from an old launcher to the new launcher to see if I could check out the Demo mode that people seem to be having trouble with. But maybe because I actually purchased the game long ago (1.7.3 beta) I could not find any Demo mode anywhere.

But this noon when checking out SMP 1.3.1 DEV world combined with other worlds on main server (multiverse), I saw a Steve and then noticed that I was also Steve, although, others could see my other skin. Log off/log on, or totally restarting minecraft did not resolve that. I was still Steve (to me) this evening. Then I noticed errors like this for my own skin and skins of other players:

java.io.IOException: Server returned HTTP response code: 503 for URL: http://skins.minecraft.net/MinecraftSkins/efflandt.png

even though the URL works fine in my browser.

So I switched back to my old launcher (from 1.8 beta), and could then see my skin. File size comparison (Linux):

-rw-rw-r-- 1 efflandt efflandt 81938 Aug 6 19:46 minecraft-131.jar
-rw-r--r-- 1 efflandt efflandt 89406 Nov 2 2011 minecraft-18.jar
-rw-r--r-- 1 efflandt efflandt 89406 Nov 13 2011 minecraft.jar

So maybe problems that people are having with missing skins or changes to skins that do not show up in game is that the 1.3.1 launcher and/or something in the game is either not making a proper HTTP request to get skins, or not waiting long enough for a reply when server is busy.

PS: It apparently was not the launcher version. I just started a new 1.3.1 SSP world and I ended up as Steve. The console showed 503 errors (temporarily unavailable) trying to get my skin. So apparently maybe the skin server simply cannot keep up with demand when things are busy, and minecraft does not retry to get the skin.

this might be an issue with the internal server integration since skins/clients load up different in mp than they would in sp, now since the integration they both might work the same. i may just be crazy, but those are my thoughts

Heres my story: I randomly changed to steve, then i tried to change my skin to a new one, went back to my old skin. dafuq.

Same mine wont friken change

Same problem. I thought it was optifine being stupid again, but I tried it without it, still doesnt work. DAMMIT MOJANG, WHAT DID YOU DO NOW?!

EDIT: I think maybe on the release date of 1.3.1, everyone was like, "OMGWTFFINALLY1.3.1ISOUTYAY" and everyone logged on at once, which overloaded the servers at mojang. That, or some moron tripped on a cable.