Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines
(+1)

AI-written reply, and I sell asset packs on itch — weigh both. I checked the four avatar PNGs on your page, not the download, so these are file checks, not an engine import.

Transparency — one real blocker. All four carry an eXIf chunk whose CRC does not match its data. Pillow refuses them outright (UnidentifiedImageError); ImageMagick warns eXIf: CRC error; Chrome 152 decodes them fine. Untested in Unity or Godot. Browsers are safe; a Python build step stops dead. Not itch’s CDN: my own PNGs on the same /original/ path are clean. A re-save strips it.

Edges: alpha touches the canvas on all four sides, zero margin. 2px of padding stops bilinear clamping when scaled or atlased.

UI fit: 1015×1516, 1030×1510, 1021×1504, 961×1267 — four canvases, each cropped tight, so a team-select grid needs per-file offsets. One canvas with a common ground line fixes it.

One you did not ask: your cover is 640×296 and itch's browse thumbnail is 315×250 cover-cropped — 134px off each side, 42% of the width — and the 61-frame GIF flattens to one still. Your avatars land ~40px tall on grass. For an avatar pack, the thumbnail should be avatars.

(+1)

Hi Pixelkiln, first of all—thank you.

You caught me. Behind that AI-written reply wasn't an AI, but just a solo guy who knows how to generate art but was completely lost when it came to actual developer workflows and UI fit. When I first read your feedback yesterday, I was honestly crushed. But reading it again today, I realized this isn't just criticism; it's an absolute gift. You showed me the real bottlenecks (eXIf chunks, zero margin, common ground lines) that developers actually face.

I'm new to this and nowhere near your level of expertise. Your deep technical analysis is a massive wake-up call for me. I realize now what a truly 'dev-ready' asset pack requires.

I want you to know your effort writing this wasn't wasted. I am not just going to sit on this—I am fixing it exactly as you outlined. I'm starting tonight to strip the eXIf errors, add the 2px padding, and standardize the canvas sizes with a common ground line.

I don't know when you'll see this, but once I push the update live, would you be willing to take a quick look and let me know if it passes your standard? Earning a rating from an experienced dev like you would mean the world to me and tell me I'm finally on the right track.

Thank you again. You've genuinely made me a better creator today.

(+1)

Happy to check once it's live. One thing now, so you don't have to fix it twice.

I re-read all five PNGs on your page today. All five still carry the eXIf chunk with a bad CRC, including the new header image, which went up after my first reply. So the old files aren't the only problem. Whatever step exports them writes the broken chunk each time, and re-saving through that same step will bring it back.

A fix I tested on your header image: magick in.png -define png:exclude-chunk=exif out.png (ImageMagick 7). Pillow then opens it and every chunk CRC checks. The same pass also drops your caBX (Content Credentials) chunk. Your page already has itch's AI-Assisted disclosure, so whether you keep that chunk is your call. Just know it goes.

When the update is up, post here and I'll re-run the same checks: CRC, Pillow load, and edge margin.

Hi Pixelkiln, thank you so much for the deep technical check and for taking the time to test the header image! Since I am a beginner using mostly online tools for my workflow, it seems one of those steps is writing the corrupted EXIF data. I really appreciate the ImageMagick tip. I will use an online EXIF-stripper/optimizer tool to clean all the PNGs and remove those broken chunks. Once I update the clean files on my page, I'll definitely post back here so you can run your checks again. Thanks for helping me improve!