r/devblogs • • May 13 '26

We Quit Our Jobs to Make an Indie Game

Thumbnail
youtube.com
79 Upvotes

About a year ago, my husband and I left our jobs at a company called Creative Assembly with a hair brained idea to try building a survival game set during Arctic expeditions in the early 1900s. Perfect time to make a game studio right folks? But industry be damned, we're going to give this game dev thing a shot.

Neither of us have done anything remotely close to this before, we had no coding experience, no game design experience. We’re just concept artists… we’re good with crayons I guess?

Would love feedback from other devs. Especially on whether the game’s direction and tone come across clearly.

Also happy to answer questions about the game or the development process. Still feels surreal that a whole year has gone by.


r/devblogs • • Dec 05 '25

A playtest destroyed 8 months of work. Thank you.❤️

70 Upvotes

Hey everyone!

We’re a small studio called Parallel Minds, and we just published a devlog about a tough but transformative moment in our journey: a playtest that forced us to cut a project after 8 months of work.

In the article, we break down what went wrong, what we learned, and how it ultimately pushed us toward building something better. If you're interested in honest behind-the-scenes dev stories, you might enjoy this one.

👉 Read the devlog here:
https://devlog.parallel-minds.studio/a-playtest-destroyed-8-months-of-work-thank-you/

Would love to hear your thoughts or similar experiences!


r/devblogs • • Jun 05 '23

/r/devblogs will go dark on June 12 to protest reddit killing 3rd party apps

Post image
67 Upvotes

r/devblogs • • Aug 27 '19

I’m working on a Metroidvania-inspired claymation game. I recently finished a proof-of-concept room.

Thumbnail
youtu.be
66 Upvotes

r/devblogs • • Dec 31 '25

An MMORPG for Those Who Miss the Old Days, but No Longer Have Time to Play

Thumbnail
gallery
63 Upvotes

We’re a group of four “retired” MMO veterans and busy adults (read: 30+ and dads) who got tired of how hard it is to organize group play with packed adult lives - while still absolutely loving the genre. So we decided to do something just as crazy as it is ambitious: build our own MMORPG.

How does it work?
You automate your character’s behavior and send them into a world filled with other players. You can actively fine-tune the automation and your build, keep the game running on a second screen… or simply close the device. Your heroes persist in an open world, where they autonomously gather resources, craft, and fight - 24/7.

Players can give orders and talk to their characters from their phones using natural language - via text or voice. Heroes develop personalities based on their in-game experiences, and you can feel it in the way they communicate with you, with voice-overs powered by ElevenLabs (think: Tamagotchi for gamers!).

We’ve combined idle mechanics with classic MMO roles (tank, healer, DPS), with a strong focus on asynchronous cooperation. The game is fully automated, giving everyone equal 24/7 access - no pay-to-win and no play-more-to-win.

Please remember to share your feedback on our Community in the #bugs-and-feedback channel - it helps us a ton in shaping the game and pushing it to its full potential!
Join us here: dominusautoma.com

If you’d like to play, just message @tom on Discord - he’ll send you a steam key as soon as possible.

P.S. Three very important things:

- This is an early version of the game.

- This is an offline build - we’re currently testing core mechanics; online features will come later.

- AI communication with your hero is temporarily disabled - it will be publicly tested at a later stage.


r/devblogs • • Dec 22 '25

I Analyzed Screenshots From 10,000 Steam Games

59 Upvotes

I downloaded screenshots from 10,000 Steam games and used a neural network to build a map where games that look alike cluster together. I then explored this map using game metadata like review counts, prices, and genres, looking for any patterns that emerge from visuals alone. If you’re interested, you can check out my findings and all the details on the project in this video I made. Hope you like it and let me know if you have any questions 🙂


r/devblogs • • Mar 23 '21

Docking experiments. Space shuttle

Thumbnail
reddit.com
59 Upvotes

r/devblogs • • May 29 '23

From the humble beginnings of the original Doodle God to the massive and complex Doodle God Universe!

58 Upvotes

Once upon a time, back in 2010, the small team of developers had a simple idea for a game - a puzzle game that let players combine elements to create new ones. This was the birth of the original Doodle God. And up until now, we are fully committed to the genre that we've been working on for years, but now we're coming with something even bigger - Doodle God Universe! We've taken all the elements that you love from the original series and expanded it to create an even more immersive experience.

