Buongiorno Max! Se hai più root in un progetto Spine e desideri esportare un unico file JSON, dovresti assicurarti che tutte le animazioni e i dati siano consolidati sotto un singolo scheletro. Spine è progettato per gestire un singolo scheletro per file JSON, quindi se hai più root, potrebbe essere necessario riorganizzare il tuo progetto per avere un solo scheletro principale. Puoi anche utilizzare il comando di esportazione per specificare un singolo scheletro da esportare, assicurandoti che tutte le animazioni e i dati siano correttamente associati a quel scheletro.

MAx In Spine, there is a principle that each skeleton is exported as a single skeleton data file (either a JSON file or a binary file). To consolidate multiple skeletons into one file, you must manually move all elements from each individual skeleton into a single one and then merge them. However, merging skeletons comes with several limitations, making the process quite challenging. For example, while bones and slots can be moved, constraints cannot be transferred between skeletons. Additionally, when using skins, only the attachments from the currently active skin can be moved, which further complicates the process.

It would be helpful if you could explain the reason why you want to consolidate all skeletons into a single JSON file. If you let us know what you're trying to achieve at runtime, we can offer more specific advice.
If you need to share any images or files that cannot be posted publicly due to confidentiality, please feel free to send them to this email address: contact@esotericsoftware.com
Please include the URL of this forum thread in the email so we know the context.

Misaki's response is great. I would add that unless you need a human to read your skeleton data, you should be using the binary skeleton data format. It is smaller and faster to load.