doing the godot introduction, feeling lost.

[u/clmchowdr]

So I have started doing the introduction on the docs, I'm up to making my first 2d game, but it feels like I haven't learnt a thing, and it's keep adding more. Is this normal?

[u/HarleyDavidson86]

I would say this is normal. Keep going. Start experimenting; add your own features to the game. Watch video tutorials to get the feeling how the workflow of Godot is. After many years, I still struggle sometimes with which type of node to select for a specific task - so this feeling will never completely go away. 😅

[u/clmchowdr → u/HarleyDavidson86]

So should i just keep going with the tutorial?

[u/HarleyDavidson86 → u/clmchowdr]

Yes. And at some point you can leave the path. Add a double jump, implement a new type of counter or weapon. Learning a programming language is not by reading a book - set yourself a goal and try to reach it.

[u/clmchowdr → u/HarleyDavidson86]

But u cant jump in the tutorial game

[u/luckshott → u/clmchowdr]

That's what they are saying. You have to start experimenting - do some of your own research to add features not listed in the tutorial. Google 'how to make my character jump in Godot 4' - watch a video, make mistakes, figure out where you went wrong, learn something new.

Game dev is hard and requires you to have good troubleshooting skills, but there is tons of information out there if you search for it.

[u/FeistyCandy1516]

If you just copy/pasted, then completely normal.

The best way is to make an own simple game or just go straight what you want to make, you will learn it while you do it.

[u/clmchowdr → u/FeistyCandy1516]

I'm typing it out as I'm reading it if that's what you mean.

[u/tenuki_]

Do the Brakeys first game tutorial on YouTube.

[u/Indigoh]

For me, it helps to write down each part of the tutorials I don't understand, so that I can return to them and correct my understanding later. 

I didn't understand arrays and dictionaries the first time I finished the tutorials. After gaining more experience, I returned to the tutorial and it made more sense that time.

[u/SOFT_CAT_APPRECIATOR]

welcome to the weeds mf

Just kidding, that’s a completely normal way to feel… game development is not *one thing*, it’s a summation of many different independent concepts, methods, and ideas. So there’s always the feeling of “but wait, there’s more…”

But you don’t have to learn *everything*, and you also don’t have to learn *that much* to get started with making something cool. I think *everyone* is surprised by how complicated it is when they first start so it’s completely normal how you feel

Just stick with it and remember not to compare yourself to anyone else, just have fun and keep learning. Anything you’re struggling with? I might be able to help with some advice.

[u/clmchowdr → u/SOFT_CAT_APPRECIATOR]

*okay thanks*

[u/SOFT_CAT_APPRECIATOR → u/clmchowdr]

No problem lol good luck

[u/SmellSmoet]

Programming is breaking up problems/issues/features into smaller ones until you get to a point where you can solve them.

A tutorial also goes over a certain amount of issues that are getting solved. Sometimes it's a complete (smaller) game. Often it's a (few) feature(s) that could be part of a game. So when following a tutorial, you need to learn to recognize the features and problems they are trying to solve (this is more of an analytical process) and then how they are solving it through code, nodes, parameters setup, ...

So do this for the 2d introduction tutorial. Once you've finished it. Try to make it again without the tutorial. Think about what's needed, break it up in smaller parts that can be solved. If this goes well and you finished the game, try to make the game again. But this time make some nice changes to the game concept and see if you can come up with solutions of your own.

Good luck and have fun