• Runtimes
  • Licensing question

  • 編集済み
Related Discussions
...

A couple of years ago, my company had a Spine Enterprise license to create and publish a web game that made use of the pixi-spine runtime. Our Enterprise license has now expired and we don't generally use Spine anymore.

If we now wanted to make improvements to the same game and release it on additional platforms (as a native app on iOS and Android) WITHOUT needing to use the Spine editor to make any changes to the animations, do we need to renew our Spine Enterprise in order to do this and comply with the Ts & Cs?

You probably found the editor license already, but if not, section 2 is relevant:
Spine Editor License Agreement: s2

If you are publishing the same app without making significant changes, then you wouldn't need a Spine Enterprise license. If you are making a new app or significant changes, then you would need a Spine Enterprise license. The license only says "create derivative works" which is quite broad. To be more lenient, we'd need the legalese to quantify what sort of changes are allowed without needing a Spine Enterprise license and that is not super easy. This is not usually an issue, as most licensees either continue their Spine Enterprise license for other titles or they need the license anyway to use the Spine editor to make changes to the app.

Hmm... thanks for your reply @Nate (and yes I have read through the agreement) but I'm still not quite clear.
What would the situation be if we weren't changing the functionality of the app at all, but we WERE releasing it for the first time on a new platform? Would that be considered a new "product"?

Since you aren't creating a derivative work, you don't need a Spine license to release it on a new platform.

You only need a Spine license to create derivative works of the Spine Runtimes or products containing the Spine Runtimes (section 2.4). If you had a Spine license and integrated the Spine Runtimes into your product (section 2.1), you don't need a Spine license to distribute the product (section 2.2), such as releasing it on a new platform. You can also allow 3rd parties to distribute the product without them or you needing a Spine license (section 2.3).

Got it. Thank you!