What do you do if you're facing technical glitches while developing a game?

I tend to want to write tests whenever possible. There are, of course, many situations where this isn't really possible in game code, but to the extent that you can, it's always best to find a "minimal repro", which typically involves either starting from scratch and adding components from your game until you see the glitch, or else copying your game project and stripping things out until you have the smallest version of the bug you can manage. Once you have a minimal repro in place, you can be reasonably sure that you can validate whether any fix you make actually works.

The first and most important part of solving a problem is understanding what is going on, or at least having a good 80% grasp of the "what/why". If you make that single step, congrats you're at 50% of solving it. After this, you can get a good direction using your logic. Make sure to use keywords in your Google search for other similar problems on the internet, or using ChatGPT/Bing, I've been able to get hints and solve problems again, using keywords and common sense (which sometimes is not that common).

If you find solving the problem too difficult, first of all: Don't panic. If you do, you take irrational decisions, or worse, abort the mission. I strongly suggest checking the list of basic requirements: Very often, the issue arises at a fundamental level, such as incompatible deployment, incorrect version compatibility, or outdated frameworks or libraries. Remember to refer back to the manual.

It's all about timing. Sometimes, a quick 30-minute Google/AI search can offer immediate hints (remember, understanding the problem means half the solution). Yet, under tight deadlines, seeking help in forums, chats, support sites, Slack/Reddit/Discord groups, etc., is best. Here's a tip: Take your time to elaborate and provide detailed information about your problem. The more data you offer, what you've tried, versions used, deployment details, the better help you'll receive. Asking more and providing high-quality information yields quicker and better assistance.

Incorporating testing into every iteration is essential to prevent the emergence of critical bugs in later stages of development. Starting with Test-Driven Development (TDD) ensures that your codebase is robust and minimizes the likelihood of future issues. Additionally, integrating both automated and manual testing into the final phase of each sprint guarantees that your game functions smoothly across various scenarios. This comprehensive approach to testing not only enhances the quality of the game but also streamlines the development workflow.

I tend to share to my teammates and friends that are writing codes in just "workable" way without any design which is terrible when your application has to be long run. One thing that I prefer the most are is the system can run independently. This is important when you making tools, game features or any other plugins etc and would definitely help you when you faced issue/bugs.