tsukina-7mochi / aseprite-scripts Goto Github PK

Hey there,
Thanks for this script! I just tried it out and run it, then the following error message comes:

Could you help me?

Thanks,
Abo

Hi!
I get this error (7:unexpected symbol near ‘<’ ) when I try to run the scripts on both the uploaded lua files. Is there something I can do?

Hello, The script works, but it only saves one frame. So if I have a file of 10 layers and 10 frames, It will only choose the layers under the certain frame and save that one frame (for whatever frame I selected) and all the layers below it. But I was wondering if I could save a flattened file with ALL the frames so that I can save the animation and open it on Photoshop since Aseprite doesn't support 256 colors like Photoshop and breaks the animations that have transparency in it.

PSD files exported via CLI have smaller size and cannot be loaded in Photoshop.

Hi,

I'm facing error in the code, is there any version requirement?

Here's the ide info:

Thanks.

Hi, first of all, thank you very much for creating this script! :)

I’ve just tried the script but it seems that it doesn’t work 100% correctly. I made a simple sprite in Aseprite, with just one layer and one frame, saved it, and the exported it to psd.

After that I tried to open the psd file with other programs, but I got these errors using Photoshop and Gimp:

I could open the psd file using Krita, but the image was pretty broken.

Any idea of the cause of the problem?

Both the LICENSE.md and each project directory claim that all scripts are MIT licensed.

However, all .lua files contain this in their header: DO NOT redistribute this code

In addition, the README.md files explicitly state:

• You cannot redistribute files with no change without my permission.

This is in direct contradiction with the MIT License:

Permission is hereby granted [...] to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software [...]

As of right now I have to treat the repo as effectively unlicensed, as the stricter restriction is usually what applies. Would it be possible to clear up this licensing issue?