Interesting - I’ll take a look at the palette save function to make sure it’s not misbehaving somehow. What operating system are you using?
Hi again Mushrooms, thanks for your patience while I looked into this. I just tried the current version of the extension on my PC under Windows 11 and it doesn’t appear that the extension is saving imported palettes as read-only, and I am still able to add new colors to imported palettes as normal.
As an additional test, I opened my palettes folder and deliberately set one of my imported palettes as read-only and I was still able to modify it in Aseprite.
Here are some steps that might be worth trying:
- change the palette format used by the extension from *.gpl to *.aseprite (you can do this via the importer’s settings dialog), then import a new palette and see if you can modify it - if that works, then I’ll have some more digging to do
- Reinstall the extension
- Make sure Aseprite is up to date
- Try setting the permissions on your palettes directory manually (you can open it via the button at the bottom of the palette list in Aseprite)
FWIW, I noted that at least on my machine the palettes directory shows that the folder is at least partially read-only (the checkbutton in the Windows properties dialog is dashed), but none of the palettes I had imported via the extension were marked as such.
Sorry I don’t have anything more concrete for you at the moment.