When i started this group I thought i was gonna have time to do all the things I had promised in my mind, play everyone's games and spend time giving feedback left and right, but thats not the way it happened, I have lots of things going on in life, and skool kind of became just an extra pressure. From the beginning I wanted to try this as an experiment and im glad Ive gotten to see everyone's stuff, and im still deciding what I want to do with this space if anything. But time is a factor, making games is and is going to continue being my priority as far as game development goes and its just where my heart truly is, im glad I've tried to make a community here and im glad I got to meet all yall. If you want to keep posting your games here, for now I'll keep this all up, if I decide to close down the community I'll let yall know, and I'll likely just rephrase the discord to be a place where yall can continue posting game progress and all that. Thanks for all your time you spent here!

Dream games can be a bit of controversial topic at times, cause they do come with big scope and at times it might be too difficult to ever do aka making and mmo by yourself 🫠 But I think its fun to think about and share what your dream game could be, I have a few, but I would love to hear what you guys have thought up!

Who is working on a board game?! I am a board game designer working on a game right now called Cozy Lighthouse Keeper!

Im sure ive almost heard everybodies, but I wanted to kind of formalize it here! Mine is Godot, ive been using it from the beginning, but im starting to explore other means of making games, been learning a bit of javascript recently. Anyways whats your favorite? or What do you feel most comfortable with! 🤔

The best way to become a good programmer is to become good at debugging. When you build complex systems, eventually you will run into bugs that are nearly impossible to reproduce. Sometimes it's not our code — the bug is baked into the dev platform we are using and there is nothing we can do about it. Users will occasionally run into the bug ,but we won't be able to reproduce it. So how do you fix a bug that you can't reproduce yourself? We use an approach I call Catch and Correct. First, we identify the symptoms of the bug — as reported by our users and through our deeper investigation. Then we add code that looks for those symptoms and corrects the problem while it happens in real time. Since we can't fix the bug itself, we fix the consequences of the bug so that the user can continue playing — perhaps without even knowing that something happened.