• Editor

  • Combining multiple jsons/skeletons into 1 json file

    영어

Hey guys, is there a way to combine multiple json files or skeletons and be exported into 1 json file? For example, I have a few background animation skeletons animated in their own seperated spine file, and now i'd like to combine them into 1 spine file and eventually export as 1 single json file.

Thank you so much 🙂

Related Discussions
...

@bounce2, each skeleton is always exported to its own file. Why do you want to combine them?

@foriero, no, your proposed feature does not involve combining skeletons into a single file.

This is unrelated to the original question to export multiple skeletons as one single json file.
Which by the way is something you can do by:

  1. importing the various skeletons into a single project.
  2. moving the bones of the various skeletons into a single skeleton by drag and drop from one skeleton to the other.
  3. redoing the constraints that might have been lost in the process
  4. reimporting the animations for said skeletons into the now unique skeleton
    You have to make sure the names of the bones, slots, and images are different among the various skeletons to avoid problems when importing the new bones in the chosen skeleton, and depending on the quantity of constraints, or bones, or animations, this could potentially be a long process, which is why just using multiple jsons might be better.

@foriero, you have a thread about your proposal, it's not necessary to derail other threads. I have moved your last post to that thread.

foriero wrote

Hi, solution for this problem is not yet implemented. It is called Linked Skeleton... Read more here.

Spine Editor what's next after 3.7!!!

Ahh thanks for the link foriero.

Erikari wrote

This is unrelated to the original question to export multiple skeletons as one single json file.
Which by the way is something you can do by:

  1. importing the various skeletons into a single project.
  2. moving the bones of the various skeletons into a single skeleton by drag and drop from one skeleton to the other.
  3. redoing the constraints that might have been lost in the process
  4. reimporting the animations for said skeletons into the now unique skeleton
    You have to make sure the names of the bones, slots, and images are different among the various skeletons to avoid problems when importing the new bones in the chosen skeleton, and depending on the quantity of constraints, or bones, or animations, this could potentially be a long process, which is why just using multiple jsons might be better.

Hey Eikari, thank you for the clear explaination! Previously tried it on an older version and it keep crashing when i dragged and dropped skeletons. But will try it again on latest version. Btw it was a great learning lesson when i saw your gif on the 3d cube rig using edge vertex. Thank you so much!

Nate wrote

@[삭제됨], each skeleton is always exported to its own file. Why do you want to combine them?

@Nate, sometimes towards the end of production stage, we may get instructions to try combining them into one. Lol.

Thanks alot guys.