spine animation runtime libraries for various languages

#animation #library #gamedev #c #cpp #c++ #csharp #java #lua #flutter #libgdx #ts #xna

Nathan Sweet 87b9821e00 [as3][c][cpp][cs][libgdx][lua] Fixed crash with path constraint proportional spacing and tangent rotate modes. 4 년 전
.github 8dde2fd976 [ci] Update spine-libgdx workflow 4 년 전
examples 8db815bd33 [corona] Renamed runtime to spine-solar2d 4 년 전
formatters 109356268f Eclipse formatter update. 4 년 전
gradle 2fdd6e5c11 Upgrade Gradle to 7.0, fix libGDX build, add Java formatter 4 년 전
spine-as3 87b9821e00 [as3][c][cpp][cs][libgdx][lua] Fixed crash with path constraint proportional spacing and tangent rotate modes. 4 년 전
spine-c 87b9821e00 [as3][c][cpp][cs][libgdx][lua] Fixed crash with path constraint proportional spacing and tangent rotate modes. 4 년 전
spine-cocos2d-objc 688d855006 [runtimes] Updated examples with Editor version 4.0.58-beta. 4 년 전
spine-cocos2dx de697385fc [runtimes] Fix up README.md files using correct editor version. 4 년 전
spine-cpp 87b9821e00 [as3][c][cpp][cs][libgdx][lua] Fixed crash with path constraint proportional spacing and tangent rotate modes. 4 년 전
spine-csharp 87b9821e00 [as3][c][cpp][cs][libgdx][lua] Fixed crash with path constraint proportional spacing and tangent rotate modes. 4 년 전
spine-js 45362e60bf [all] Source clean up, formatting, and tabs for indentation. 6 년 전
spine-libgdx 87b9821e00 [as3][c][cpp][cs][libgdx][lua] Fixed crash with path constraint proportional spacing and tangent rotate modes. 4 년 전
spine-love 3f735ed0be [lua] Ensure clipper.clipEnd() is called appropriately. See #1694 4 년 전
spine-lua 87b9821e00 [as3][c][cpp][cs][libgdx][lua] Fixed crash with path constraint proportional spacing and tangent rotate modes. 4 년 전
spine-monogame de697385fc [runtimes] Fix up README.md files using correct editor version. 4 년 전
spine-sfml de697385fc [runtimes] Fix up README.md files using correct editor version. 4 년 전
spine-solar2d de697385fc [runtimes] Fix up README.md files using correct editor version. 4 년 전
spine-starling 33ffd065d1 Merge branch '4.0-beta' into 4.0 4 년 전
spine-threejs 45362e60bf [all] Source clean up, formatting, and tabs for indentation. 6 년 전
spine-tk2d 45362e60bf [all] Source clean up, formatting, and tabs for indentation. 6 년 전
spine-ts 87b9821e00 [as3][c][cpp][cs][libgdx][lua] Fixed crash with path constraint proportional spacing and tangent rotate modes. 4 년 전
spine-ue4 7b0d71568b [ue4] Set mixes on native Spine data upon retrieval via Atlas. Closes #1772 4 년 전
spine-unity ea991a6324 Merge branch '3.8' into 4.0 4 년 전
spine-xna de697385fc [runtimes] Fix up README.md files using correct editor version. 4 년 전
.gitattributes a7dc2b1d8f gitattributes: set .cginc and .shader files to lf line endings to prevent Unity code auto-updater to create mixed line endings. 6 년 전
.gitignore 30702a3bff [c][cpp] Fix AnimationState::clearNext() 4 년 전
.npmignore a8a20fce13 Add npm support (#793) 8 년 전
CHANGELOG.md 63d8d17620 [unity] Reordered changelog 4.0 spine-unity section entries, now thematically ordered (as on the forum post) instead of chronologically. 4 년 전
CMakeLists.txt 30702a3bff [c][cpp] Fix AnimationState::clearNext() 4 년 전
LICENSE 86a529d01c Updated LICENSE. 6 년 전
README.md 849e9acc7e Updated READMEs. 6 년 전
build.gradle c2b1ecb195 [libgdx] Fix line endings, CRLF -> LF 4 년 전
gradlew 2fdd6e5c11 Upgrade Gradle to 7.0, fix libGDX build, add Java formatter 4 년 전
gradlew.bat 4005b4dee9 Support for Gradle building, installing, and jitpack (#1431) 6 년 전
package.json a8a20fce13 Add npm support (#793) 8 년 전
settings.gradle 4005b4dee9 Support for Gradle building, installing, and jitpack (#1431) 6 년 전

README.md

Spine Runtimes

This GitHub project hosts the Spine Runtimes which are needed to use Spine 2D skeletal animation data with various game toolkits.

Licensing

You are welcome to evaluate the Spine Runtimes and the examples we provide in this repository free of charge.

You can integrate the Spine Runtimes into your software free of charge, but users of your software must have their own Spine license. Please make your users aware of this requirement! This option is often chosen by those making development tools, such as an SDK, game toolkit, or software library.

In order to distribute your software containing the Spine Runtimes to others that don't have a Spine license, you need a Spine license at the time of integration. Then you can distribute your software containing the Spine Runtimes however you like, provided others don't modify it or use it to create new software. If others want to do that, they'll need their own Spine license.

For the official legal terms governing the Spine Runtimes, please read the Spine Runtimes License Agreement and Section 2 of the Spine Editor License Agreement.

Documentation

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.

Bugs, enhancements, and tasks

Review our backlog of bugs, enhancements, and tasks in the spine-runtimes and spine-editor issue trackers. Our roadmap provides a more convenient view of the same issue tracker information.

Versioning

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.

Contributing

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 [email protected].

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.