In my case each skin represents an individual character, and we're trying to keep it so that each skin is totally contained within a single atlas for processing reasons. When an individual character is generated, only one atlas need be loaded for that character. Based on this other thread (Organize atlases by skin automatically) and further exploration on my own, the only way to accomplish this is to use the texture packer and subfolders. Each subfolder corresponds to a skin.
I want to be able to import data so that for the first skin within a project file I can have all the image attachments arranged automatically for me. The first skin is done. Then when I create a skin for a different character I can easily update the original images. I wasn't aware of the find and replace feature, but that will make this step even easier.
The problem is that the Images directory will be set to whatever folder the JSON points to, in this case a subfolder (i.e. /images/character-01). I need to have access to all the subfolders, but when I update the directory path to the root folder (/images) the image paths break and I have to update them and point them back to the correct subfolder (/images/character-01). I could create a dummy skin that exists solely for the initial setup and is contained within the root folder rather than a subfolder, but I still have to go through and update every image so this doesn't strike me as any more efficient.
Basically what I'd like is for the script to recognize that I'm pointing to a subfolder, and therefore I don't want the entire image directory to also point there instead of the root. Does that make more sense?
Before fixing the Images directory path
After fixing the Images directory path
