Phaser-Spine not in list of runtime implementations
- Edited
+1, and it works very well !
I would like to know what are the features that are'nt supported at this moment by this one
We generally rely on the maintainers of 3rd party Spine runtimes to tell us about their efforts. Guess we didn't catch this one. It's not based on the latest spine-ts runtime, but rather uses the old spine-js runtime, which means features at Spine 3.1 level. Added it to the runtime page!
Thanks! The maintainer of this implementation says performance with Phaser on a mobile game was pretty decent for them. We can animate with the latest version of the editor and use this to play those no?
No, this runtime seems to only support Spine 3.1, nothing above. That means things like paths, transform constraints, the reworked format of meshes in the .json file exported by Spine, and other things introduced after 3.1 won't work. You can poke the author of the runtime to update to our latest core library, the rest (Phaser specific code) can probably stay the same.
Ah that's why I was wondering why some of the spine-ts demo animations don't run properly.