@@jestarray It's fine, and I ended up finding a python script that can create that slice data, but it is a little bit unfortunate. Admittingly my use case is a bit niche. I wanted to create a texture array from several smaller textures, move them around in Aseprite and modify them, then unstitch them and have them go back to the file they came from. While aseprite does save the frame data if you create a texture atlas from the command line, moving any of the textures around in aseprite afterwards does not get saved, and makes unstiching them impossible. Thus I was looking to somehow programmatically create the slices upon creating the atlas so I could use --split-slices to unsplit it, while also moving them around on the canvas for easier editing. Color me surprised that aseprite does not have a built-in json import function.
nice i have been use Piskel
This does not work with slice data.
Nope, I never used 9 slice so I'm not too familiar with it, sorry.
@@jestarray It's fine, and I ended up finding a python script that can create that slice data, but it is a little bit unfortunate.
Admittingly my use case is a bit niche. I wanted to create a texture array from several smaller textures, move them around in Aseprite and modify them, then unstitch them and have them go back to the file they came from. While aseprite does save the frame data if you create a texture atlas from the command line, moving any of the textures around in aseprite afterwards does not get saved, and makes unstiching them impossible. Thus I was looking to somehow programmatically create the slices upon creating the atlas so I could use --split-slices to unsplit it, while also moving them around on the canvas for easier editing.
Color me surprised that aseprite does not have a built-in json import function.