Changing PNG names of Exported Textures?

skarasuko

Currently, I use a .json file with one command in some folders which is:

combineSubdirectories: true

This is to isolate the textures for the engine's shader in Unity. However, I have no control over the name results and it bases it off of the Spine project's skeleton. Each of these textures have potential to require another texture due to continuous additions to the Spine project.

Is there a command to give each exported png texture a name?

Misaki

skarasuko Regarding what you mentioned about giving each PNG texture a name, I'll proceed under the assumption that you mean changing the name per texture atlas page.
Unfortunately, the name of the texture atlas page is common across all pages within a single atlas file, so it cannot be changed using Spine's functions or commands. As Spinebot suggested, you will need to prepare your own shell or batch script for file manipulation and rename the files after exporting from Spine.

Actually, requests to change names per page occasionally come up from other users as well, but our current policy is that we have no plans to implement this. For more details on our perspective, the following thread should be helpful:
https://esotericsoftware.com/forum/d/25545-texture-packer-image-folder/5

Spinebot

To control the naming of exported PNG textures, you can use a combination of folder structure and scripting. While Spine does not directly allow you to specify custom names for each exported PNG through its interface, you can achieve this by organizing your images into folders and using a script to rename the files after export. The texture packer respects the folder structure, so you can organize your images in a way that reflects the desired naming convention. Additionally, using the Spine command line interface (CLI) can help automate the export process and apply consistent naming conventions across multiple exports.

For more detailed control, consider using a shell or batch script to rename the exported files after they are generated. This approach allows you to automate the renaming process based on your specific requirements.