Video

Watched your two "50 tips" videos, and learned a lot of new things. Thank you!

I've been learning Godot for a few months now....I learned SO MANY things from this video that were never mentioned in any of the tutorials I've watched. Thank you!

omg there is a CODE COMPLETE DELAY?! This has to be the worst feature ever. I cannot believe I didn’t know this!

"Stop using your mouse for these." hahahaha

I am not very good at creating video explainer but sure enough I progressively made a way to deliver a game this time.

this is super helpful. thank you <3

I could not get to work the 26. Mandatory Export script. I set exactly as you did. Even put the script in auto-load. I thought that this would warn every script I have. I think I misunderstood xD Could you provide a little more clarification on how to use this?

Really, what my solution to everything is: Step 1: get diagnosed with ADHD Step 2: take prescribed meds so I can actually focus on the things I want to do Step 3: profit

It's true, I understand a tutorial so much better when I change a few things as I go along and try to understand beyond just following each step, and combine it with what I learned in other tutorials. The animation of combining different chairs is a great way to demonstrate this. On the other hand, I also think it should be remembered that not everyone learning game development is aiming to primarily be a programmer. Things like graphics, level design, story, and music are also extremely important.

Hey! Very good advice. I do have some minor criticisms, not really directly about the advice itself (it's very good), but about some parts of the delivery. As a teacher: you *do* want to just copy at first, and telling people to try to "understand" right from the start is likely to be discouraging. Just like you can't "understand" the letters or words of a new human language or musical notes in the beginning. You just need to fill pages and pages of "mama ate the apple". One huge hurdle to get through when learning to code is being able to visually parse, and write, the esoteric and weird syntax. Learning follows a [ Copy -> Customize -> Create ] model. I prefer [ Copy -> Modify -> Remix ], but it sounds less nice; nonetheless, the principle is: you do need to mindlessly copy in the beginning. However, and that is important, *manually copy*, not copy paste. Actually writing out everything is paramount because coding, in the beginning, is almost all skill ("learn by doing"). This is not at all to detract from the points in your video, which are all very valid. Just... As a second step. It's totally fine, and necessary, to just copy. You say at the end that you had a revelation and started trying to understand. That's great, but I bet you wouldn't have been able to without the preparation in copying code before. As another, smaller caveat, I also take contention with the usage of "totally" understand, this can also provoke some anxiety in the learner. Rather, I would recommend to understand "as much as you can", and move on with the bits you don't. All programmers operate with enormous gaps of knowledge, because computers are complicated. There isn't really a qualitative difference between not being sure how scons compiles Godot and what `move_and_slide()` does, just a difference in depth. The depth to which you can go increases over time, and where you choose to stop is arbitrary. Trying to understand "everything" is an unproductive rabbit hole and will send people tumbling into weird corners of the internet. The right frame of mind is similar to the concept of flow: do what's familiar, and push the boundary *a bit*. Every time, push the boundary a little more. So, to TLDR, I would recommend people *consider* trying to understand as early as possible, but it's fine to copy. And that people *try* to understand always as much as they can, but to not get hang up when they don't. It's very similar to the advice you give, but the difference is to consider the standpoint of absolute beginners and potential cognitive overload. Everything else is on-point, good video!

Sorry but it's not an easy watch. accent and speed don't help much

me personaly, i will never use code in my games that I don't understand.

These are some great tips, but the music is definitely too loud in order for me to understand your accent. If you have a script for the video, turning it into closed captions would be a great idea!

Me, for everything irl, and everything I do, I should just accept my fate and understand why

My favorite thing is when someone is trying to do something very specific and there's one really well made tutorial that explains everything step by step and they say they already saw it and it's too much work 🥴

Thank you for this video, i pretty much understand all the mistakes a lot of people make by just following a tutorial, not learning the "why" and "how" something works etc. I'm a slow learner and using gamedev tv course to get through, bit by bit. But also learning Github at the same time, saving the project via private repository for learning version control at the same time. Fun stuff! Still a lot to learn to even make simple games, but this video gave me some perspective on how many other people are just following along and never getting anywhere. Which gave me some confidence boost. Because i already use some of the tips and tricks you said to use, without realising that it's a skill many people don't utilize. For one example, googling simple and concrete "generic" questions and to not be so specific in questioning your unique situation only you may have. I don't know how long it would take, but if the situation rises for me to want some questions or tutoring, i have saved your info abour tutoring on my digital sticky note for a reminder to my future self that i can seek you out, to maybe get some help, if needed. Thanks for getting me some perspective!

I can relate so much to this video. Learning game development has been a real struggle for me too. I'm currently working on a minimalist 2D platformer and it's been tough. I've made countless mistakes, from blindly following tutorials to not knowing how to properly troubleshoot errors. It feels like every step forward is met with two steps back. What's the one piece of advice that really turned things around for you? Your video really hits home. I appreciate how you go through the common mistakes, like not googling the right way or just accepting solutions as-is. It's encouraging to see someone else go through the same struggles and come out the other side. Thanks for sharing your experience-it's really motivating!

I'm going to bookmark this video for my repertoire of tutorials to give out in #godot-4-chat

I found my icon buddy!

Very good video! I'm really surprised this only has <2k views

I love your 50 tip videos. I'm gonna get one of your courses on Fiverr :-)

This clearly deserves more views (and all begginers should be shown this video)

Damn. You make really great analogies. It's so much easier to understand your point. Great video!

Man, I get that this is just them not having learned how to learn - which has to be remedied, ofc, but folks asking questions without as much as the bare minimum of information to go with it... oof, that's a real one. Honestly not an issue if you accommodate it, especially with LLMs being useful for quickly parsing the overall form of a Discord comment or something; just tell people to specify whether they had error messages and whatever prerequisite information we need to know. Still, it hurts seeing people do that.

This video is awesome, but damn that stuff with the cards and folders around the end looked very cool and fun to play with.

this video is so true, as a comp sci student, I can confirm that you only learn when you actual look and read what is happening in code. example, there's a game called snake, people can do it in around 150 lines of code - it took me the best part of 20 hours to get the snake to move, because I was dealing with a linkedlist, and setting veribles and pointing and moving x and y values. only use youtube tutorials if you want something to work in a project and you need it to work fast. but if you want to actually learn what is going on in a 4 loop or how to correctly deal with pointers. than you've got to put in the hard yards

Thank you for this very interesting work. though I do have one question. Why does my code not work?

I am in tutorial hell right now, you have showed me what I was doing wrong, thanks for the help :)

