Devlog 02

I just finished video 2 where we do more player movement and create 2 states in a state machine. I was surprised that for a tutorial series focusing on beginner and intermediate learners, we started on state machines right away. We set up animations and key frames in a way different way than I'm used to in Godot. It works mostly the same way, but we add based on frames. Also, when we use @onready variables, I'm not sure why they don't have us drag from the scene tree, then hold down CTRL, and drop. In Godot that writes that whole line so it helps avoid typing mistakes. There might be a reason they get to later, but they didn't mention it yet. They did mention that sometimes you get a null value on a variable if it's not in the tree yet and that's why we use @onready variables, so we can't use it until it's ready, and we don't have those errors. That I didn't know. They also didn't explain Enums very much, but it seems like an array, not a dictionary since there is no additional values assigned. I really liked making custom physics layers by name in the 2d physics area. That was well explained instead of trying to remember what number layer each object was on, or what it was masking or looking for by number. The actual name makes it easier to remember and I will use that with my students for sure next year. Using an underscore in front of delta, when it was named as a parameter, but not used, to remove the warning, was a useful explanation. My students complain about that all the time even if it doesn't impede their progress.