itch.io

Do you mean to have snapshots show up in the edit history or to reverse course if you undo an action?

Hi, I pushed an update yesterday to address this. If you’re still experiencing this with the newest version after downloading please let me know.

Update: I have a fix together. Still testing it but I’m hoping to push it this weekend after verifying.

Still digging into this - it seems something changed in the underlying system relating to when the script saves a snapshot.

A weird workaround for the time being is if there is something in 0,0 (top left most corner pixel) it won’t bug out - like having a colored in background layer. I think it has something due to how the app looks at a sprite’s dimensions.

Hoping to come up with a solution that doesn’t require a work around.

Hi, sorry you’re running into an issue. This is definitely a new one since the script isn’t supposed to modify the active sprite. Let me dig into this and see if I can figure out what is happening.

It seems to happen if there is nothing in the corner (0,0) on your active layer and you hit control…Hoping I can spend some time to sort that out :|

Sorry about that, I’ll be sure to update to the usage notes to include that limitation.

Hi, I’m sorry you’re running into issues.

What version of Aseprite are you running it on? It would also help to know what values you’re setting when using this script.

That is interesting. I will need to poke at this to see if it’s a me or an Aesprite issue. Thanks for sharing.

It may be a box was checked stopping the behavior like mentioned in this comment https://itch.io/post/11079990

If you want to modify the name output when saving the snapshot, you should be able to edit this line as that is where the saved filename is built out https://github.com/sprngr/aseprite-record/blob/master/Automatic%20Snapshot.lua#L122

They should be getting saved to the folder where the image you’re working on is.

Odd, because that’s the exact same error on Linux I just fixed in the latest release. I will try to see if I can find some way to replicate it again but I’ll ask in the mean time you reinstall my script to make sure it replaces it with the newest copy. Sorry for the inconvenience.

Hi, whatever screenshot was included seems to not attached. A recent fix was pushed out in the past 3 days regarding an issue encountered by Linux users, I would recommend making sure you’re on the latest version.

I was able to get Linux setup and reproduce the error. A fix has been pushed up and should resolve it. Thanks for raising the issue.

Thanks for bringing this up. I’ll go check the github issue filed and see if I can get some time set aside to look into this.

Sorry you’re encountering issues. I had tested on Linux when developing this but it could be anything specific to your configuration. Is the directory it would save to set with permissions for the script to be able to perform a write? If you included a screenshot of your error it appears to not have attached.

I haven’t tested it with Libresprite, but if it has the exact same APIs it may work. This will be something I’ll need to dig into before giving a definitive answer on compatibility.

Edit: Based on what I see, Libresprite is based off a much older version of Aseprite and will be lacking the more recent APIs it had added in so there will not be support there. Sorry for the inconvenience.

Solid game, too busy going for one drop off max combo.

Hi, please check the Preferences for Alerts and make sure your option for “Open a sequence of static files as an animation” is set to either “Ask” or “Yes”. This should get past the problem of only opening a single image.

If you go to the timelapse folder (the sprite name, suffixed with _record) for a sprite, and open the first file suffixed with 0 via the File > Open dialog in aseprite - it should attempt to load all files sharing the sequence, like the included image, . The folder should contain an _index.txt file and all of your snapshot pngs assuming you’re using a current version.

Based on the error you are getting, that would indicate there are not any snapshots taken for the file you have open. The Open Timelapse function acts upon the currently active sprite in your editor.

If you open the first png in the list on its own in Aseprite, assuming the files are named sequentially, it will trigger the same prompt the plugin uses. Does that work?

Good point. I’ll work on some text to help make it more apparent.

I’m not sure if I would be able to pull that off with the way the Aseprite API works but I can put on my todo list to look into see if there are better methods around converting snapshots into the final timelapse.

Please try the most recent version of the plugin, the changes introduced may have resolved your issues.

No worries about the C-like Lua, I hadn’t really written any Lua prior to this extension so a lot of it was learned on the fly.

I did managed to squeeze out the compatibility shim, I think it’ll resolve any possible issues that may arise.

Regarding a version file, I don’t imagine it’ll be necessary as I tend to aim to keep things backwards compatible - and based on the nature of the utility I would figure people won’t tend to go back to previous snapshots once they’re done with their piece. Something to think about though, like tracking more meta data if necessary.

Just a heads up, I’ve pulled in your updates to the project with a minor tweak to maintain compatibility with existing snapshot files & added documentation for a migration path for anyone who may try to use the update with said existing snapshot.

Oh wow, that’s quite an update. I’ll give it a read through and let you know if I pull it back into the main project.

Sorry to hear that things aren’t going so well. I’ll try to help in any way I can but cannot guarantee I’m able to figure out a solution.

What version of Aseprite are you running? Are you using the most recent version of this plugin? Do you have any other plugins/extensions running? If you are using the automatic snapshot functionality, what interval are you recording at? How big is the file you are working on?

Wow, that’s great!

I figured as much - maybe they’d be open to accepting a PR for such a change to improve more automation like extensions if it was reasonable.

I would be, but I assumed it’d require some way to to override the dialog that wasn’t exposed via the API.

You will not be able to use the most recent version that contains the automatic snapshot tools, but you will be able to leverage the previous version that has the manual controls. That can be downloaded here (https://github.com/sprngr/aseprite-record/archive/refs/tags/v1.2.zip)

That’s an interesting problem.

What Aseprite version are you using?

Do the files have sequential names?

Are you able to open the first file in the list with Aseprite like you would any other file and have it try to prompt then to open as an animation? That piece is built into Aseprite, so I’d be interested to see if that works.

I’m going to test on my PC when I get some free time but hoping we can figure out what has gone wrong.

It cannot take automatic snapshots, I had tried to include a timer but doing so locks up Aseprite while the timer is enabled.

Given that’s the case, I do provide some tips as to how to enable triggering the snapshot via keyboard shortcut.

Glad you were able to get over that hurdle. Hope you find the scripts to be of use :)

Thank you for reaching out.

The scripts menu should be under the File tab on the main menu. I just checked it in the current version and did a reinstall to make sure everything is working as expected.

What version are you using? The scripts require at least version Aseprite 1.2.17.

Thank you! Hopefully you’ll be able to find use with it to make your progress gifs.

This was really fun. I like the idea of wanting to not dodge the bullets. Great artwork and sounds too!

I love the idea, I love giant monsters too, but it was fun to run around and attempt to "hide" while I'm knocking over buildings.

I like the approach, it is a bit challenging but that's what helped keep me playing. Great work.

I really liked your approach to moving between platforms, but also requiring the player to be smart about it with the evaporating slime mechanic.