Hello there!
Thank you for taking the time to read my post, I am fairly new to Spine, and am currently facing a rather interesting problem.
I am struggling to understand what the best, or rather, correct way of using Spine for my current situation is. Let me try to explain my situation briefly:
Our game has some 10k character NFT's, each one Unique of course, with some dozen different body types, each body type having hundreds of different designs. Every one of these sprites has 3 images, down facing, up facing, and left facing.
Our spine artist currently has created a spine skeleton with skins for 3 of these characters, and it is working very well in Unity. However, I am concerned with the number of skins we have, it seems that having all possible skins in a Spine file, and then swapping it in engine is a huge overhead.
Theoretically, a single player will most likely only have a couple of these NFT's, and he should not care about the look of the others, but he will still have this data in his client application.
What I am trying to achieve is the following:
Since all our NFT's use the exact same skeleton, I want to create an Atlas for each NFT, and then when a user connects their wallet, I would grab the respective atlas, and apply it to the Skeleton. I would want to do this for each NFT he owns, so the same Skeleton is used but the Atlas is created on our backend.
I have tried to create an Atlas myself, by duplicating the already exsting atlas and changing a few things, I have encountered a few minor problems with that approach so I've decided to write to you for help.
Hopefully I was able to explain my problem coherently, once again thank you for your time and support.