@tasco exports to non-desktop platforms, that's a big item on my todo list. I want to make sure everything else is good first.
@Ryusui that's actually what I spent most of my time on They way attaching other nodes is planned to work is like like this:
- In the inspector for SpineSprite, you have a dedicated section where you can specify which node should be rendered before/after which slot. It's not using the standard array or dictionary inspector UI, but a custom UI with drop downs for slots and node paths.
- In code, you will have setters to add/remove nodes from slots.