How to setup player movement in Godot 4! 

THANK YOU SO MUCH for going back and adding this. Most people wouldn't and it's really frustrating.

Spent an hour following it, wondering where all the error messages came from. Maybe the title should say: only works with godot 4.whatever or sth like that. Otherwise I quite liked it. Moving on...

I'll make sure to do that in the next vid. Thanks for the feedback!

Ya wtf 😭 can't see anything

Screenshot then zoom

Don’t even need to screenshot u can zoom with RU-vid now

for me as well. has anyone figured this out?

Yup, I actually just looked this over again today, and saw that XD I'll make an updated more optimized vid soon 👌

@@queblegamedevelopment4143 Worth noting, this code is broken in Godot 4.1 due to a minor mistake. You have `axis = get_input_axis()`, while setting the value of axis directly in the get_input_axis code. This sets the value of axis to Nil since there is no return value in the function, causing an invalid operand error when running the code. Changing from `axis = ...` to `return ...` the same value that was applied directly solves the issue (and is much cleaner, since this was clearly the intended approach anyways). I was very confused, since I tried to run the exact same thing you had up there, but it was throwing this error. Thought you should know! Otherwise, great tutorial! Subscribed :D

I've run into the same error. I've tried 5 different vids and followed every direction, copied each code line for line and still haven't been able to make a character move yet. Lol

Oh interesting, thanks for pointing this out! I'll need to re record this one

@@queblegamedevelopment4143 If you find a way to use a vector2 expression somehow in the new build I would appreciate if you could give many any advice.

Which ones?

same here. it moves up and left fine, but the right and down are just 1 pixel each press.

Did you find a solution?

@@JetMango yes, thanks for asking. I just didn't put the script on the player-node. That's why it didn't work. Nice tutorial though!

Noted for future vids! 👍

There are many options for achieving this, all of which have different pros and cons depending on the situation obviously. If I understand your question correctly, I'd recommend just putting the movement script inside the _physics_process() function (which executes code every physics frame of the game). Alternatively you could setup the motion inside an animation player or a tween, but this would depend heavily on how you plan on using the motion.

@@queblegamedevelopment4143 Thanks 😊

yea press equal two times

Awesome! You should follow my latest player movement video if you want the animations part too!

Hmm I'm having a hard time understanding exactly what's going on, would you mind describing the problem in more detail? :)

@@queblegamedevelopment4143 well I made a top down game by this code extends CharacterBody2D const speed = 100 const friction = 500 const acceleration = 500 @onready var animeplayer = $AnimationPlayer @onready var animetree = $AnimationTree func _ready() -> void: set_motion_mode(MOTION_MODE_FLOATING) func _physics_process(delta): var move_direction = Vector2( Input.get_action_strength("right")- Input.get_action_strength("left"), Input.get_action_strength("down")- Input.get_action_strength("up"), ) move_direction = move_direction.normalized() if (move_direction != Vector2.ZERO): animetree.travel("parameters/moveing/blend_position") velocity = velocity.move_toward(move_direction*speed,acceleration*delta) else : velocity = velocity.move_toward(Vector2.ZERO,friction*delta) move_and_slide() but the player is geting stuck with collision i want it to slide when colliding

Hmm, I'm not by a computer atm, but I'll see if I can solve it tomorrow 👌

@@queblegamedevelopment4143 ok thanks

()

move_and_slide() not move_and_slide

Are you sure you're comparing the input axis to a Vector2? If the input axis is a Vector2 (just x and y values), then it's impossible to compare it to a Vector3 with the == operator

@@queblegamedevelopment4143 Oh that makes sense, I'll see if I can fix it

@@queblegamedevelopment4143 got it to work somehow lol (I spaced some periods and colons so youtube doesn't delete my comment. func get_input_axis() : var input_dir = Input . get_vector("left", "right", "forward", "back") var axis = (transform . basis * Vector3(input_dir . x, 0, input_dir . y)) . normalized() return axis . normalized()

I didnt make my input names the exact same as they were in the code, so it wasnt calling the movements like it should. make sure inputs are named as they are in the code like move_right

Yeah you can do that! Just create a fake z axis variable, and change the jump height with that value. Then you could move the player up by that amount (multiplied by your tile ratio), and also keep the players shadow on the ground

If you're on version 4.2, you may want to check out my latest video on this :-)

​@@queblegamedevelopment4143 I spelled physics wrong 😂

Hmm, that might be it, but probably not. Are you getting any errors? Also verify that you setup the input map correctly, and if you're still having trouble, try printing out or displaying the velocity to make sure the values are correct. Another thing to note: Since you're multiplying the movement by Delta, you'll want to use higher values, otherwise the motion will be too small to notice. Maybe try adding a 0 to the movement speed if that's the case. Hope this helps!

@@queblegamedevelopment4143 Thank you ill be sure to try these

@@queblegamedevelopment4143 and it didn't show any errors but there are little yellow arrows at the line apply_movement(axis * ACCELERATION * delta) and move(delta)

I think I just turned on GameChops radio while I recorded 😅

replaced the code with your pinned comment. Works. My bad

Control+S to save :) This is so that the scene can be saved in its own file. Once you save a scene, you can create an instance of it anywhere

@@queblegamedevelopment4143thx❤

Hmmm, is your character a Character body 2d?

What version of Godot are u using? If you're in anything later than 4.0, you should checkout my latest tutorial (pinned comment) on this system :)

@@queblegamedevelopment4143 4.1.2

does work as of 12/7/2023, What problem are you having?

thank you, btw you left a space in "move_down"

Noted :)

If you wanna checkout my updated video on this topic, it's a bit cleaner and doesn't have music :)

Thank you!

Yeah but Unity can't be trusted.

And you can do this in 2 lines of code if you wanted in godot, He is making it longer to have cleaner code, because its better to have 20 easy to read lines of code than 5 lines of code that you don't remember how they work, and have to look it up or be too afraid to change anything. In Godot you can write func _physics_process(delta): velocity = (((int(Input.is_action_pressed("move_right")) - int(Input.is_action_pressed("move_left")), int(Input.is_action_pressed("move_down")) - int(Input.is_action_pressed("move_up")).normalized) * delta * 15000).limit_length(300) That is 2 lines of code that does basically the exact same thing, but its just not very readable so you wouldn't do it like that, and honestly, the about 30 lines of code he makes in the video is really nothing, your whole game could easily have 100,000 lines of code in total, and it could be much much more, so I would rather have code that is easy to read if I ever need to change something than code that is a little shorter.

It's almost just as many lines in unity but go off ig