#Skins spine2d skin
skin: If true, the constraint is only applied when the active skin has the constraint.order: The ordinal for the order constraints are applied.The "transform" section may be omitted if there are no transform constraints. The bones section describes the bones in the setup pose. audio: The audio path, as it was in Spine.images: The images path, as it was in Spine.fps: The dopesheet framerate in frames per second, as it was in Spine.
x: The x-coordinate of the bottom left corner of the AABB for the skeleton's attachments as it was in the setup pose in Spine.This can be used by tools to enforce a particular Spine version to be used. version: The version of Spine that exported the data.This can be used by tools to detect if the data has changed since the last time it was loaded. hash: A hash of all the skeleton data.The skeleton section stores metadata about the skeleton. This is stateless data that is not tied to a particular on-screen skeleton instance. The JSON format is the serialized version of a "skeleton data" instance, which has a list of bones, slots, skins, and animations. This data is not required for rendering but may be useful for tools or when importing the data back into Spine. The downside is that the JSON format has a larger file size than the binary format and is slower to load at runtime.ĭata marked "nonessential" is only output when the Nonessential data export setting is checked. It is also resistant to minor changes in the runtimes, which may prevent the need to re-export the data when the runtime changes. This makes it a good choice when needing to manually inspect or otherwise process the data. The JSON format is human readable and editable, especially when used with the "pretty print" setting.
#Skins spine2d code
You do not need to write your own loading code unless you are writing your own runtime from scratch (which is an enormous amount of work). The Spine Runtimes handle loading JSON and binary data. Also, Spine can import data in this format, allowing interoperability with other tools. The Spine Runtimes load this data to display animations. It does not store any personal data.This page describes Spine's JSON export format for skeleton and animation data. The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. The cookie is used to store the user consent for the cookies in the category "Performance". This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary". The cookie is used to store the user consent for the cookies in the category "Other. The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional". The cookie is used to store the user consent for the cookies in the category "Analytics". These cookies ensure basic functionalities and security features of the website, anonymously. Necessary cookies are absolutely essential for the website to function properly.