You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
SpineSeperatorNode or SpineRenderSeparatorNode would split a Spine skeleton in two or more parts with different Node2D Z Index property values. Presumably, this would be set to be a parent node of any SpineSprite that would require this functionality.
Use cases:
Users might need to display in-world objects between parts of Spine character, e.g. to let the character run into a tree and display one leg in front and one behind the trunk.
Interactions between multiple separate Spine characters that have different rendering order requirements depending on the animations played. For things like hugs.
This would also work for advanced character customization systems where the body is separate from the head skeleton and the head has to render the face in front of the body and some of the hair behind the body skeleton. I'm aware SpineSlotNode could sorta achieve this by inserting the body in a dummy slot between the face and the hair, but this does not address all use cases, especially when the body is the same and it's only the heads which are swapped.
The text was updated successfully, but these errors were encountered:
SpineSeperatorNode or SpineRenderSeparatorNode would split a Spine skeleton in two or more parts with different Node2D Z Index property values. Presumably, this would be set to be a parent node of any SpineSprite that would require this functionality.
Use cases:
The text was updated successfully, but these errors were encountered: