That was a very interesting read! Thank you for posting it here! I really enjoyed it.

@ReMikeAble@beehaw.org Thanks for your encouraging comment! (I can’t reply directly because it doesn’t load on my instance for some reason), but I remembered I could just leave a general comment and a mention. I really appreciate the kind words~

I found your post on Beehaw originally, but for some strange reason couldn’t get the post to load while logged in to comment, so here it goes!

I really liked the subtle world-building you included, it was perfect. I think the overall write up was really well done. Calling humans mayflies was muah! And the whole story gave me a nice little chuckle. Good job!

Does !comics@lemmy.ml work for that?

Well, Unity had a lot of unfinished packages that they suggest you use, and then depreciated the packages that they had already, and it seemed like a huge mess. Unity also took forever to load, - so I prefer the ‘just works’ of Godot features, and the fact that it’s lightweight and quick to load.

Since it hasn’t been mentioned yet: since you’re absolutely new to coding, if you choose Godot start with 3.5 version. 4 is new and shiny, but that means that there isn’t as many guides and tutorials. There’s also some changes from 3.5 that will make it hard to follow old tutorials. And some of the better changes are being backported to 3 anyway.
Once you’ve got a decent understanding of 3.5 you could upgrade to 4 for the quality of life features. And you will have to adjust to the changes, but there aren’t as many resources for 4, especially for completely new coders as there are for 3. There are kidscancode and GDQuest - there are also plenty of YouTube tutorials for Godot 3.5.

I believe Material Maker uses Godot and I believe I’ve seen a couple of other things too! I’ve debated it by my desire to make non-game projects is slim. However, if I needed to make a program I’d probably use Godot because I love the UI system and it just makes things a bit easy compared to Python and Tkinter 😆

Well. This could be a lot of different things. What do you think is making you quit?
There is a dopamine hit for an unexplored idea. People essentially get very excited about an idea, like the dopamine, and then when it starts to fade as they have to actually implement things they quit. Sometimes. They manage to get some things down and those small successes of implementing mechanics gives them the dopamine to continue - until they hit a big enough road block. (Guilty!). Working on a game is more about discipline. Not feel good emotions. If you’ve never created a game before create a small project idea, and work on completing it. Even if you don’t feel motivated.
Motivation doesn’t usually last a whole project. But doing it for the sake of doing it will. After you have a small project break it down into bite sized pieces that you can check off from a to-do list (if that works for you). And Don’t burn yourself out on it, but try to enjoy the journey, and keep that finished game goal in mind and look forward to it knowing it just takes overcoming small hurdles repeatedly.
This is harder than it sounds, and maybe it won’t work for you, but it is one way to tackle the problem of completing a project.