As I've said in my previous post, I've given up on my game. I want to come up with an idea that I can enjoy building in the longer(ish) term.

In the meantime, I'm working on my own Godot add-on that I can use for all of my future games — an achievement system. It's going to be nothing fancy but something I'm going to find useful. I plan to put it up on Itch for other game devs to use. While I am still coming up with a new game idea, I feel good creating Merit to give me a sense of forward momentum, at the very least.

And now, to just put in the work. I've been incredibly distracted with the beautiful weather we've been having. I should be able to put an hour or two of work in throughout the week. I just have to lock tf in!

And I feel bad about it. I told myself a bad, complete game is better than no game at all. But every Sunday I dreaded having to come back to a project I wasn't really interested in since it was more of a learning experience.

I think the big mistake was choosing a game to build in Godot that I can easily create in React, a language I work with 40 hours a week. Because, essentially, Zetus is a 2D array that just checks conditions when buttons are pressed.

What I'm saying is I want to play with physics. Have things fall, bounce, and collide. Something I can't easily do in JavaScript.

So, what now?

My thoughts and ideas on Zetus are all over the place. Some on paper and others in the nooks and crannies of my head. I've recognized my hesitation to getting deep back into GDScript and Godot and it's because I do not have a concrete plan. My method of coding up the new, interesting idea I just came up with has slowed my progress to a near halt. There's too much to learn, too much to try, but not enough actual progress being made.

I've decided to take a step back and create a concrete GDD (Game Design Document) for Zetus before I dive back into coding. If I keep dilly-dallying like this I'll never get anything done. I don't care if it's a decision I may or may not use but it's a decision nonetheless and that's progress!

But first, what's a game design document? Good question because I have no idea either lmao. I have some research to do.

I regret to inform you that I have again not had a lot of time to put into this project. This entire month I expect to be unproductive due to life things but I'm still trying my best.

Here's what I've worked on:

I'm tired of calling it Untitled First Game so I'm now going to call it Zetus (zee-tis) for no particular reason. And I'm naming the protagonist Zetus Lapetus (luh-pee-tis) for no particular reason, as well.

I've also decided that I'm no longer going to prototype this game before deciding it's worth building out or not. It's my first game and I think the most important thing is to finish it. Regardless if it's good or not. I haven't seen a roguelike game like mine that has a cycling active item inventory system so at least I have that going for me.

I have no game updates.

Quick one this week. I did a lot of refactoring and created a Thing class, more commonly known as entity but I do not like saying that word as much as I do not like typing it, that the enemy and player will extend from. So far, its tree only consists of a sprite and its health points.

The monster spawns on a random open tile and does nothing. It has health but I haven't wired the attack functionality in yet. So he just sits there, menacingly.