[SOLVED] Re-uploading a texture atlas is too tedious


#1

We are using texture atlases to minimize the number of files that would be downloaded.
If some new image is to be added to the image,
we first repack the image using TexturePacker.
Then we manually reorder the created json file to match the previous atlas’s order.
Then we click and drag every sprite that needs 9-slicing.

I won’t bother hasseling you about the internal frame information being saved in numbers
“frames”: {
“0”: { },
“1”: { } …

Can you at least consider reading 9-slice info when a json file is uploaded?


#2

@vaios recently made a TexturePacker plugin to make this process a lot less tedious.

You can download the zip here, and then just follow the instructions in the README.

Let me know if this helps ease your workflow!