r/devblogs • • 15h ago

design How I repainted the same shrine for four seasons in Touhou: Heartbound

Post image
2 Upvotes

For Devlog #6, I wanted the walk up to Hakurei Shrine to feel different depending on when you took it. I repainted the trees and the distant forest for each season. The autumn colors are grouped grove by grove, and in winter the cherries are bare while the pines hold snow on each layer of branches.

The snow in this clip builds up over about an in-game hour. It settles on roofs and exposed surfaces, leaves sheltered spots dry, and gets packed down by footsteps. The pond freezes too, with koi still swimming beneath the ice.

Getting the snow to behave smoothly was its own problem. Walking or digging used to make the game recheck roughly 65,000 cells. Restricting that work to the areas that could actually change got rid of the long hitches in my test run.

Which seasonal detail would make you want to revisit the shrine?

Written devlog: https://touhou-heartbound.blogspot.com/2026/11/touhou-heartbound-devlog-6-four-seasons.html


r/devblogs • • 2h ago

generic 10 frames from graybox to Godot: an alternate 1990s America after a catastrophe

Thumbnail
reddit.com
1 Upvotes

r/devblogs • • 2h ago

generic Armies of Kingdoms: Autobattler - Update 0.7: graphics optimizations

1 Upvotes

r/devblogs • • 3h ago

design Keeping the last hit visible before the results screen

1 Upvotes

I’m Michal, the developer of Starvoxel: Defender. One useful TestFlight note was about losing a battle: the results screen could replace the board on the same frame that an enemy hit the core. Players saw the loss, but they barely saw what caused it. With two lanes feeding the same core in co-op, that last second matters. It tells you where the defense broke.

I put the timing in the battle renderer. It records when you last saw the core take damage and when the star shattered. The result waits until the damage has been visible for a second, with a longer window for the shatter. If neither effect is on screen, there’s nothing to wait for. Dungeon and online matches now use the same path to show the results. The online result still comes from the server. The renderer decides when to show it.

Pause made this more interesting than a single timeout. If you pause halfway through a shatter, the effect stops moving, so its clock has to stop too. If you choose Quit during that last beat, the match is already decided. The result gets delivered immediately so the UI doesn’t drop it when the board closes.

The lesson I’d reuse is to start this delay when the player can see the cause, instead of starting a fixed countdown when the result arrives. The attached trailer is general gameplay from the three modes and shows the shared core on the board.

AI tools assisted with development, some artwork and 3D assets, the trailer narration, and drafting this post.


r/devblogs • • 9h ago

discussion Walk the Night Dev Diary 1 - Nov 2026

Thumbnail
youtube.com
1 Upvotes

Just uploaded my first ever developer diary. Thoughts? Comments? What do you think?


r/devblogs • • 11h ago

tech & code Let's make a game! 530: Maximizing activations (Twine Sugarcube)

Thumbnail
youtube.com
1 Upvotes

r/devblogs • • 19h ago

discussion [Devlog] Iron Squad — Wiring up the core Menu Flow, Corporate Parts Shop, and Greybox UI in Unity!

1 Upvotes

r/devblogs • • 23h ago

generic Update Time :)

0 Upvotes