To speed up our pipeline process I've written a CLI tool to help automate the exporting of Spine files.
However, I've noticed that the "Attachments" option for packing when exporting is only available in the Spine GUI, whereas the CLI can only specify an images folder. This poses a problem for us since some of our projects contain images which aren't used by any attachments and which would normally be excluded from packing by the "Attachments" option, but are unnecessarily included in the atlas when exported via the CLI.
We have a large pre-existing base of Spine projects which we need to re-export for the move to 4.0, so manual solutions like simply removing the unused image files, or moving them all into separate folders and adding pack.jsons to ignore them, aren't practical.
Are there any workarounds or perhaps options or settings that I may have missed which could help here?
Or, if any Spine devs are reading, would adding the "Attachments" option for exporting via CLI possibly be on the backlog anywhere? c;
(Relevant docs regarding the "Attachments" option)
http://esotericsoftware.com/spine-texture-packer#JSON-Configuration
Thanks,
I'm not sure how I missed this, but it turns out you actually CAN use the "Attachments" option via the CLI...
We ended up finding out by manually editing the export settings JSON, changing
"packSource": "imagefolders"
to
"packSource": "attachments"
But it seems that just normally saving the export settings from Spine also properly sets this value.
In any case, problem solved I guess lol
