Sekomu Indeed, I was able to reproduce the problem with the Spine project you sent me. I am sorry that the order in the JSON file did not seem to be a problem! I'll create an issue ticket to fix this.

Sekomu I have not created an issue ticket, but wanted to let you know that Nate is already working on this issue. I will let you know when the fix is complete!

Sekomu Sorry for the wait on this issue. In the recent release of Spine 4.2.34, the parameter --export-all is now available, which allows you to export all skeletons, whether you want to export them in JSON or binary format. (Please ignore that I previously told you that this can be set in the export settings JSON file, just add this parameter.)

Spinebot
I'm not seeing a --skeleton command line option

stupot Your point is correct, sorry I missed Spinebot's incorrect response! The command line option --skeleton does not exist, edited Spinebot's answer.

Misaki that option would still be good though, thats how I ended up here, looking for a way to target specific skeletons for export easily. Specifying a skeleton to override default behaviour would be great, specifying a list of skeletons even better (or multiple --skeleton). Whats mentioned in the above solution, to export and edit etc, although appreciated, is more of an impractical workaround than a realistic solution.

stupot Hmm, when I read your suggestion, I thought for a moment that we might consider adding a way to specify the export target skeleton via the CLI, but I can't think of many cases where that would be very useful. In Spine, whether exporting via the CLI or not, you cannot specify the target skeleton when exporting skeletons in JSON or binary format unless you uncheck the skeleton you want to exclude from the export. In many cases, exporting skeleton data is very fast, even if there are many skeletons in a single project, so re-exporting even unrelated skeletons should not be a big problem.

When exporting animations in image or video format, you can specify the target skeleton in the export configuration JSON file. I wonder if what you are referring to is the hassle of editing the export settings JSON file to export a specific skeleton when exporting in image or video format.
I would appreciate more details about your current workflow, preferably in a new thread.

Misaki Hi, it would be very handy for me if a single skeleton could be exported from a spine containing many skeletons, without any editing or unchecking exports.

In my use case, a spine could have many skeletons, each exporting with multiple variants, which then triggers creation of multiple image formats. So that generates a lot of image files (some quite big) and avif's aren't quick to generate. So for just one small source edit, this would generate a lengthy asset creation which would also hammer the source control for a lot of files that haven't really changed.