At the time, our Doodle God was a small, browser-based title that quickly gained popularity due to its addictive gameplay and unique concept. Players loved the idea of starting with just a few basic elements and gradually unlocking more complex ones through experimentation!

As we continued to develop the game, we began to realize the potential for expansion. We wanted to create games that were bigger, more complex, and more engaging for players, with different styles.

In 2012, we released Doodle Devil, which added a darker twist to the original game, allowing players to create evil creatures and wreak havoc on the world. This was followed by Doodle Farm, which focused on creating various animals and plants.

Over the years, our team continued to refine and expand on the original Doodle God concept, releasing new titles that explored different themes and added new gameplay mechanics. We released Doodle Kingdom in 2014, which allowed players to build and rule their own medieval kingdoms, and Doodle God Blitz in 2015, a fast-paced version of the original game.

At some point we decided to bring all of these elements together into one ultimate game - Doodle God Universe. This game will feature all of the elements from the previous titles, as well as new ones and an expanded storyline.

The development process for Doodle God Universe is a massive undertaking. And we are proud to say, that Doodle God Universe will be released in 2023! The game will include over 400 unique elements and 700+ unique reactions you will spend hours philosophically pondering, as you try to reverse-engineer millions of years of evolution!

The game will show all the beautiful details of the creation along the way, with the help of 200+ 3D-animated scenes. The coolest thing is that players will be able to walk around the Universe, examining every corner of it!

We are excited to get the feedback from you, hopefully you will like what we have prepared for you

https://store.steampowered.com/app/1697770/Doodle_God_Universe/?utm_source=Reddit&utm_campaign=blog2905


r/devblogs • • Feb 09 '21

I recorded my life with camera glasses for an entire year and made a VR app that lets me explore my memories in a beautiful memory palace! Each sphere is a 10 second memory :)

55 Upvotes

r/devblogs • • Jun 13 '20

Small snippet from my latest RPG game devlog! Relatable?

54 Upvotes

r/devblogs • • Nov 12 '18

Here's some WIP AI and combat/stealth mechanics! More in comments

52 Upvotes

r/devblogs • • Nov 08 '16

my own indie game studio - a recap [X-Post from /r/gaming]

Thumbnail
imgur.com
51 Upvotes

r/devblogs • • May 19 '15

We're creating games on our free time. Here's how we feel about it.

Thumbnail
mysweetwhomp.fr
50 Upvotes

r/devblogs • • Jun 13 '22

Basics of Allocating and Using Memory

48 Upvotes

I wrote a blog post explaining concepts about managing memory in a way I wish someone explained them to me a long time ago.


r/devblogs • • Jan 12 '20

Demo of manufacturing automation in Mechanica. Also wrote my first blog post at deimosinteractive.com/blog

48 Upvotes

r/devblogs • • Mar 24 '19

I started making an API for Nintendo Switch JoyCon support. This is my progress so far.

47 Upvotes

So a couple weeks ago, I was watching a MrCrayfish livestream. He was working on his Minecraft Vehicle Mod and added controller support but wanted to expand upon that by making an API that other mod developers could use (Controllables API). I thought about how Nintedo Switch JoyCon support would work. I looked online for an API that lets you do this. I had found a Unity C# asset package but obviously for Unity C#. I found a Java API, which is what Minecraft mods call for, but looking through the API I found that it's quite messy, hard to read, not very thread-safe (in terms of high-quality JoyCon support), nor did it offer a whole lot of functionalities that you could do that would be handled/managed by the API. There were lots of things you could do with the API, the problem was that it was very skeletal and barebones. I wanted an API that could manage your use of the JoyCons in a clean, efficient, and thread-safe way while still giving you all the flexibility. I started off with Java since that's what I know the most and it was originally for aiding in MrCrayfish's Controllables API. As time went on I began to understand how HID devices worked, how the JoyCon's worked, how multithreaded programming worked, and finally getting the analog stick calibration to work. I was reading through the reverse engineering notes for days and days trying to get things to work. After over a week of tinkering with things, I had finally gotten basic input to work in a thread-safe and clean way.

