Could also be used to hide/show the cape as detailed in issue #5

Limb's aren't correctly rotated, might wanna look into the rotation values set in the getFIgure() method.

Should save render time & resources for rendering a large number of polygons (for instance, when you subdivide faces multiple times).

Back-face culling: Doesn't render a face whenever it isn't visible to the camera.

The newer "Alex" model skins with slim arms only have 3-wide arms. Add support for them!

This can be done using the same API as is already used to retrieve skin files, Crafatar.

Title explains it all. It can be actual lighting or ambient occlusion, doesn't matter.

When rendering players alex style arms, the N, S, E, & W texture faces are offset by one pixel each horizontally.

Instead of returning null, check for the player's skin type (STEVE or ALEX, see issue #8) and assign either a steve or alex skin based on the result. Default to steve skin if unable to determine.

Exactly as it sounds like. When displaying only the base or overlay layers, they display properly. See attached screenshots.

Possible cause - sortPolygons() method is comparing pixels from the base layer to pixels on the overlay, resulting in SOME base pixels SOMETIMES being drawn over the overlay when they shouldn't be.

Happens as a result of ObjectGroups not sorting correctly, look into how global positioning (of Groupables assigned to ObjectGroups) is calculated and fix.

Could use mojang API, see UUID -> Profile + Skin/Cape (wiki.vg) (includes whether or not a player's skin is slim).

Might also be useful to pull the skin from there instead of crafatar (as we do right now), although it would limit player info retrieval to once per player per minute.