How? Blood, sweat and tears mostly.

Usually it’s not recommended to start with your “dream game”. Pick an engine (I like Godot), grab some Kenney art assets, and get to work on a pong or snake clone. This can be using written tutorials, videos, or hard mode, read the docs and piece it together.

Trying to learn a language, learn an engine, learn the art pipeline, learn game dev concepts AND dream up a new game concept with custom assets simultaneously is trying to boil the ocean. Start small: add a start menu, add a scene. Make jpg appear and move using player input, add an obstacle, add a death scene/restart. Iterate from there.

Passion project “dev”.

Mechanics first. Placeholder template for what you need for visuals. There’re also free assets for that if you want to avoid your own altogether.

Sound is a set all on its own, so I would save that for the near-mid to near-end point (before finishing touches). That is to say, don’t think about it for a while.

Others have said, but take it like a cake. One piece at a time ;)

A gamedev I know who has a currently running online MMO says:

"Don’t overthink it. When I learned gamedev I learned how to display something on the screen, I learned how to move things on a screen, how to play sound effects and music, and then rolled it all together to make a simple pong game. If you can make that you can scale up from there. Buy an asset pack off of itch.io for whatever genre you want to make. "

For context this guy made his engine from scratch.

Most solo devs don’t do everything. They download packages of meshes (3d objects) to… Not reinvent the wheel.

You can, in most game dev studios, develop game logic, maps, textures, meshes, characters etc.

People can buy them, use them, modify them, etc.

That’s not to say none do. Just… The same ones don’t.

Then there’s the issue of like… Youre building in Unreal, and you want a portal that when you enter, you shrink my 10%. Okay that’s… That’s not in the engine. So. Yeah. The wheel you’re reinventing here is pretty big.

Idk if this fully elucidates. I’m in mobile and at work, hope this makes sense.

Everyone has their own process, but I think it’s fine to just start with a simple idea that’s not yet a game, jump in, and experiment around, especially if you’re just starting out. I’m not an expert by any means, but I managed to release a small game of my own recently, and all I had at the start was a test where I could knock over a box by throwing a ball. Everything else that eventually became the game were ideas that I had later while playing around and showing it to other people.

Either you learn how to make the assets, use free ones, buy them or commission someone.

Hard to believe, because it’s such a high quality product. But every asset used in Diarrhea 4 was free. Apart from the fart noises. Those were made entirely by me.

Hey, I’m also a software developer, and I dabble in game dev.

You eat an elephant one bite at a time. You’re probably already familiar with Agile, and that’s a good way to organize your project. Start small, get one thing working, and then you can iteratively add features.

If you’re interested in game design, you may want to do some reading on the subject. The Onion model for game design is highly effective. You start with a core feature, finish that feature, then add new layers by adding new features. You complete each feature before you start on the next, and this way you always have a working game. It’s fairly similar to Vertical Slices in Agile development.

As far as choosing an engine, I’ll make it easy for you and just recommend Godot. It’s FOSS and widely used in particular by solo devs. I’ve also dabbled with Unity and Unreal, which will be the other major free (but proprietary) options. Unity has less ramp-up time than Unreal, but it also has a history of screwing with its users. You’re probably familiar with vendor-lock, and that’s what you’ll be getting into if you try either of those.

You may already have the skills to build your own engine. Don’t. You’ll pull your hair out on all the edge cases and abstractions, and an off-the-shelf engine already has that figured out for you.

As far as learning to use the software, I guess that depends on your learning style. There’s books, videos, and official documentation on the web for whatever engine you decide to use. I’d recommend you use the same approach as learning any other new stack or library. For me, that often means going to the documentation’s Getting Started page and just playing around.

As you mentioned, tutorial hell is real. Don’t get me wrong, tutorials are a great way to learn the engine’s features that you aren’t already aware of. But don’t be afraid to go off-script and just play around. Sooner or later you’ll have to make your own sausage anyway.

Since you already know how to code, you’ve got a huge leg up on most beginners. The hardest part about making games is creating assets and scripting features. As far as assets go, you can certainly make them yourself, or you can outsource that work with third-party assets. While you’re learning, I’ll recommend Kenney - they’re highly regarded in the game dev community, and all of their assets are CC0 licensed so you’re free to use them even without attribution.

Good luck!

The process of making a game on your own involves failing to make the first 10 games you try to make on your own.

Ultimately, it sounds like you already have a good handle on everything that goes into it, and are just hoping to hear it’s not actually as hard as you think it is… it is hard. Know that going in, and assess if you will be able to do it. But give yourself a bit of benefit, getting most of the way tends to increase your resiliance to the final hurdles.

Just like anything else, one chunk at a time.

You can start with a story and build the game off of that, or you can start with the gameplay and build up from there.

Sometimes you just have to start, and see where it goes. Pick an engine and start building something, don’t be afraid to throw it all out and start over from what you’ve learned so far. Make a game that has some of the elements you want to use and try it out, then throw it out and make a different game with other bits. Start small and work up.

The biggest problem is thinking it has to be perfect to move on to the next part.

You can commission art, or you can buy some models and just use those.

You can also just build everything from the ground up, but it would be hard to do that for your first project.

you need to start small, here is my first game for example (I’m still learning):

https://github.com/ttttux/bevy-shoot-em-up-example

Well, for someone like me who had no inkling of programming skill until I forced myself to learn, let me tell you it was HARD. Everything about my game was a learning process but I took that as a challenge to improve myself and make myself more adaptable for future projects.

To give you basically a rundown of how I’m making my game is I first started with an idea. I liked playing Paper Mario and Super Smash Bros so I decided on gameplay similar to those two. Then, I chose Unity based on a recommendation from a teacher. As I learned coding through YouTube tutorials and asking questions on forums, I started with a simple script to control a tic tac that runs around a quick map I made with primitive shapes. And from that initial prototype I added more and more things. Different mechanics, quests, etc. For art, I’m making most of it on my own since I’m an artist first thing but most I’m getting from free sites like turbo squid or the Unity Asset Store. Music and sounds I’m using temp stuff until I can get to making them.

For myself, even making a simple mechanic of controlling your cat to explore an environment is a game. Sure, it might not be GTA quality, but it’s still a game. From here you can make something more interesting. I always say that in order for something to look beautiful, first it has to look ugly. Even a beautiful butterfly has to start as a worm.

Look at the gource utility commit visualization history of some open source games.

Just ask the guy who made Axiom Berge, Thomas Happy. Or Stardew Valley creator, Eric Barone.

By starvation.

I am not even kidding, see indie game the movie.

Games are art and making art in this works comes with the sacrifice of not being able to afford anything until you by chance become popular.

One thing I’ll throw out there is while there are rare cases where a solo dev really does everything themselves, when you see a really ambitious looking result from a supposedly solo dev, it’s very likely they either contracted things out, bought/found assets, or had on and off help from people. It’s only solo in the sense it’s their vision and they get to put things together/make all the final calls on the game.

Making stuff solo is hard. I’m doing it right now and I’m purposely trying to use a lot of stock assets for art and music because the game alone is already a massive task by itself. Don’t be afraid to use what’s out there. If your game feels good to play most people will never worry about whether you hand built every blade of grass. In other words, go for as small a scope as you can, and don’t be afraid to cut corners.