Closed learliet closed 3 months ago
In the texture map of a variant in rig.variants, variants correctly associate textures by their UUIDs:
rig.variants
"c3fa5074-1ee5-5c3b-a641-d575dcc648ff": { "name": "new_variant", "display_name": "New Variant", "uuid": "c3fa5074-1ee5-5c3b-a641-d575dcc648ff", "texture_map": { "cc51833f-1a47-e0ed-2f36-e11575ea7db0": "8d9af0cb-3ce2-2247-d3eb-a45ecb7b108c" }, "excluded_nodes": [] }
However, in resources.textures, textures are mapped by integers rather than UUIDs, and lack a uuid field.
resources.textures
"resources": { "textures": { "1": { "name": "texture2.png", "expectedPath": "assets\\animated_java\\textures\\item\\blueprint\\texture2.png", "src": "bla" } } },
Technically this is extra data, as the models for variants are already generated in variant_models.
variant_models
You just need to swap out a variant's models when the variant is applied.
In the texture map of a variant in
rig.variants
, variants correctly associate textures by their UUIDs:However, in
resources.textures
, textures are mapped by integers rather than UUIDs, and lack a uuid field.