Re-exports

danialcaraz

Hello. Every time we update spine and unity runtimes to a newer version we need to manually re-export all skeletons manually. And we have hundreds of them. Is there any way to automatise that process? Or
could the newer runtimes and spine versions automatically read old version skeletons and update them? Thanks for your help

Spinebot

To automate the re-exporting of skeletons when updating Spine and Unity runtimes, you can use the Spine command line interface. This allows you to batch-export all your skeletons, saving you from manually re-exporting each one. Unfortunately, newer runtimes cannot automatically read and update skeletons from older versions due to compatibility constraints. The recommended approach is to set up a script that uses the command line interface to handle exports as part of your build process. This ensures that your skeleton data is always up-to-date with the latest project files. You can find more information and example scripts in the Spine User Guide: Command line and Blog: New export shell scripts.

Nate

Spinebot's info and links are good. The runtimes benefit in a few ways by targeting only a specific version of Spine data, at the cost of needing to re-export occasionally. We recommend automating your exports, often as part of your software's build process.

To be clear, you only need to re-export when major to a new major.minor version (ie 4.1 -> 4.2). Moving to a new patch version never requires re-export (ie 4.2.10 -> 4.2.16). Version numbers are major.minor.patch.