Best Learning content for Godot, I assume you are a professional teacher. The way you teach and explain things is by far better then anything else on RU-vid.
I find that a lot of tutorials spam out instructions without explaining them. Sometimes that's enough I guess but overall I prefer your approach. Very helpful for actually learning and understanding.
This is a great tutorial, thanks for creating this and sharing it for free. really clear and comprehensive explanation, perfect examples and even has challenges to solve. couldn't ask for more. Thank you!!
After checking the first one I have to say this Part 2 is also excellent. Definitely going to share this with anyone who needs a "from zero" style video to get them going and I hope to see more from you in the future 👍
Many thanks for your wonderful training videos. I'm a long time hobbyist C# programmer and I'm finding my transition to Godot much easier thanks to your effort.
You're absolutely KILLING it! Ignore the haters who focus on how your art was made with AI, it personally looks great. I've introduced some friends to your material, and they absolutely love it.
I'm struggling with understanding 3D transforms and how to manipulate them. It'd be great if you covered these as you explain things in a way which makes it easy to understand. Thanks for all your videos so far.
First of all i wanted to express my sincerest gratitude for your awesome work like many before me. Your style of doing something the most straightforward and simplest way and then correcting "yourself" has not just opened my eyes to a broadened and systematic way of looking at solving problems more than once (especially in your UI and data model videos), it also impressed me in regards to teaching techniques. Just a little side note from me as a fellow german. While you can use "before" positionally like you do in your video, most of the time it is either used temporal ("i was a bad programner before watching your video") or in a more abstract positional way like "sitting before the jury/judge". Your use of the word (function: "item_before_me) sounds very german to me and maybe you would be more on the safe side if you'd use "in front" instead. Not trying to nitpick only trying to give constructive feedback. But maybe it only sounds strange to me and our englisch native speaking friends would disagree. Best wishes
I'm honestly not sure about "before". I've seen it used in different ways and the dictionaries also have direct positional examples like "we sat before the fire", "he stood before me". Maybe a native speaker can shed some light on this?
@@godotneers Native speaker here! I would say that using "in front" is more common, at least colloquially, than "before" in the context you mentioned. From my experience, I usually see sentences like "we sat before the fire" or "he stood before me" in more formal settings like literature.
Hello! can you can give us an idea when the next tutorial will come out? It has been 2 months since this episode, and i was wondering when the 3rd one will get released. I really hope it's soon, thank you for this useful and comprehensive resource!
Another great video and demonstration project. Will there be a part 3? Also this part is melting my brain, I don't quite get how the variable gets the item name from the for loop. Or is it just because the Array and Dictionary share the names of the items? for item_name: String in item_names: var price_for_item = menu[item_name] total_price += price_for_item
Is there a way to use say() method outside of what_should_i_do() function? I'm trying to use say() in _input() function and it's not working there. UPD: i've found a way to do that - expand Mr G node and use speech_bubble's node method say()
First of all, thank you for your very helpful tutorials. As a teacher I appreciate your style of teaching by showing how to solve problems instead of just quick fixing them. So I have a question about the dictionaries: To me it is not quite obvious, what the real benefit of a dicitionary is? The price of the item from your example illustrates this very good, because for me this would be something to include as a property in the class item like the item_name (#DataModels). This has the benefit, that whenever I create a new item I don't have to update the dictionary. Maybe you could give an example for a feature of a game, which can't be/shouldn't be handled via a data model but rather by a dictionary. Liebe Grüße aus Deutschland
Dictionaries are mostly useful as lookup tables because they can very quickly find an item for a given key. If you want to store structured data, you can technically use a dictionary for that but a class is usually the better choice for this because you can give proper types to all properties and you get auto-complete. Dictionaries can also be used as a "Set" which is a data structure available in other programming languages. Say you have 5000 items identified by their ID and you want to know whether or not you have an item with a certain ID. If you use an Array to store the items, you will have to traverse 5000 items in the worst case to find out whether or not you have one with a given ID. If you use a dictionary for this (ID is key, item is value) your lookup will be a *_lot_* quicker.
@@godotneers Thank you for your time. By the way: It would be very helpful for me if you could show in a tutorial how to use/setup the versioncontrol via github for a godot project. If this topic doesn't make it to the top of your videoideas, never mind. I still will watch your videos ;)
Funny, I was skipping ahead a bit on my own and by accident made the exact same mistake as in the video, with lower case letters for dictionary entries. Found it and fixed it then continued the video and saw that you created the exact same problem for yourself.
thanks for making this amazing tutorial. i tried downloading the example project and open it but it shows an error due to vilkan drive. i can only run compatibility option. is it possible to follow your tutorial using my low end laptop?
@@godotneersthanks for replying. i tried but it sends me the error I even tried making a project and then copying the folders from the project but it failed. if its not too much to ask could you maybe export the files using compatibility renderer?
I tried pausing the video to teach myself dictionaries through the Search Help docs. I was NEVER going to figure that out. How will I ever learn anything on my own in Godot? 😭
I'm wondering what would be like in games like Fallout Shelter where you have 2 Body2D that must be inserted into an area, like a room, and when that happens it starts some function....but thanks for the video. But I'm looking for something in the style of Fallout Shelter....how to make a Side-View Management game....2 months trying learn to start my project and nothing....i'm stuck.
Well the thing with "how to make Game X" - tutorials is that they are highly specific to a game and if you want to do something slightly different then you're stuck. I call these kinds of videos "recipe-style" tutorials. They give you a recipe to follow and you don't need to know how everything works - you just follow the recipe and get a result. The problem with this approach is that you never learn why stuff is done the way it is and the concepts behind what is shown in the video. So this kind of video is super nice if you know actually how stuff works and just look for a neat technique for a specific problem. But its not very useful if you don't know the basics of the engine and try to build a game from nothing. The most important skill really is to be able to dissect a problem in to smaller problems and then find solutions for these smaller problems. So start really small and simple and work your way up. Instead of trying to do a full blown 2d management sim, first try some simple things that you can later use in your final game. E.g. say you want to make a trigger that does something when the player steps on it (e.g. a door automatically opening for the player). How could that work? We dissect the problem: 1. We assume we already got the player movement done. 2. We need something that can detect if the player walks over it. 3. We need a way to notify our door to open close as the player enters or exits the trigger. So now we can find solutions for these problems. E.g. we can find out that there is a thing called Area2D in Godot which can detect when it overlaps with other Areas or Bodies. This sounds like it could be useful for Problem 2. We can also find out that Godot provides a thing called "signals" which allow us to notify objects when something interesting happens. This sounds like it could be useful to solve problem 3. Now we have new, more specific problems: 1. We need to find out how Area2D works and how we need to set it up so it detects our player. 2. We need to find out which signals Area2D provides and see if one of them can be used to notify our door. 3. We need to react to the notification in our door and open/close it. And so on... You see that even this very simple example requires a lot of thinking, looking up stuff and problem solving. And this is very very difficult at the beginning when you have no experience to rely on. So don't be discouraged if you haven't made your 2d management sim in 2 months. Developing games like this really takes a long time (e.g. Fallout Shelter took 5 years to make and was made by a team of seasoned developers at Bethesda).
@@godotneers Thank you soo much.....actually yesterday i watch a video from a woman dev here on RU-vid and she explains all the problems she had and how she solved....and it's literally the same thing you explain here. Breaking the ideas into small pieces. Thanks again, i will change my aproach.
First of all, I like your videos! The only confusing thing sometimes is when you ask how can we solve this, and then you show a way which is wrong.. 😅 So why show it in the first place? You could just have explained in a side note, that it can't be done inside the for loop (the thing with the three variables for item names for example).
I do it this way to mimic the way in which a beginner would approach this. I think seeing the actual problem is a much better illustration of why something doesn't work or maybe is problematic than just saying "do it like this and you won't have problems" . By seeing the problem occur and understanding why the problem occurs and how a solution actually solves it, I hope viewers will be better equipped to handle problems that come up when they work on their own projects. The idea is that viewers will be able to say "yeah I have seen this before, i know how to fix it" rather than "oh this must be the thing the person in the video talked about in a side note but i have no clue how to fix the problem myself". Also I really like the "show, don't tell" technique ;).
@@godotneers Thanks for taking the time to respond, i understand. I guess for me (i'm like intermediate i guess) it doesn't make much sense to watch everything, i just like to check if i have some gaps maybe (and i learned a few shortcuts at least, and some details about classes). In general i like your style, didn't want to be nit-picking. 🙂
