joo
Hello Joo, and welcome back. Doing that with the spine-player is tricky. In the meantime, we added spine-webcomponents to our official runtimes, and you can read the full documentation here.
There's a feature to load atlas pages on demand, which you can see in action in the dragon example. The skeleton is fully loaded, just press the buttons to load a specific page.
If you organize your traits/skins into different pages, as explained here, you can then load the specific page for the desired trait/skin on demand.
To achieve that, we created a new loadTextureAtlasButNoTextures method. It creates the pages but does not load the textures. Textures can then be loaded when needed.
However, making this work with the spine-player requires a very specific customization for this use case, adding many additional lines of code to an already complex component. It’s probably much easier to fork it and change the default behavior.
