Hello! That's kinda baffling to read. I'd like to ask you to open a ticket with me, where I can explain exactly what those bones are for. I would also like to know what you had to redo, or why you say the product is not "optimized", since all of their "display" bones are used in all animations. The average skeleton has 13 bones, two for each limb (arm-elbow, leg-shin, hip-chest, head-jaw) and the weapon. This could be considered pretty standard optimized for the market. Maybe you have noticed there are various "bone" folders, but only the bones with cubes (inside blockbench) create display entities, thus "affecting performance". If they have 13 "real" bones in average, the rest are just "Ghost bones" (Even if blockbench says "47 bones"), which mean they don't impact performance, since they don't spawn display entitities at all, and instead, they are used for many internal functionalities in the scripting. If you removed the death_markers, for example, which apparently are "unused bones", you basically risk breaking the death animations completely. (Take a look at death animation, and you'll notice it looks wrong inside the model, and instead, can only be displayed in-game, through the MythicMobs mechanics, and the information is given by these death_marker bone locations) In fact, this is an animation system I like to use, since it allows correct and seamless separation of animations/states for dynamism, and in other cases, allows to use procedural animations without affecting the base blockbench animations. Some other bones are markers for particles, which are necessary for @Modelpart targeters. Some other bones are used for specific animations, like hurt/hit animations, and while some of the "control" bones might be unused in some animations, i standardize them along all packs to make features also standardizable. Still, as I say, those do NOT affect performance, network load, or entity amount. Once again, I'd beg you to open a ticket if you have doubts on any of this, and maybe tackle any other issue you might have related to these issues, or any other pack related issue, before leaving this review! It truly hurts to have a 2-star review on a pack that i've tested many times to make sure it works out of the box :c. I could have explained this and helped you with any modifications you needed by just opening a ticket.