Hey,
We have a use case where we want to use Spine CLI as some sort of dedicated export machine for viewing only purposes.
Let me explain, at the company we have built a custom editor that uses JSON skeleton data, and then we pack with it various other data (sound, runtime vfx, gamplay data, etc.) that can be authored with it.
However, exporting the atlas texture from the editor for every changes is very error prone, especially when various people from different departments are involved. Additionally, we have a hot-reloading mechanism that uses the SPINE CLI to quicky update changes on the fly without having to generate the atlas.
Now, as far as i know the ToS does not prohibit the use of the CLI for batch export farm, but since our use case is that non-animators also uses SPINE CLI indirectly as a "viewing" tool (generating JSON skeleton data in the custom editor), and does not author Spine animation with it, without purchasing a new seat for each user, the case might be different.
We would like to inquiry Esoteric Software's stance about this.
Thank you.
