Hi @Nodragem, the --palette is an old parameter used to change the default palette of the program (almost useless nowadays). You are the second user that found the same problem so I'll change the meaning of --palette parameter so we can change the palette and save the sprite with different palettes (it makes a lot more sense).

Anyway, there is a quite "hidden" feature that I made some time ago for that other user. You might try to use the script inside the attached .zip (save-with-other-palette-test.zip) and execute Aseprite in this way:

./aseprite -b --script test.js 

See the content of the test.js file. You will see that it's straight forward to change it for your needs. I hope you find it useful for your specific case.

This will be available in v1.2-beta2. An example for the future usage syntax:

aseprite -b test.bmp --palette pal2.bmp --save-as test2.bmp

Thank you!

Concerning the hidden feature. Are you telling me that we can simulate an Aseprite session with a javascript file? that sounds really powerful!
I did not see the --script command in the doc, I think that it should be an official feature :)

You're welcome! The --script is a little hidden because there is no official API yet, as you said, it can simulate just a few commands (also it's quite easy to crash Aseprite using the API incorrectly). There is some features with more priority at this moment like #126 and #475 which I think would be better for most users.

isn't #475 requiring the API we just spoke about?

More or less. Actions could be recorded in an XML file to execute UI commands, which then are easier to be modified/edited (so then you can edit your macro/actions step by step). Instead the API is a more text-based/scripting like set of functions that might be bigger than the available UI commands, also it could be then impossible to edit the script step by step from the UI (because that would be like refactoring the JavaScript code).