Harald wroteIf you want to provide a full-fledged wardrobe system, I would suggest an additive setup where equippable items are combined to a final skin programmatically as described here:
Animation w/ asset change cause asset to vanish on skinchang
And also here:
Unityでの3.7から追加されたスキンの組み合わせ機能について
The setup would then be something like this:
base-skin= "caucasian character in underwear", "african character in underwear", ...
item-skin-earrings="normal earrings", "no earrings", "fancy diamond earrings"
Then the user could remove those earrings by changing the earrings skin from "normal earrings" to "no earrings".
After every item-change, the skin layers are re-combined like layers, as shown in the code in the postings.
I hope that this was not too confusing, please let me know if this makes sense to you.
So I think base-skin and item-skin-earrings are two lists? If I've got that correct, I understand you. In my code, I would have to build those lists myself, right? That's effectively creating my own slot system in my unity code and I was hoping to avoid this, but it's not the end of the world.
Here's what I'm trying to build:
It'd be really convenient if that whole picture could be generated from Spine data. I could iterate all the skins of that character, and for each skin, I use the skin name on the left and put a button on the right. That I know I could do. But how do I tell if the button should be enabled or disabled? For that, I wish I could check the skeleton and ask, "What skins are active?" It'll say one of those items, so I'll know to disable it. But, I don't know if that's possible.
I've noticed if I say: SetSkin(earrings); SetSkin(no earrings); the last one wins. This would be like the user clicking on the "earrings" button, then clicking on the "no earrings" button. If, after the user does this, I could ask the skeleton which skins are active, if it would return "no earrings," Spine would be doing all the work for me. The only logic I'd need to write is, "Which skins are active? Disable buttons with those skin names." Then, the user could click on any button, and the buttons would enable/disable correctly.
But, I gather that I don't have access to, "What skins are active?" This means I have to make my own concept of slots in my Unity code (e.g., the list of earrings). That's kind of a shame. Spine knows that I can't wear "earrings" and "no earrings" at the same time, but it sounds like I need to duplicate that logic in my code, too?
