Hi, I'm evaluating Spine and have a basic setup question. Our game has several customizable characters as well as customizable equipment that can be shared among all the characters.
The Mix and Match example and the Goblins example both give me the impression that it is reasonable to have a single Spine project for multiple characters (full skins) that share the same skeleton and animations. Those examples have 2 "characters" each (male and female, boy and girl). Does this setup scale to around 50 characters? Or would that be too many skins and attachments to reasonably manage? It seems that the tools do a good job allowing you to hide everything that's not in the current skin.
If the answer is "no, you should put each character in its own Spine project", then can those separate skeletons still share animations in the runtime and will it be easy to keep them in-sync if we decide to add a bone or slot to all of them at once?
Or, is there a way to have a single "master" project with the skeletons and animations, and then separate "character" projects that just define new skins/attachments. And in the runtime the two are merged?
Any recommendations? The simplest solution seems to be to just have one project like in the examples, but I'm new to this.
Thanks!
