Have you ever wanted to play god? Be merciful, vengeful, or simply watch evolution happen right in front of you? Well then, this game is for you.

Blobvolution has you watch over a small tribe of "blobs" with their own names, memories, and wants. They explore, gather resources, interact with each other, and try to survive all on their own.

And you? You have the power to kill creatures, move creatures and items, or refill their hunger and energy. You can make their lives better, worse, or simply sit back and watch what happens.

Your goal? Help the blobs discover fire, as that is the win condition after all. But how will you use your godly powers? We will see.

---

Now that we got the game description out of the way, here are some of my thoughts.

THOUGHTS TIME

Balance is shit, so here are a few small things to know:

Tools are made with wood, which blobs try to gather. With tools they can gather stone and ore. Tools also let them forage from trees, but they do this automatically.

Fire is made with ore and needs tools. The current problem is that no blob really goes and gets ore and then makes fire. So for now the game is stuck until some rando punches an ore node and gets ore... Even then, making the fire takes ages (my bad, I didn’t configure wants properly).

If you downloaded the Windows file, it has the source code. If you have a C++ compiler, you can modify and compile it yourself (feel free to), say to make the game easier or to adjust stuff. But man, the code is shit. It’s all over the place, so don’t try to make sense of it. You won’t.

But if you enjoyed this still, I’m glad. And honestly, lesson learned: don’t aim for the sun when your wings are glued together with wax, ’cause you will fall. The game was rushed by the end. The defines are all over the place, the game can’t finish ’cause blobs don’t want to mine, and it doesn’t even have sounds.

For the next game jam (if I join any), I’ll try to make a simpler game that actually works and is polished, instead of adding new and new things that break the game until it stops working altogether.

---

AI USAGE

Code. Small portions of the code were written by AI. This includes “duplicate” functions that do the same thing across several similar structs. It was also used once or twice to clean up the code and organize it for reading. Otherwise you would have define.h with the defines in random order.

Graphics. Used heavily here. Nearly all of the graphic (gfx) files were made this way to save time. My general approach was to write the functions myself and THEN have the insides filled in, instead of relying on it to give me something sensible PLUS guiding the output.

That’s all. So yes, I’ve put the AI disclosure on everything, mainly because everything was slightly touched by it. But only a few things related to the core logic of the game were changed by it. Say stuff like behavior loop which was written heavily by hand but portions of it were AI-assisted (it was messy trying to get it all to work).