violet

Given people have to know what texture ID to fetch anyway, it's not unreasonable to expect them to know whether or not a skin needs to have a slim model....

I mean, there's always the option of having a fallback API such as Electroid's [mojang-api](https://github.com/Electroid/mojang-api) for if requests to Mojang's API bounce. You'd probably want to talk to the host...

Oh, yeah that makes total sense, I don't know why I didn't realize that would be an issue. Oh well...

Idk if there's a way to tell Cloudflare to query from a different datacenter, but if there is that might be a way of mitigating this. I don't know how...

Hm, interestingly I see a very similar issue with my [own cape](https://crafthead.net/cape/tibinonest). It has displayed the blank image despite that a) I have a cape enabled on my skin, b)...

I think once I PR everything I have planned I might see if I can get more extensive documentation going, we'll see tho.

Hmm, given we have to fetch the texture URL for a request anyway, we could add an `X-Crafthead-Texture-ID` to every request, it'd be nice to hear what @astei thinks of...

There's also the question of whether avatars, helms, busts, etc should return the `X-Crafthead-Skin-Model` header or only the skin endpoint. My thinking when adding that header in is that since...

> I think you should only have the header if the render is effected by the model. That would mean only body and bust renders. Do you think skin requests...

Currently, the branch renders the overlay textures directly on top of the cube, meaning it looks like one contiguous texture. While this is good for 2D renders, it may be...