Great video, I'm three weeks into learning Unreal Engine. I'm lucky as I have a lot of free time on my hands but here's how I approached it and I hope it helps other aspiring devs. Tutorials can be great if they are coming from a good source. So many tutorials on youtube are incorrect, not very efficient and don't explain the HOWS & WHYS. WHY? being the most important aspect I feel. I made sure the courses I followed were from people who are in the industry and were substantial (Not just some 2hr course so they can earn a buck) Don't put pressure on your time, it's about the journey not the destination. If you have an idea in your head for a game/app, take notes on any areas you cover in the tutorials that may be relevant to your idea so you can go back to them later and have a good starting point. Week 1 - Followed a detailed and complete beginners tutorial to Unreal Engine just to familiarize myself with the basics of the engine including navigation, hotkeys, blueprint application etc... In the small segments where they used blueprints I copied initially but then adapted it a few different ways on my own to get different results and didn't leave them alone until I understood HOW I was getting those different results and knew by heart which nodes I needed etc. They covered a few different variable types and offered explanations/use cases. I hand wrote these in a note pad for quick reference but also to imprint on myself something I was writing out and reading aloud. For just 1 hr every night I would also allow myself "Fun time' where I just played around in the engine and would see if I could create anything in it from nothing. (This was important as just 5-6 hrs in this week I started to get used to terminology, names etc within the engine) Week 2 - I followed an extensive tutorial on Blueprint scripting (Over 20Hrs worth) Again, I followed the tutorials perfectly but then allowed myself to go off script and try to put my own twist on the examples they had given. I found myself thinking about how I would adapt what they were teaching for my own uses/ideas and the creativity flowed. Major stumbling blocks obviously, but this is where true learning is done. We don't walk, straight away in life. We fall over a lot of times until we start to realise what needs to be done to achieve the goal. Week 3 - By this point I'm starting to get excited. I decide to work on different areas for a week at a time. This week I've been looking at materials and textures. It's complex but mistakes are fine (As I said, this is when we do most of our learning) Play around, if you don't understand any areas or implementations then find a reliable source and learn why it's needed or why it does what it does. If you come away from anything knowing why it happened (from mistakes or otherwise), why it's need or what it does, you have learned and the next time you try to reference it you'll be so much more informed. Enjoy the process fellow aspiring game devs/programmers. Creativity is a wonderful thing, as is knowledge.

My brothers 1:43

These are all very good tips. It's very easy to overlook a lot of these when starting out, as your more focused on getting a result than learning. Loved the chair example and animation!

I would almost say, for the beginner questions ask chatgpt, but only gpt4 or gpt4o, gpt3.5 is "useless" for complex stuff. Edit: Same applies, ask how/why something works instead of just coping the code.

the visuals are cool but your voice is shit

underrated! you deserve more subs!

This does not only apply to game development but to programming in general. I teach programming to students at work, and probably the most common thing I see is actually the "not reading the error" problem. READ THE ERROR. If you don't understand it, google the things you don't understand, try to figure out what's wrong. The same applies to tutorials. They are great, but you have to understand what the person is doing, why they are doing it, and what else you may be able to do with their solution. Programming is problem solving, and if you don't learn to problem solve, you won't get far. I know it's hard, but you'll get there 😉

eyyy its here

the animation look great! and thanks for the tips :)

1:43 Middle one has very Human Design.

visuals r AAA but audio quality/script is like an indie game that no one heard of

i like the visuals they're really cool

I feel like I am really blind, there was the entire time an option to speed up code completion? I though that the code editor is just slow as heck

Some nice genuinely useful tips here! The middle click to close scripts is just 🎉🥳🤯

i was always saving my scripts to automatically format the spacing, thanks for tip 9!

How did you get your scripts panel to be above your code? And have the Methods be where the scripts panel was

Appreciate your attempt at making this video concise and not unnecessarily long, but this is just too fast. Awesome video though

El 17. me ha sorprendido su lógica, desconocía de su existencia. Bravo. El 22. me hizo explotar la cabeza, no sabia que se podía hacer eso en GODOT. Lo que echo de menos como progrramador es el uso de try{} catch() como contenedores de errores. Espero el dia que Godot implemente su uso

5:03 I SWEAR TO GOD (ot) AAAAAAAAAAAAAAAAAAAAAAAA ( i didn't know this existed! :3 )

This may be the most useful video for people starting out. Thank you so much for putting this together! Now I just have to remember to use them all.

great videos! I appreciate both in the series. pacing is definitely not too fast. thank you for saving us time!