First what I had to do was create interfaces for taking input reports. Input reports are raw bytes structured in a particular pattern that told software how to handle the data. They always started with an id at report index 0, and contained the data for that report from index 1 to index 13. Index 14 had a subcommand id (for subcommand replies) and index 15 onward contained the rest of that data. This is how a standard full input report was structured. There were several subcommands that could be handled. I had to improve my interfacing to properly handle the input reports and all the different subcommands. I also had to create an output report factory for interacting with the JoyCons. This was all easy and all but what was difficult was trying to make things thread safe. I also needed to figure out how the analog sticks worked since their input is fluid and not static like the buttons. In the JoyCon's SPI flash memory is a section (or really a subsection) that contains the factory default calibration data. All the data was encoded from unsigned 16 bit integers to 8 bit bytes. All the data for the JoyCons were encoded like this. They were also in little endian so I not only had to decode them from little endian to big endian but also decode them into 16 bit unsigned integers. When I started working on the calibration I realized that I need to read from memory and then wait for the memory to come back to me. This required me having to make the current thread wait/sleep (waiting was the right thing to do since sleep didn't allow me to notify the thread that the memory had come back). In order for this to happen I had to create some delegate threads for handling input reports, this way I would have the input report thread notify the main thread that everything had come back. I had no idea how threading worked at the time so it was a learning experience.

I needed to make this thread-safe because if games are going to be using this API for proper, efficient, clean, and thread-safe JoyCon support, it needed to be thread-safe. I needed to figure out how I wanted this to work. As I was learning Java's Thread API, I was constantly struggling with understanding how it all worked. I kept running into hanging with the program but didn't understand until I looked at the threads in IntelliJ's debug panel. I had realized that I was making the main thread wait. The threads that I created were all dependent upon the main thread cause the main thread was actually a thread *group*. So making the main thread wait meant that all threads made under the main thread group also had to wait. When I came to that realization I went to make the main JoyCon class, which is a wrapper class that contained all the necessary information and methods needed to construct a usable JoyCon object, a thread. This way when I make the JoyCon thread wait for memory to come back, the entire program isn't waiting as well. So now I had a JoyCon thread, an input handling thread, and the only thing that I needed to do was have my JoyconManager class, a singleton for managing all connected JoyCons, wait for the JoyCon object to be done initializing. So I had to make a separate thread for the JoyconManager as well. Oh wait, I also need to ensure that the JoyCon object is having all of its important information initialized before it can be used. How do I do that? Not only that but I need to ensure that there are no async problems during initialization. So I had to make a thread dedicated to initialization and make the JoyCon thread wait until that init thread is finished by calling Thread#join. This made things a whole lot better cause now I can guarantee that the JoyCon class will be initialized with all the important information before it gets used. Then the JoyconManager can continue afterwards. There is a LOT of improvement to be made with this but I will do that some other time. When this all started to work I headed on over to the analog stick calibration.

The analog stick calibration data, as mentioned before, was in little endian and encoded as 8 bit bytes. The bytes were sent like this: 0x5D 0xC9 0xB2 or something like that. This is for input. It has to be decoded into two unsigned 16 bit integers for the horizontal and vertical axes. Now the calibration data itself was encoded into three groups of three bytes. When decoded it gave you the center_x, center_y, min_x, min_y, max_x, max_y variables. There was also in memory information about the deadzone. The deadzone is where the analog stick memory stops being read as input and instead gets read as 0 during the calculations. I had to decode that. I'm not gonna go into the maths involved in decoding but you can view it all here. I was struggling to get the calibration right. I had no idea why the numbers weren't coming back between 1 and -1 and 0 for the center. I was so confused. I then realized that the bitwise operators are considered mathematical operations by the JVM and return to you signed 32 bit integers every time. So I had to fight against the JVM's love for two's compliment by taking the result of every bitwise operation and doing a bitwise AND with the proper mask such as 0xF or 0xFF or 0xF0 depending on what I need. When I realized this I finally got the calibration to work. It all now reads between 1 and -1 on both the horizontal and vertical axes.

This API currently has support for reading the battery information, including the exact voltage output. I'm going to find a way to set a flag for whether the JoyCons are charging or not but since to charge the JoyCons they have to be connected to the console and on the doc, there really wouldn't be any use for this flag. This API also has memory reading capabilities, but reading memory right now isn't really a biggie but it's there if needed.

