This GitHub project hosts the Spine Runtimes which are needed to use Spine 2D skeletal animation data with various game toolkits.
You can play with and evaluate the Spine Runtimes and the examples we provide in this repository free of charge.
If you use the Spine Runtimes in a product, like a game or an app, you need a valid Spine Editor license at the time of integration. You can sell the product to consumers and other companies without any additional licensing requirements, provided they can not modify the product. However, if you sell your product to another company that wants to modify the product, the company will need a Spine Editor license. You can keep selling your product even if your Spine Editor license expires!
If you integrate the Spine Runtimes into development tools for other developers, like an OSS game engine, or a commercial SDK, the users of your development tools will need a Spine Editor license. Please make them aware of this requirement!
For the full legal terms governing the Spine Runtimes, please read Section 2 of the Spine Editor License Agreement and the Spine Runtimes License Agreement.
See the Spine Runtimes Guide for detailed information about using the Spine Runtimes. The Spine documentation page provides further information about tools and data formats. For runtime specific documentation, refer to the README.md file in each runtime directory.
Review our backlog of bugs, enhancements, and tasks in the spine-runtimes and spine-editor issue trackers.The spine-runtimes roadmap provides a more convenient view of the same issue tracker information.
The default branch on GitHub is stable and works with data exported from the latest, non-beta version of the Spine editor. New development is done in an X.X-beta branch, which may be a work in progress. Important changes to the runtimes can be reviewed in the CHANGELOG.md file. Occasionally the Spine Runtimes are tagged with the specific Spine editor version they work with.
It is highly suggested to freeze the Spine editor version to match the Spine Runtimes source being used and to update them in lock step. See the Spine Runtimes Guide for more information.
In order to merge your contributions, we need a signed contributor license agreement (CLA) from you. You can send a copy of the CLA to contact@esotericsoftware.com.
When possible, it is best to base your contributions on the current beta branch (X.X-beta). Please be sure to follow the style and formatting you find in the respective runtime code to which you are contributing.