• EditorBugs
  • [Spine 4.2.10 -> Spine 4.2.17] All Skin Renamed

I have open a previous spine project where skin where like this :

folder "Head"

  • Human
  • Elf
  • Siren
    folder "Eyes"
  • Human
  • Elf
  • Siren
    folder "Ears"
  • Human
  • Elf
  • Siren

When I updated to Spine 4.2.17, the skin were renamed like this :

folder "Head"

  • Human
  • Elf
  • Siren
    folder "Eyes"
  • Human2
  • Elf2
  • Siren2
    folder "Ears"
  • Human3
  • Elf3
  • Siren3

The update seems to have renamed every skin without taking into account that they were in folder ... I usef only head/eyes/ears and human/elf/siren but in fact I have a lot more folder and skin, so this is a little bothersome ... Is there a way to avoid it ? I have this skin structure on ten project so I would prefer to don't have to rename everyone of them 😭

That being said, I used it on a new project and folder for constraint and slot order is just a pure ecstasy ... good job 🫡

Related Discussions
...

That shouldn't happen!

I created skins like this in 4.2.10-beta:

Изображение удалено из-за отсутствия поддержки HTTPS. | Показать


When I opened the project with 4.2.17-beta, the skins are named the same (both still named a but in different folders).

Maybe it's something else about your project? Could you send us the .spine file? contact@esotericsoftware.com

    Nate 我也遇到类似问题,4.2.09升级到4.2.18时。在不同文件夹内的相同名称的动画。有一部分会被重新命名。
    我把spine文件发你邮箱麻烦看看。

    Nate
    I've sended one of the project file, I hope you will find what's wrong.
    By the way, I also add animations renamed, just like HaiGeGe.

    Ooooh, this was my mistake:

    I created skins like this in 4.2.10-beta:

    I should have used 4.2.09-beta. 😬

    Thanks for the projects. We've fixed this in 4.2.19-beta, available in ~15 minutes. Sorry for the trouble!

    • Pentacles ответили на это сообщение.

      Nate
      Omg, you're right 🤣 I was waiting so long for 4.2.10 that I wrote the wrong number on the title 🤣
      My bad.
      I don't mind, I'm working on another project right now 🙂 .
      Thanks anyway for your responsiveness!