Right now I'm in the process of getting a Kotlin/Native workspace going so that I can port my API to native libraries. I'm already fluent in Kotlin so it's not gonna be as painful as having to learn an entire language on top of learning its tools and compilers and learning its libraries. Kotlin/Native will allow me to compile the API natively, and I can create bindings for different languages and platforms (such as iOS, Android Native, WASM, etc) without having to rewrite everything and have inconsistencies. I am just struggling to get the workspace to work because I have to learn how C compilers work since it uses C compilers for interop and linking native libraries together with projects.

I am looking at this project as having a lot potential honestly. I think if I do it right, there could be a lot of games out there that take JoyCon support. Not only that, but since the JoyCon's connect via bluetooth you could actually use this API for making mobiles games that have JoyCon support. With the ChromeCast or apple tv (or whatever the apple screencast is called), you could probably (no definitely) create a mobile game that you can play on a bigger screen with the JoyCons. This would obviously require the JoyCons of course but perhaps there could be a way to connect any bluetooth controller.

I'm gonna be doing occasional livestreams of my development over at my twitch channel. Once I get myself a bluetooth adapter for my desktop (I'm using my macbook for API development and it does not like to stream for whatever reason, don't really care tho (not a fan of macs tbh)) then I'll be good to go with porting my API to Kotlin/Native.


r/devblogs • • Feb 04 '21

not a devblog I made a Dog Fight Style game in a Week

45 Upvotes

r/devblogs • • Feb 15 '19

Here's some gameplay of my hobby Xcom/Darkest Dungeon project. Enjoy!

45 Upvotes

r/devblogs • • Jan 20 '19

This shows the procedural level generation algorithm we created for our latest game.

45 Upvotes

r/devblogs • • Feb 06 '21

not a devblog After roughly 2 years of development, me and the rest of the team are overjoyed to share the progress we have done during the last couple of months and finally dropping a public demo! 🐒

43 Upvotes

r/devblogs • • Jan 15 '21

How much money my indie game made in 6 months, and do Steam sales work?

43 Upvotes

r/devblogs • • Apr 21 '20

video devblog I Completed My Game (free to play + full source code)

Thumbnail
youtube.com
43 Upvotes

r/devblogs • • Jan 14 '26

An MMORPG for those who miss the good old days, but don’t have the time to commit like before (Reminder)

Thumbnail
gallery
42 Upvotes

Hey there!
I noticed that the last post was received very warmly, so I’m sharing it once again for those who might have missed it earlier 🙂

We’re a group of four “retired” MMO veterans and busy adults (read: 30+ and dads) who got tired of how hard it is to organize group play with packed adult lives - while still absolutely loving the genre. So we decided to do something just as crazy as it is ambitious: build our own MMORPG.

How does it work?
You automate your character’s behavior and send them into a world filled with other players. You can actively fine-tune the automation and your build, keep the game running on a second screen… or simply close the device. Your heroes persist in an open world, where they autonomously gather resources, craft, and fight - 24/7.

Players can give orders and talk to their characters from their phones using natural language - via text or voice. Heroes develop personalities based on their in-game experiences, and you can feel it in the way they communicate with you, with voice-overs powered by ElevenLabs (think: Tamagotchi for gamers!).

We’ve combined idle mechanics with classic MMO roles (tank, healer, DPS), with a strong focus on asynchronous cooperation. The game is fully automated, giving everyone equal 24/7 access - no pay-to-win and no play-more-to-win.

Please remember to share your feedback on our Community in the #bugs-and-feedback channel - it helps us a ton in shaping the game and pushing it to its full potential!
Join us here: dominusautoma.com

If you’d like to play, just message @tom on Discord - he’ll send you a steam key as soon as possible.

P.S. Three very important things:

- This is an early version of the game.

- This is an offline build - we’re currently testing core mechanics; online features will come later.

- AI communication with your hero is temporarily disabled - it will be publicly tested at a later stage.


r/devblogs • • Jun 15 '19

Unreal Engine Time Warp Effect: Colorful Ball

41 Upvotes

r/devblogs • • Dec 01 '16

I'm working on a game, that runs on GPU, because it's a massive physics simulation, but still works in realtime

Thumbnail
youtube.com
39 Upvotes