Hello,

We're having a little hassle with implementing new content. It does work ok and as intended i assume, but right now it almost takes longer to implement stuff in the spine project than to actually make the content.

We have 1 spine file, with ₅₀ skins. Each skin has various parts that are changeable (hats, shoes etc) - all under a skin placeholder. If i want to add a new pair of shoes, i duplicate the latest one, and then change its image path. Problem is that i have to change this image path 100 times for just a pair of shoes. This is also a forever growing spine file, so its only gonna get worse.

Just wondering if there's a clever way of doing this? If not i could always create alot of temp placeholders for the future (as i did earlier in the project) and just update existing images - but that's still a daunting task at this point.

Cheers!

Pharan a écrit

If it's complicated do use Spine's Find and Replace tools for the job, it might be easier if you export your skeleton as a JSON and then manipulate that with some code (or pre-existing program) that can juggle JSON, or even plain text if it came down to it.

Then you can reimport the manipulated JSON as needed.

Also, to clarify:
What are in those 50 skins? Are they 50 actual unique sets of swapped images?
Or are you making skins that are just different combinations of a few sets of image parts? Is that why for one new pair of shoes, you have to change a hundred skins?

If you're doing this, you might be better off building a mix-and-match system at runtime, which is pretty simple to do as long as you leave the attachment/alignment data in the skeleton.

Yeah not familiar with the Find and Replace tools, maybe i should get into that either way. Thanks for the input! Will look into manipulating the JSON.

The 50 skins are a mix of completely different characters and alternate versions of those characters, so yes, unique sets of swapped images. The accessories/items are in skin placeholders as well because their rotation, scale and position varies from skin to skin. We tried with an earlier game to have a spine rig per character, and it works - but with an immense load time as a result (mobile). Might not have been the best implementation from our side anyways though. But it works well in this game, and 1 spine file for everything does wonders to load times.