We have the following architecture setup to load different skins at runtime:
- A single base spine atlas/json/png that contains the basic avatar body
- Many atlas/json with empty png files worked as template that we can replace those empty pngs with different skins to change the outfit.
This works fine.
However, it doesn't work well when we want to add new animations.
For example, we have a new animation called "Eat" that will show the avatar eating a burger, and the burger will will only when the "Eat" animation is active.
If we play this animation with the new atlas/json data, we can play the "Eat" animation with burger just fine.
But if we just play the "Eat" animation with the original base atlas/json, it won't show the animation nor the images.
We want to keep the base spine as clean as possible, so that it will contains the basic avatar body and nothing else. All new outfits should be added by skin atlas/json/png, and new animations should be added by the similar architecture.
Any thoughts?
Thanks
