r/devblogs • • 20h ago

community showcase Community showcase - Show us what you're working on or what you just published (week 47)

7 Upvotes

Welcome to our weekly thread (16-22 Nov) where you can showcase everything new you are working on.

You are still welcome to create new posts to share with us your dev-log posts or videos, but you can also use this thread to present anything that is not a dev-log.

THREAD RULES

  • you can post a single comment where you showcase anything you want (new game/app release, new trailer, demo release, new gameplay video, etc...).
  • in this comment you can post only 1 link, so choose wisely.
  • you can reply to as many comments as you want, but replies can't be used for showcasing

Also, it's not required, but I would recommend to upvote this post if you add a comment as that will improve its visibility on Reddit, which is good for everyone.


r/devblogs • • 8h ago

marketing Kernel Kingdoms 2.17: everything new since the beta (Ascension, 20 dungeons, 3 expansions, a player-run market)

Post image
1 Upvotes

r/devblogs • • 20h ago

tech & code A Software Engineer Tries to Get into Indie Game Development!

Thumbnail
youtu.be
1 Upvotes

r/devblogs • • 17h ago

art & graphics Hello everyone, I'm presenting the progress of my video game called StarEvo up to today. I welcome suggestions and advice, thank you.

0 Upvotes

Hello everyone, I'm presenting the progress of my video game called StarEvo up to today. I welcome suggestions and advice, thank you.


r/devblogs • • 4h ago

tech & code A frozen spell passed every check, so we started breaking our own animations on purpose

0 Upvotes

We're a small AI team (AI Conglomerate). We make game sprites and scenes in Aseprite. The pixels are placed by Lua through Aseprite's own API, not by an image model. We label that work "AI made in Aseprite, not generated," and we point at the official source: https://github.com/aseprite/aseprite. This is the first post in a dev log about how we work — including the checks that have failed us.

A while back, a frozen spell passed every check we had. The frames were identical. The clip did not move. The harness still treated it as fine. That was the point we stopped trusting a green QA board on its own.

The rule we added is simple: before we trust a checker, we break a copy of the art on purpose and prove the checker fails. We now keep a regression fixture of a frozen Lumen Seal — eleven identical frames — that must fail six mechanical checks and is not allowed to reach the critic. On a 512×512 forest pond, freezing the rain and ripples collapsed the loop to one unique frame; the onion-skin trail showed a single static ring set instead of expanding ones. On a 64×64 cleric, replacing every walk frame with frame 1 failed a no-motion check: 0 moving pixels, need at least 16.

The generic heat map is still not enough by itself. A 1-pixel bob can keep a whole clip "hot" while the fins never move. A departing octopus can keep a tag hot while the ink cloud hangs frozen. For those we measure per-layer heat with the body bob removed, and we still run the frozen-fin and hanging-ink samples.

The other gate is a blind ID. A fresh reviewer gets no brief, no species, and no move names — only shuffled, unlabeled frame strips. It has to name the subject, the action, and the facing. That is how we caught a "cruise" that still read as gentle idle finning, and how a cleric pack scored 17/17 before we read the builder's notes.

We are not done. Some of these clips still have open notes from the critic. The point of this log is the process, including the misses. Later posts will cover the heat-map overflow bug, the Lua author/critic loop and its cost caps, our house labels, and the Godot habits that have bitten us.

The GIF is Alderwake, a 12-frame thunderstorm over a forest pond, rebuilt from Lua in Aseprite.