Okay, I’ve tested the extension on both Windows 11 and Mac OS Sequoia using the latest stable version of Aseprite, which at the moment is 1.3.10.1. It’s possible that since v1.3.11 is still in beta (not sure if you’re on -beta1 or -beta2) that not all of the API features have been implemented/are working correctly. For the time being I’d recommend rolling back to the stable version of Aseprite.
sudo_whoami
Creator of
Recent community posts
I’m afraid the short answer is no, or at the very least “I doubt it”.
The longer answer is: I don’t know what parts of Libresprite’s API are compatible with Aseprite’s API, if any. This extension also relies on Aseprite’s CLI to handle Lospec’s “Open In App” links, so that feature would almost certainly not work in Libresprite.
Hey again,
I just got another reply from user @PhoenixTamer who’s been running into the same issue on Windows and they found out that Avast was preventing the script from executing properly (likely because it relys on curl under the hood, but that’s a guess). I’m not sure if that’s what you’re up against, but it’s possible that your AV is being overzealous.
Thanks for the report. Based on the information from you and @PhoenixTamer, it seems like there’s something up with a file path somewhere when using the Steam version of Aseprite. This should give me a place to start looking.
That said, I don’t currently have a Linux machine (virtual or otherwise) set up for testing, so I can’t 100% guarantee Linux support with this extension, but I’ll do my best!
Thank you, that helps! If it’s every name you try then I can assume it’s not just one palette with a weird JSON issue. I just hav a couple more questions if you don’t mind.
- Are you using the Steam version of Aseprite or the standalone version?
- Have you tried removing and reinstalling the extension? If you do, I’d recommend a fresh download just in case something got corrupted last time!
Hey PhoenixTamer! Can you give me some more info when you get a second?
- What version of Windows are you using?
- What version of Aseprite are you using?
- What’s the name of the palette you tried to import?
- Does it only happen with that name, or is it every time?
That’ll help me narrow down the issue. Thanks for the report!
There's some kind of issue applying this theme to Aseprite 1.2.34.1-arm64 (MacOS 12.3). When I click "Apply", the screen just flashes briefly before going back to the default theme. I doubt this is an issue with your theme specifically, but I wanted to put this out there in case anybody else runs into trouble!