Hello, I'm very new to Spine, and for my project I started with something simple, a portal animation that uses skins since the portals will have different shapes and colors. However I've been banging my head against a wall for some hours since I can't find the correct tagging and/or hierarchy in Photoshop so the script translates the skins correctly. I've searched for older posts describing the same issue trying to find a solution, like this one: http://en.esotericsoftware.com/forum/Photoshop-to-Spine-to-Skin-Folder-13087 but the fix in this post seems not to work or I'm missing something important.
I'm working with two skins for now, 'Blue Portal' and 'Orange Portal', each one has three distinc parts, and two of them are slots containing different variations that I'll swap during the animation (different types of spiral effects swirling around, etc.), so my hierarchy in Photoshop, from what I learned watching skin videos, looks like this:
However, when I export it to a JSON file using the latest script, the hierarchy in Spine looks like this:
I'm trying to get something similar to the old Spine example 'goblins', where I would have just three slots, each one with a skin attachment that swaps its image according to the skin selected. Instead, I got duplicated slots for every skin, and for some reason, as it shows in the screenshot, the second skin, Orange Portal, has no image attached to its skin folder, only the other one has its corresponding image.
I can fix this issue manually, deleting the repeated slots and manually dragging the images for the second skin, then it works when I swap between the skins, but there must be a way to do it automatically from Photoshop but I just don't know how. I'd appreciate any help or an example of how a correct tagging in Photoshop would look. Thank you in advance.
So I found an older version of the script, closer to the ones showed in the skins tutorial videos where it worked as intended (I tested the 3.9 ver) and it turns out it fixed the issue completely: the skins hierarchy were exported to Spine as intended, no repeated slots, no empty attachments. So I'm guessing there's a bug with the latest script. I already contacted support to see if there's a way to fix it, but I thought I'd post a follow up here too.
