Erikari a écritHi! what if I told you you don't need to do this tiresome procedure as of Spine 3.8?
I'd be very happy! And gladly upgrade my game to Spine 3.8 if so.
But first I need to check specifically what you mean when you say:
Erikari a écritSimply import the new json in the existing skeleton, and Spine will automatically add the new skin and populate the correct slots as long as the same nomenclature is used:
Import - Spine User Guide: Data
So what you're saying is that in Spine 3.8, using 'Import Data' into the existing skeleton means that if I have images in a file like this:
ExistingSkin/Head.png
ExistingSkin/Body.png
ExistingSkin/Weapon.png
And I add a new skin, then as long as I have named these images the same way but in their own folder:
BrandNewSkin/Head.png
BrandNewSkin/Body.png
BrandNewSkin/Weapon.png
Then wherever the original ExistingSkin/Head.png and so on are found in the existing skeleton, a new skin will place the BrandNewSkin/* variants in all the same slots/skin-placeholders... while also leaving all the ExistingSkin images positions/scales/hierarchy-positions all the same?
^ Because that's exactly what I'm after.