r/devblogs • u/Timely_Mobile8565 • 8h ago
r/devblogs • u/vivaladav • 20h ago
community showcase Community showcase - Show us what you're working on or what you just published (week 47)
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 • u/Krilantis • 4h ago
tech & code A frozen spell passed every check, so we started breaking our own animations on purpose
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.

r/devblogs • u/starevo • 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.
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 • u/dylaninfinitus • 1d ago
tech & code How a CAD workflow turned into my first Unity asset
Hello! I'm Dylan. I work on a bunch of cool digital twin projects, and Mesh Engine came out of the CAD models I was bringing into Unity. A model could come in as thousands of separate parts. I started grouping the existing geometry by location so I could work on it a section at a time.
One decision I had to make was what to do with triangles along a cell boundary. I kept them whole and assigned each one to the cell containing its centroid. That meant the geometry could reach past the grid box, so I gave the preview both Grid Bounds and Content Bounds.
This is from the plant demo I put together. I pulled one of the generated partitions clear so you can see what comes with the tower. The two little platforms and a bit of pipework slide out with it, then the whole lot slots back into place.
r/devblogs • u/LightModeOnGames • 20h ago
tech & code A Software Engineer Tries to Get into Indie Game Development!
r/devblogs • u/SubtusStudios • 1d ago
discussion What I'm doing to make sure my third game isn't a huge flop
After two total failures with my last few games, I'm going all in to make sure this new game is a financial success. Here's how.
When diving into the development of my third game, I needed to identify the core reasons why my last two games failed. I've taken a lot of time to reflect on them, and their problems mostly came from three things:
Over scoping, and doing everything myself, which not only made the game's quality worse, but it lengthened the scope by so much that to meet the idea in my head, I'd need at least a small team of developers to help push it over the line.
Not enough playtesting. This issue always crops up amongst failed games, and it makes sense why they do. If you don't test a product, then the only reason you have to believe that it's a good product is your own word. External validation is the only way to know if an idea is worth pursuing, and to catch out the mistakes that you, as the developer, most likely won't see yourself. You either do this before the game launches, or you let all the actual players find the bugs and issues after they've spent money on your game, which results in anger, frustration, and refunds.
Finally, my marketing campaigns were basically non-existent for both my last games, which means, no matter if they were good or not, nobody knew about them, so nobody bought them.
This time around, I've outsourced my weakest skills, buying assets on FAB. I've play tested and fixed as many bugs as I can so it comes out as a polished product. And as you can see right now, I'm marketing the hell out of this game, and making sure that as many people know about Primal Nights, my new game, as I possibly can.
I'd be interested to hear your development stories too, as the best part about being an indie game developer is that we all start with the same problems, and we all go through the same steps of evolution.
If you are interested in checking out my new game, which is basically FNAF but dinosaurs, then here's the steam link to check out the page!:
Thanks for reading!
r/devblogs • u/apeloverage • 1d ago
tech & code Let's make a game! 531: How many rolls? (Twine Sugarcube)
r/devblogs • u/SeMiSo2309 • 1d ago
generic PUBG Lite DEVLOG #12 - Level editor showcase!
r/devblogs • u/atman_studio • 1d ago
design We cut our force meter from two bars to one (devlog #03)
Hi all! This is the third devlog of our roguelike deckbuilder where office fights are ping pong matches.
Our first force meter had two bars but was hard to understand what was going on, so we simplified it into one. The bar now goes back and forth during a rally. We also added: saves that let you resume mid match (boss phases included), bosses with multiple phases and dialogue, drag and drop for cards, and the first Android build.
Happy to answer questions if you’re curious about any of it.
r/devblogs • u/juliorain • 1d ago
marketing Project Crimson Development Update: January 31 Build Target, Community Memberships Opening Wednesday
Following the discussion on my previous thread in r/gamedev, I wanted to share an actual update on what I’ve been working on. For context, I’ve spent nearly five years developing games independently through Greatsword Games Studio. One of those projects is Project Crimson, an ambitious multiplayer RPG built in Unreal Engine.
Development hasn’t been a straight line. Project Crimson was actively developed for several years, but eventually I hit some difficult technical problems involving multiplayer replication, gameplay systems, and networking architecture. I also had other projects and professional responsibilities competing for my time, and development slowed considerably.
At one point, I stepped away from the project rather than continue fighting problems I couldn’t resolve. The funny thing is that an older gameplay demonstration has been sitting on my company’s youtube channel for almost two years:
The project didn’t disappear. The work didn’t disappear. But development did lose momentum and the development footage was apparently lost. Recently, I returned to Unreal Engine, revisited the architecture, and started working through problems that had previously stopped development.
I’ve since made progress on several systems, including:
- Multiplayer ability activation and server-side spawning.
- Replicated gameplay effects.
- Casting state and UI synchronization.
- Player character and gameplay state management.
- Multiplayer combat functionality.
This has been a useful opportunity to revisit the project with fresh eyes and address architectural problems that were difficult to untangle previously.
So what's happening next?
I’m changing the immediate objective. Rather than trying to finish an entire MMO with the resources of a solo independent developer, I’m working toward a smaller, playable engineering showcase that demonstrates the systems I’ve already implemented.
Current target: January 31, 2027.
The goal is to provide a playable development build where interested players can explore existing gameplay systems, test multiplayer functionality, and help identify problems.
This is not a promise of a finished MMO or commercial release. It’s a development milestone.
Community memberships opens Wednesday, November 18
I’m also finishing the infrastructure for community participation through the Greatsword Games website.
Starting Wednesday, players will be able to register for Project Crimson’s community in the late afternoon EST.
The planned structure includes:
Free Tester Registration
Access to available playtest builds.
Public development updates.
Bug reporting and community announcements.
Development Supporter — $4.99/month
Everything in the free tier.
Access to a dedicated supporter feedback community.
More direct development discussions.
Additional behind-the-scenes updates and opportunities to participate in structured feedback.
The goal is to create a sustainable way for interested players to follow development and participate as the project evolves.
I want to be transparent about something: Project Crimson is currently maintained by one developer. This is an early development environment, not a staffed live-service operation. Players should expect bugs, server instability, interruptions, and delays in support responses.
let's be real here; I'd rather establish realistic expectations than pretend otherwise.
Website:
https://www.greatswordgames.com/
Why I’m sharing this
My previous discussion thread raised questions about how independent development experience is evaluated by the industry.
I’m on the autism spectrum and have ADHD, and I’ve struggled considerably with putting my work in front of people because of my fear of overwhelmingly negative community responses.
Over time, I’ve found myself repeatedly treated as an “ideas person.” Some of that is admittedly my own doing. I’ve been so apprehensive about criticism that I’ve sometimes struggled to properly showcase, explain, and advocate for the work I’ve actually completed.
I want to change that.
I’m not asking anyone to take my word for what I’ve built. I want people to be able to experience it, inspect the systems, and evaluate the work for themselves.
There’s still plenty to do, and January 31 is an ambitious target. But for the first time in a while, Project Crimson has a concrete development milestone and a path toward getting the work back into players’ hands.
Thanks to everyone who participated in the previous discussion. The feedback, disagreements, and encouragement have all given me plenty to think about.
Back to building.
— Greatsword Games Studio
r/devblogs • u/Siaale • 1d ago
generic This is my first devlog! What do you think?
I released my first development diary on YouTube.
https://www.youtube.com/watch?v=Q-5MTBS50Zc
To be more precise, it's not really a full development diary. It's more of an introduction video, so viewers can understand who I am and what I'm all about.
My English isn't very good, so the video is in my native language with English subtitles. But for those who don't like reading subtitles, don't want to read them, or don't have the opportunity to read them, there's also an English audio track with an AI voice-over.
I understand that many people don't like AI, but what other options do I have? I'm still learning how to pronounce English words correctly. :)
Besides, the AI voice-over actually uses a cloned version of my own voice and even tries to preserve my intonation. I spent $10 on it, which, unfortunately, is quite a lot of money for me right now.
Anyway, watch whichever version is more convenient for you: the original audio with subtitles or the English AI voice-over.
I'll be happy if you watch it and leave some feedback!
r/devblogs • u/BookkeeperUseful4908 • 1d ago
design Designing a once-per-life transformation system for Touhou: Heartbound
I wanted choosing a race in Touhou: Heartbound to feel like a decision you make after living in Gensokyo for a while. You start human, and completing a transformation rite spends the one change you get in that life. The human path can still grow without spending it.
The design problem was making that commitment feel fair. The Race Book lets you see the requirements early, and pinning a route puts the next missing step beside the clock. I wanted players to be able to compare paths before committing, even when two routes ask for very different things.
This clip shows the kitsune rite. The basic Race Book and transformation scenes are already in the game. The illustrated book, the new rite confirmation, and parts of the race-specific art are still in development. All 66 races are defined in the data, with art and powers being added race by race.
What would you want to know about a path before making a permanent choice?
Written devlog: https://touhou-heartbound.blogspot.com/2026/11/touhou-heartbound-devlog-8-who-will-you.html
r/devblogs • u/Timely_Mobile8565 • 1d ago
marketing Kernel Kingdoms 2.17: everything new since the beta (Ascension, 20 dungeons, 3 expansions, a player-run market)
r/devblogs • u/FreshyMaxy • 1d ago
design Devblog mid Nov 2026, also sort of realily check. check, check, check.
reddit.comr/devblogs • u/MaxKarabin • 2d ago
generic Armies of Kingdoms: Autobattler - Update 0.7: graphics optimizations
r/devblogs • u/dymy2k • 2d ago
tech & code Curso de OpenGL (Episodio 1) - Configuración de la API en Visual Studio.
r/devblogs • u/nklbdev • 2d ago
generic 10 frames from graybox to Godot: an alternate 1990s America after a catastrophe
r/devblogs • u/kernet • 2d ago
design Keeping the last hit visible before the results screen
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 • u/Mr_Poopy_Stockhole • 2d ago
discussion Walk the Night Dev Diary 1 - Nov 2026
Just uploaded my first ever developer diary. Thoughts? Comments? What do you think?
r/devblogs • u/BookkeeperUseful4908 • 2d ago
design How I repainted the same shrine for four seasons in Touhou: Heartbound
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 • u/apeloverage • 2d ago
tech & code Let's make a game! 530: Maximizing activations (Twine Sugarcube)
r/devblogs • u/SingleDogGames • 2d ago