Видео

Thanks so much for this. It took me three days to wrap my head around state machines, but thanks to your videos and downloadable examples, I've got state machines handling characters' actions in the game I'm working on

awesome, thanks! Any directions for the range highlight that "shapes" around the walls?

Gold stuff

Thank you!

Wow, this is actually a very informative video with a bunch of quirks I didn't know about... LIKED!

nooo he didnt mention the shortcuts to evaluate an expression(ctrl shift e) and copying or moving lines of code (ctrl alt down/up)(alt down/up)!!! sidenote: these might not work when preferring wayland, since it's broken on my linux laptop

Godot has REGIONS? Oh thanks god for this information. I use them so much on my c# scripts and was missing them on godot (though I also should have checked)

Oh the prints() will save me a lot of time, thanks a lot ❤

Brilliant vid, definitely saving for reference 🙌

Dude thank you so much this is amazing information to have!

that's great tutorial! thank you!

is there a reason why you are not simply making the animations and state machine variables on your player node exported vars? on one hand you say that not passing the reference would break the code if you change the node structure but on the other hand you hard code the path to your state machine. just trying to understand your reasoning as i‘m currently in the process of switching from unity where i heavily used inspector set paths

Last one was worth the free price of admission :p

👍

A m a z i n g video, thank you!

Really helpful!

use & when possible (StringName). it's more optimized.

Code regions and prints() goated fr

Very helpful, thank you!

I literally needed Dictionary.get() today, wish I'd knew sooner lol

#regions ❤ did not know they existed

Thanks for the video. it is very informative. by the way, what is the game shown in 3:46?

The one about dictionaries and prints and print_rich were pretty helpful, thanks for the vid!

Cool! Something I really wish they implemented is to view my script's documentation without having to class_name them.

i will watch all your videos

Программировать научись сын сам знаешь кого

Very inspiring video! Some thoughts: 1) I think your progression generator can be nearly effortlessly adapted to random room placement 2) Another kind of locks are locks that require multiple keys. Also you probably can adapt any algorithm to do it because it is reducible to a sequence of simple locks. 3) To generate small keys you can find a path to a generated door from start, flood fill all accessible from this path without unlocking doors rooms and place a small key in this area. I think it should work for one type of small keys, no big keys and no extra keys perfectly. For big keys you can also flood fill from paths to each required key for already checked paths. For multiple types of small keys it should work fine I guess. It ignores some interesting possibilities in both this cases (like locking access to all small keys of one kind behind big key/another kind of small keys). For generating extra small keys you need some other approach. Probably you can check such level (with 1 small key type) for validity by using greedy algorithm (player picks door that unlocks least keys). So I think (lets say for simplicity that each room is locked behind a small key door) for each room you should keep track of the max amount of keys in the room added after it and append to it only rooms with greater amount of small keys in them. And if you make share that amount of small keys player has during such a process is > 0 (except exit, you can let it be 0 there) it will work, I think.

Great Video. Thanks.

What if I wanted to use a Animation Tree to blend the animations?

Hi Shaggy, could you make an update to this topic covering handling multiple substates? (BaseState>MoveState/ActionState/WeaponState)?

Any chance it'll be uploaded to github?

U r fucking genious

How important is it to use the optional static typing here? I couldn't find a reason to do so in the GDScript style guide

THANK YOU SO MUCH!!!

can i ask what's the importance of adding the return void to each function? is there a reason for it?

Or you can ignore all of that and make jump king

What was the 3rd game you showed never seen it

When I was earning my master's degree, I heard a lot about finite state machines (FSMs), but it was all theory - like clouds in the sky: there's a lot of water, but you can't drink it. I toiled for three months after graduating until I implemented my first FSM in code in 1981. Now, there is a programming methodology based on this concept - v-agent oriented programming (VAOP) - with many examples of its implementation. It's best to start learning about VAOP with this article on Medium: "Bagels and Muffins of Programming or How Easy It Is to Convert a Bagel into a Black Hole". With VAOP, you can implement FSM in any programming language.

That's a pretty good example of what game designers have to come up with in their work, i.e. what game design is all about. People think game design is about large scale ideas, when in fact the things described in this video are the type of stuff game designers need to put tons of time and effort, sweat and tears into figuring out on every game they make.

do you know where I could find a video like this but for defold?

I use rigidbodies and they work great. I used the tip with reducing velocity when releasing jump button. I love it! In my case i only reduce the velocity by 20% but it makes huge difference.

for some reason, on line 10 "value_changed.connect()" is not working for me. It says "not declared in the current Scope".

Oh wise dev. I bow to your wisdom.

On the next to last day of my first game jam. You are my HERO!

I realized coding things such as sprite.flip_h = true. Is not a good practice, the best option is to do it from an animator... Maybe this character does not have an animator.

Coyote time sucks if you design jumps to require using it. It really annoys me when games make it so that the only way you can make a jump is to literally fall off the ledge before pressing the jump button. It should be there to catch millisecond mistakes, not a feature of level design

This tutorial is absolutely fantastic, and I've learned a great deal from it. Thank you very much for sharing your knowledge. I have one observation regarding the "move_component". I noticed that while you've declared types for all parameters and variables, the "move_component" was an exception. Would it be possible to encapsulate these functionalities in a class like "MoveController"? This class could include fundamental methods such as "get_move_direction()", "wants_to_jump()",... In "CharacterBody2D", you might then add a node with a new script titled "PlayerMoveController" that inherits from "MoveController" and overrides certain functions. Within "PlayerMoveController", you could manage controller inputs, and in NPCs, automate certain behaviors. Ultimately, this approach would allow for the specific type declaration for "move_component" using "MoveController", enhancing the robustness and readability of the code.

I have spent all fucking week trying to find a solution and here late at night at 01:23 on friday, with a new Indev releases every Saturday, thank you so much for literally de-stressing my whole week. You just earned a sub, like and a pin on my bookmark bar

Man I made a game in action script around 2013… it’s not even playable anymore since flash has been abandoned

also if you had a death state how would you do that? would you have a transition from every other state to the death state?