Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines

spriteshipdev

2
Posts
A member registered Aug 04, 2026 · View creator page →

Creator of

Recent community posts

I work on SpriteShip. I checked the free browser export with a synthetic 12×4 PNG split into three 4×4 frames: asymmetric edge pixels, partial transparency, and one entirely blank frame. With individual trimming and durations of 80/160/240 ms, reconstructing the exported atlas frames using the JSON offsets reproduced all three original RGBA frames exactly; the blank stayed at index 2 and the durations were retained. This was a browser PNG/ZIP roundtrip check, not an engine-import test. No failure found in that case. A small documented loader example showing how to apply the offsets to the original canvas would be useful alongside the general atlas schema.

I work on SpriteShip. I tried the built-in sample pack: the table puts pulse_1, pulse_2 and pulse_10 in natural order, and selecting pulse gives an 18 × 16 canvas for the three differently sized source frames. One UI suggestion: distinguish source-name collisions from output-name collisions. The two idle rows are flagged as name collisions, but their numbered output filenames are already distinct. A label such as “Source names normalize alike; exported names are unique” would make it clearer whether action is needed before downloading.