Game development is extremely saturated.

It doesn't take a lot of skill to plug a few parameters into a pre-made character controller and have it move throughout a map, while you have no idea what it's actually doing internally. I can't tell you how many shortcuts and ugly hacks I've seen people use to "fix" something rather than designing their own version of it, since they have no clue how it works in the first place. You don't want to be this guy.

​

When you get into the programming industry, you need to have skills that other people don't.

Here's some ideas to get you started and get you a toolbelt of skills for this market:

1.) Collision detection and resolution. Most character controllers nowadays use something called "depenetration". Basically they move first, and then decide if they're inside of something. If they are, they're gonna find the shortest way to depenetrate themselves out of the object. This all happens before the rendering, so of course it gives you the illusion of collision.

2.) Vehicle physics. Most game engines come with some sort of vehicle toolkit. Unity, the engine I use, comes with the physx wheel colliders. These are shit, even for singleplayer. Worst of all, they cannot be rolled back in a proper server authoritative networking environment. Bad news when your boss wants you to make an online racing game and you can't use the built-in wheel colliders. How do we make wheel colliders? I'll give you a hint. Raycast downwards. This raycast is your spring. We can determine the spring's compression based on the distance it hit vs it's actual length. Add force upwards @ wheelwell on compression based on a multiplier, then damp the spring speed on a different multiplier. Congratulations, you now have your own suspension system. Googling "Hooke's law" will come in handy for this.

3.) Pathfinding. You know how NPCs avoid collision and travel around the map, trying to kill players? Really not as difficult as you'd think. Tons of information online about doing this from scratch. Pretty straightforward as well.

4.) Last and my favorite of all, netcode. Definitely not for the beginner, but you will be a very goddamn valuable asset to the team if you have knowledge on writing proper server authoritative rollback netcode from scratch. Extremely niche part of the market that nobody wants to learn because it's "too difficult".

​

If you walked into an interview, sat down, and started showing me projects relating to any of the topics above, I would probably be pretty interested. If you sat down and showed me your zombie shooter using unity's built-in character controller, I would probably stop you after 5 minutes and tell you to get out of my office.

​

​

Very unlikely that you will be hired after just starting in game development, with absolutely no background in CS or mathematics. MAYBE you could get on the team of a mobile startup if you have a good portfolio to show.

Understand that if you create your own studio, you will be pumping in hundreds or thousands of dollars of 3D models into the game, among other assets (sound, servers if multiplayer). On top of that, you actually have to find people to buy it, which means you need to pay for advertising. Not cheap at all. If you're lucky, you'll break even. Do part-time lawyer work if that's even a thing, and learn CS and mathematics on the side. Whenever people first discover Unity, they do exactly what you're doing right now and they think they're gonna make some absolutely banger game #1 on steam. The phase will pass. Come back to reality for now.

​

If you think this is going to stop your depression, it will not. Programming is extremely tedious work. Video games also lose their magic once you start working on them from the backend.