I just wrote a post on this -> https://randysworkshop.substack.com/p/game-idea-generation This process has evolved since the video I made for the scuffed course (this one). In there, I really just jumped on the first thing that came to mind, which was a bad idea. Spending wayyyy longer on this process and really diving into fleshing out a few different ideas is key.

This was done in Jai so we could move a bit quicker. But the fundamental ooga booga principles still apply. @Charlie Malmqvist and I are working on a full Steam release now for the next few weeks. I'll bring back the lessons learnt once I'm done, until then, I'm in grind mode 🫡

https://www.fmod.com/download Example helpers for using FMOD -> game1/fmod_sound.c Learn FMOD via this playlist

I asked this in the last Q&A and got a couple of breadcrumbs and spent a few mins exploring this today. @Charlie Malmqvist suggested adding a '-mwindows' flag to the compiler. This works when you launch the program through VSCode but unfortunately doesn't when you run the exe from a file explorer or the desktop for example. I asked the AI and used the GoogleFu and I think I came to the conclusion that because oogabooga is by default a console app and not a windows gui app the -mwindows flag doesn't work. I tried adding a manifest file to the compiler as well as a bunch of other flags to no avail (I could be doing this wrong lol). I think basically you just need to make the exe a windows gui app by running WinMain() instead of main(). I didn't spend the time to work out how to change this in the oogabooga files but did come across a hack. Add something like this to your code - It's Windows specific so be aware of that. HANDLE hConsole = GetConsoleWindow(); if (hConsole != NULL) { ShowWindow(hConsole, SW_HIDE); } The console window will spawn but will quickly be minimized and then disappear. I believe if the program was using WinMain() you could use the -mwindows flag on your release build and -mconsole on your debug build and things would be sweet but I am not really sure. There might be other reasons to not use WinMain() that I have no idea about. If anyone has any better solutions. Please let me know! Cheers Bell

What we're trying to teach goes against what most of you have learned. To unlearn something you've always been told is right, is not easy. Me and @Thomas Randall has gone through the exact same transformation when we started out programming. It's going to be hard, and in the end it's all about training a "brain muscle" the exact same way you have to put in reps at the gym to gain real muscles. (This is why we are programming in C, you are forced to just solve the problem with a very simple and noiseless tool). However, there are some terrific and inspirational resources out there that helped me a great deal when breaking free from a terrible mindset for programming, which I highly recommend for anyone who hasn't seen it before: