Organizing class functions

I have a new style to organize class member functions. Previously I organized them more or less by "theme", but now I have changed that and it goes like this: first getters (all functions are in alphabetical order), then setters and last three parts are display, debug and save/load routines. I think for some people the order of functions doesn't matter, but in a large project it's nice to have some kind of rules for that, too. Makes it easier to understand the workings of the class. It's a matter of personal preference, but I think this kind of ordering works quite nicely.

My next focus is Teemu and I have returned to the project just by re-organizing classes and also checking out private/public interfaces, I often place functions to public even they could be in the private part.

I have also an update to my health problem. When I got my blood checked they found out that I have hypothyroidism or the low function of thyroid. So I have been getting thyroxin for that and it has been interesting. It's likely that I had the condition for years, because the difference in my health has been quite dramatic. But on the flipside it has caused insomnia, although the quality of my sleep has increased so much that it hardly matters. As a result of all this I have been able to put more work on my projects without suffering from brain fog I had before. Yet I have a feeling that it's not over, that there is something else wrong with my health. But I'm not worried about something I don't know, I have enough actual problems in my life.

The idea I had from a dream

I saw a strange dream and realized it could be a game idea. Everyone and their dog has ideas, but this one is really good, I think. Obviously not going to tell what the idea is, but have a strong feeling this is going to be my next game project. I did already have a plan to create more traditional role-playing game rather than yet another roguelike and this is it, this is the idea for that game.

Teemu's level generation is more or less ready, after I guess 12 years of development. But it's only for the physical "topology" of levels. Game object generation is next on the todo list and then the game should be ready, that's how roguelike development works. I hope Teemu 1.3 is released even within this year, or early 2023.

I have health problems, but I don't yet know what it is. I'm trying to get into health care, but it has been weirdly difficult, because we have (I live in a small village, everyone from one knows what I'm talking about) a strange doctor (sadly, not Doctor Strange) who thinks diagnosing a patient is not that important. I know something is wrong, just have to find out what it is. If it's fatal I don't want my projects to end up in the hands of woke developers, let's get that out of the way first. I want roguelikes that have more features, not less.

Then we have the energy crisis, and we could even have a war. Fun times.

The project cycle

Lately my development "cycle" for each project has been exactly five days. I'm focusing on one project for five days and then I'm done. It's enough time to get some feature implemented and then sign off for a while. Seems to work quite well.

At the moment I'm working on 6 projects which may seem like too much, but I like it. They are all different, some of them are old roguelikes which are more or less "ready" as games, but I had an idea to make a modern version from them. The rest of the projects are Brick Atelier, Teemu and Kaduria.

In couple of months my current and long-time homepage provider is quitting so I need to figure out how to set up a new homepage. I think it'll become better than the current one, I try to find a "professional" provider so the pages will have better chance to work properly. Some people were complaining that they can't even visit my homepages for whatever reason.

Most of my projects are literally 95% ready so there will be releases "soon". I know I'm playing a long game with my releases, but that's how it is sometimes.