Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines

When did it "click"?

A topic by a_kimb0 created Mar 14, 2022 Views: 644 Replies: 13
Viewing posts 1 to 9
(+2)

How and when did things start to make sense when you were developing games? I've participated in my first game jam this week, and I'm still following YouTube tutorials on what to do. Every time I attempt to make a game, it always ends up with me having not really learned anything, just regurgitate tutorial code. Does this take years to click? I've been doing this for about a year in bits and pieces, and not having that moment of "oh, I know exactly what I'm doing, and I could implement this feature seamlessly" hasn't hit me in any form.

Deleted 90 days ago

I see. I just feel pretty burnt out right now

Deleted 90 days ago

How have you gotten over that hump? Did you try to code something every day/week? And for practicing code did you just remake a feature over and over until you really understood it?

Deleted 90 days ago

I see, that makes sense

(+2)

Game Jams can be stressful even if you do know what you're doing. If you're getting burnt out you might want to try and make a project without a set deadline and just focus on learning the basics at a comfortable pace.

That’s actually what I have been doing, so I joined a jam so that I had a deadline to work towards. In retrospect it might’ve just been such a short time frame (only like 5 days) that it ended up causing more burnout

(+1)

Writing stuff down on a piece of paper always helps me to get a better grasp of concepts.

(+1)

Game dev never clicked for me tbh
I just do it cause sometimes it's fun or I get/got paid for it.
Otherwise, I like to just draw, help others with dev or make concepts.
Though must admit, it is satisfying to have your name in a game's credits, especially if you made it yourself.

(+1)

> Every time I attempt to make a game, it always ends up with me having not really learned anything, just regurgitate tutorial code

If I may give some advice, this likely means you're trying to make games that are too complicated. Don't be afraid to really simplify things and try to make something that is simple enough to do without looking at a tutorial, and build up from there. It won't be sexy and it'll look like slow progress, but you learn a lot more when you learn things in the right order, rather than trying to skip ahead too far and get confused.

Source: wasted many years doing things way beyond my skill level until I admitted to myself that I'm still a noob :)

A year isn't very long to learn anything, really (music, foreign languages, math...). I've been programming for over for almost forty years and I'm still learning every day. Programming was simpler back then, but even so I started out copying and pasting sample code and didn't really feel the light bulb go off over my head until I went through the programming guide for an Apple II+ and then I started to understand what's going on and the cause and effect of every line of code. And present day I still prefer to learn through text tutorials, not video, so I can go at my own pace and focus on understanding each line of code, and browse reference materials so I know where to come back if I need more info (sometimes the reference manuals are the best place to learn a language or tool).

But there's no single right approach for everyone, so you should try different approaches (and tools and types of projects) and go with what works for you. The important thing is to find a way that you enjoy and find interesting, otherwise it's hard to get motivated to put in the necessary time. Taking a break is not a bad idea. It took me a long time to find a game engine I wanted to get started with for my own projects (that was Unity back when it was version 1.5) and then after ten years I didn't want to look at Unity again, so I've just been dabbling with other game engines the past couple of years just to see what else is out there, and now I'm slowly getting into the mood to learn Godot. Along the way I've also learned there are areas I'm just not interested in, like server programming, or what constitutes AI these days, so I try to spend my time on what I like doing.

(+1)

Literally this weekend during a game jam I knew every line of code to write and barely had any errors or had to look anything up for the first time ever. It is quite a feeling, so I'd definitely say something clicked. This is of course after doing 4-5 jams a month for a while and watching hundreds of tutorials (years of coding experience too).

I'd say it also heavily depends on your planning. If you know how the mechanics you are going to code are going to work and interact with the rest of your project, you will have a much better time coding them (guessing and checking is beyond frustrating at times and usually you will just be staring at the screen erasing and re-writing the same code blocks).

Overall its like any skill and it will definitely click at some point. You have to continuously practice and learn how to do things (making one game here or there isn't going to do much for fully understanding how it all works together).

(+1)

I noticed when I plan to work on a game, it becomes a bore and nothing clicks. 

But when I do it without planning to work on anything, it feels like a fun activity rather than a chore, and everything just works!

I don't know if that helps.

I saw Robert De Niro say in an interview (I think it was an Actors Workshop episode) that if it's hard to get going because you don't feel ready or you don't feel you understand the role, then you just have to jump in and get in the flow of things.

(+1)

Makes sense.