EDIT: TMC mentioned that support for skins.minecraft.net, the source for skins in versions above 1.3 to just below 1.7.9, has been discontinued. Also, I was planning on asking how to edit the skin manually in the .jar file, but I've managed to figure out a simplier solution with a texture pack. (You don't need the foundation in earlier versions; just one texture will do.) Thanks to TMC for initially informing me of the new situation.
Hello. I've been able to have different skins in versions prior to 1.7.9, albeit having to wait up to an hour. But shortly since downloading the Better than Wolves mod, they only show up as Steve. (Even in Vanilla; although they do show up in versions 1.7.9 and up.) It could be a fault with my Minecraft, but I saw the problem arise before I attempted to manually edit the skin myself, and I still have not figured out the problem, and it's really strange to me. I was using the old launcher at the time. And I don't want anything complicated. Thanks for the help, y'all.
You have to use a resource pack since they dropped support for skins.minecraft.net; this happened just the other day but I never noticed it (I play in 1.6.4) because I'd long since replaced the default skin with my own (actually, I replaced the skin, as well as a few other textures, inside the jar since I modded it for other reasons and never use/switch resource packs. Otherwise, if you use a custom resource pack you'll have to modify the skin inside of it).
The only issue is that all players and heads will use the default (your) skin but multiplayer isn't even properly supported anymore (the launcher fails to pass in a valid session ID so the game thinks you are not logged in; singleplayer works normally though. 3rd party launchers may work around this issue, but not the skins unless the game is modded to use UUIDs):
You have to use a resource pack since they dropped support for skins.minecraft.net; this happened just the other day but I never noticed it (I play in 1.6.4) because I'd long since replaced the default skin with my own (actually, I replaced the skin, as well as a few other textures, inside the jar since I modded it for other reasons and never use/switch resource packs. Otherwise, if you use a custom resource pack you'll have to modify the skin inside of it).
The only issue is that all players and heads will use the default (your) skin but multiplayer isn't even properly supported anymore (the launcher fails to pass in a valid session ID so the game thinks you are not logged in; singleplayer works normally though. 3rd party launchers may work around this issue, but not the skins unless the game is modded to use UUIDs):
Thanks for the heads-up anyway, man. I didn't realize they dropped skins.minecraft.net support until you've mentioned it, especially since it literally happened just this week.
And also, I was originally going to ask for help updating the skin manually as well, due to what I thought was a file attribute problem (but wasn't really the case, at least not with the texture pack; I was messing around with the BTW .jar file at the time), but I've managed to figure it out on my own, so this and the aforementioned problem are now solved. Again, thanks for the help.
Rollback Post to RevisionRollBack
I always seem to be better at writing than verbal communication...
Someone ought to make a mod to fix it. Too bad Forge and MCP dev environments don't work properly for these older versions and they won't even allow people to discuss modding older versions (making it hard for a fix to be found for that). But hacking support for the newer texture system into older version would be pretty cool.
Someone ought to make a mod to fix it. Too bad Forge and MCP dev environments don't work properly for these older versions and they won't even allow people to discuss modding older versions (making it hard for a fix to be found for that). But hacking support for the newer texture system into older version would be pretty cool.
MCP definitely works for 1.6.4, as I still make my own mods for it (for example, see the second link in my signature, which I see as my own version of the game). I haven't ever modded 1.5.2 or earlier but I do suspect that it may have issues since back then the .minecraft folder structure was completely different (e.g. old mod installation instructions refer to a "bin" folder; ModLoder also doesn't work from what I've heard, but you can use a 3rd party launcher that replicates the old environment). I also haven't heard anything about not being allowed to mod older versions, or talk about it, I've even seen people still modding Alpha and Beta versions.
That said, my own solution to this issue was to simply add my own skin to the jar as part of my own mod's assets (if you install TMCW you'll see my skin, I also provide a basic resource pack that shows how to change it. TMCW is singleplayer-only since that is all that I play so I don't care about multiplayer support, which is the only thing that is really broken. If you use a custom resource pack you'll need to merge them since only 1.7 and later can load multiple packs at once. The skin also must be 64x32) - I started doing this even before they shut down the skin server as insurance against server outages and never even noticed that it was shut down until I saw somebody else mention it (IMO, a bigger issue is the lack of support for custom name changes - if you tame an animal and change your name it will no longer obey you, and statistics will also be reset; when I changed my name several years ago I had to edit the save files to change the name in them).
EDIT: TMC mentioned that support for skins.minecraft.net, the source for skins in versions above 1.3 to just below 1.7.9, has been discontinued. Also, I was planning on asking how to edit the skin manually in the .jar file, but I've managed to figure out a simplier solution with a texture pack. (You don't need the foundation in earlier versions; just one texture will do.) Thanks to TMC for initially informing me of the new situation.
Hello. I've been able to have different skins in versions prior to 1.7.9, albeit having to wait up to an hour. But shortly since downloading the Better than Wolves mod, they only show up as Steve. (Even in Vanilla; although they do show up in versions 1.7.9 and up.) It could be a fault with my Minecraft, but I saw the problem arise before I attempted to manually edit the skin myself, and I still have not figured out the problem, and it's really strange to me. I was using the old launcher at the time. And I don't want anything complicated. Thanks for the help, y'all.
I always seem to be better at writing than verbal communication...
You have to use a resource pack since they dropped support for skins.minecraft.net; this happened just the other day but I never noticed it (I play in 1.6.4) because I'd long since replaced the default skin with my own (actually, I replaced the skin, as well as a few other textures, inside the jar since I modded it for other reasons and never use/switch resource packs. Otherwise, if you use a custom resource pack you'll have to modify the skin inside of it).
See: https://bugs.mojang.com/browse/WEB-985
The only issue is that all players and heads will use the default (your) skin but multiplayer isn't even properly supported anymore (the launcher fails to pass in a valid session ID so the game thinks you are not logged in; singleplayer works normally though. 3rd party launchers may work around this issue, but not the skins unless the game is modded to use UUIDs):
https://bugs.mojang.com/browse/MCL-7282
TheMasterCaver's First World - possibly the most caved-out world in Minecraft history - includes world download.
TheMasterCaver's World - my own version of Minecraft largely based on my views of how the game should have evolved since 1.6.4.
Why do I still play in 1.6.4?
Thanks for the heads-up anyway, man. I didn't realize they dropped skins.minecraft.net support until you've mentioned it, especially since it literally happened just this week.
And also, I was originally going to ask for help updating the skin manually as well, due to what I thought was a file attribute problem (but wasn't really the case, at least not with the texture pack; I was messing around with the BTW .jar file at the time), but I've managed to figure it out on my own, so this and the aforementioned problem are now solved. Again, thanks for the help.
I always seem to be better at writing than verbal communication...
Someone ought to make a mod to fix it. Too bad Forge and MCP dev environments don't work properly for these older versions and they won't even allow people to discuss modding older versions (making it hard for a fix to be found for that). But hacking support for the newer texture system into older version would be pretty cool.
MCP definitely works for 1.6.4, as I still make my own mods for it (for example, see the second link in my signature, which I see as my own version of the game). I haven't ever modded 1.5.2 or earlier but I do suspect that it may have issues since back then the .minecraft folder structure was completely different (e.g. old mod installation instructions refer to a "bin" folder; ModLoder also doesn't work from what I've heard, but you can use a 3rd party launcher that replicates the old environment). I also haven't heard anything about not being allowed to mod older versions, or talk about it, I've even seen people still modding Alpha and Beta versions.
That said, my own solution to this issue was to simply add my own skin to the jar as part of my own mod's assets (if you install TMCW you'll see my skin, I also provide a basic resource pack that shows how to change it. TMCW is singleplayer-only since that is all that I play so I don't care about multiplayer support, which is the only thing that is really broken. If you use a custom resource pack you'll need to merge them since only 1.7 and later can load multiple packs at once. The skin also must be 64x32) - I started doing this even before they shut down the skin server as insurance against server outages and never even noticed that it was shut down until I saw somebody else mention it (IMO, a bigger issue is the lack of support for custom name changes - if you tame an animal and change your name it will no longer obey you, and statistics will also be reset; when I changed my name several years ago I had to edit the save files to change the name in them).
TheMasterCaver's First World - possibly the most caved-out world in Minecraft history - includes world download.
TheMasterCaver's World - my own version of Minecraft largely based on my views of how the game should have evolved since 1.6.4.
Why do I still play in 1.6.4?