Nice video!
Note if you have binary skeleton data file, you can't use the JsonRollback tool. Instead, you can load the JSON with the old version of Spine, then export JSON and use that with JsonRollback. But what is the old version of Spine? You can see the version near the start of the binary file if you open it with a text editor (or hex editor). There will be lots of junk, but the version should be pretty obvious. For example, it might look like this:
Ç¢Õ‹’3.8.99Ã<¢@Àþ...
Of course the version of this binary data is 3.8.99.
Everyone should keep in mind that if you need the JsonRollback tool, you've messed up. People should be very careful to use the editor version that matches their runtime version.
Unfortunately the difference between 3.8 JSON and 4.0 is very large. It won't be possible to convert 4.0 data to earlier versions. There are a few reasons why, but the biggest is that 4.0 can describe curves in ways that aren't possible in 3.8. I fear a lot of people will update to 4.0, do work, and then be unhappy they can't use it with 3.8, as they always seem to do. We'll give some more thought for how this might be mitigated.
FWIW, you can use `
hide-license` to hide your name and email when starting Spine.
