However, it seemed as if right as all this came up, they announced UUIDs. When I manually uploaded a cheap mspaint job of a 64x32 template, I found that it worked again: Doing a similar tweak to MCImager, I was able to cache capes (only that this script wouldn't check the official source for newer versions). With that in mind, I had a farfetched idea that I could do the same with capes Sure enough, I found that clients would also query /MinecraftCloaks.

I handed out a simple batch script to a few dozen friends that would handle editing the hosts file for them, and soon enough, I had tens of thousands of skins cached, taking up no more than a fraction of a gigabyte. Upon realization that clients just fetch skins from, I set up a web server that acted just like the amazonaws server and edited my hosts file to redirect to, and it worked beautifully.Īll the skins I came across appeared to me as whatever I wanted them to be because my client looked them up in my cache - If they were there, it'd use the cached file - If they weren't, it'd download it from the official source. To accomplish this, I used MCImager resource, then tweaked it to my liking. As a former server owner (before 1.7 I believe), I wanted to create a skin cache for a more consistent default avatar selection on my fora (Minotar just didn't cut it for me).

Minecraft cape buy