このサイトを正しく表示するには、最新のブラウザを使用し、Javascriptを有効化してください。

Seeking way to do automatic validation and correction.

Nick

My game require every characters to have some kind of general setup involving special bones, point attachments and slots.

For example, every character needs to have a set of special bones such as look-at, shadow, head, center, dialog-at, etc. so that I can find and use them during the game. However, I find it quite often that some of them are missing or just misspelled.
I could already auto detect those issues from Unity which would gives me a list of warning to remind me to fix them but it still require me to manually adding those missing pieces back to the project and adjusting them. Thus I am seeking ways to automate part of the process. Particularly I would like to be able to inject those missing bones to the project so that all I left to do is to just open the spine project and correct their positions.

Since the .spine file is encoded and I could not edit it directly, one way I could think of is to do a full export of the project and fix the issues in the json format and re-import the whole project back into .spine form. I didn't try this yet because it could take quite some time and I doubt some data or settings may get lost permanently during the export process and could not be restored by re-import. Thus I want to ask spine team for opinion first if this is feasible to do so?

Nate

The .spine file is binary for efficiency, small file size, and version compatibility, so it's not really feasible to edit.

It is perfectly reasonable to export to JSON, make modifications, and import back into Spine to get a .spine file again. It is true you will loose some minor information, but if Nonessential data is checked when exporting to JSON, you won't lose anything that will break your project when reimported. We have a list somewhere, but I think it's bone icons that will be lost and maybe a few other minor things. We can get those fixed in 4.1.

Processing the JSON file can be relatively easy or somewhat difficult, mostly depending on what tools you use to parse/modify it. Our JsonRollback tool does that to convert JSON to older versions. It uses Java and libgdx and the code looks like this:
https://github.com/EsotericSoftware/spine-runtimes/blob/3.8/spine-libgdx/spine-skeletonviewer/src/com/esotericsoftware/spine/JsonRollback.java
You could base your processing tool on this, or you may find it more productive to use whatever development tools you are most familiar with.

Note you can turn your JSON file into a Spine file using Spine's CLI with `

import(or-r`). Eg:

spine -i /path/to/modified.json -o /path/to/project.spine 

---

import

-r is the same as `

import. You can also do multiple with one Spine execution, eg: [code] spine -i /path/to/modified1.json -o /path/to/project1.spine -r -i /path/to/modified2.json -o /path/to/project2.spine -r [/code] After the

importor-r` parameter, you can specify a name for the skeleton, eg:

spine -i /path/to/modified.json -o /path/to/project.spine -r monster

You could also use the CLI to export to JSON, run your tool, then use the CLI again to turn the JSON back into a .spine file.

Nick

Sounds good!

Nate wrote
Note you can turn your JSON file into a Spine file using Spine's CLI with

import (or -r).

One thing that catch my attention is that the

import CLI seems actually generating a completely new .spine file out of the json. It is a little different than I expect. I thought it could additionally open an existing (the original) .spine file make use of the un-exported information to have a more complete project recovery. e.g. the missing bone icons settings, export settings, selection set settings, etc.

Anyway, thank you for the quick response.

Nate

You can import data or a project into an existing project (if the .spine file already exists), but it'll come in as a new skeleton. It won't try to merge with the existing skeletons, which be a little complex.