Thank you for all of the feedback regarding the audio balance. I've started investigating how to improve the audio balance in my future videos, and believe I have a solution. Enjoy your time with GODOT, and consider checking out my other GODOT tutorials if this one tickles your fancy 😀
can you make full course top down 2D using GODOT, I will even pay it for full course cus the way you explain it simple and not complicated, I tried using unity and mostly I got confuse on my own scripts
Thanks for the help, if anyone else had trouble reading the code. I've Copy and pasted it from my exercise... extends KinematicBody2D var velocity : Vector2 = Vector2() var direction : Vector2 = Vector2() func read_input(): velocity = Vector2()
if Input.is_action_pressed("up"): velocity.y -= 1 direction = Vector2(0, -1) if Input.is_action_pressed("down"): velocity.y += 1 direction = Vector2(0, 1) if Input.is_action_pressed("left"): velocity.x -= 1 direction = Vector2(-1, 0) if Input.is_action_pressed("right"): velocity.x += 1 direction = Vector2 (1, 0)
Thank you for this! Had to even install one of those text comparison apps and found out the reason my code wouldn't work even though all the text was the same was because of a difference in indentation, having placed the velocity = velocity.normalized() lines all the way to the left
A fantastic video for those who are impatient to see their assets come to live fast and even for a free evening where you want to make a game for yourself. Magnificent to get hyped and keep learning, without all the initial hassle of reviewing thousand settings, their usage and such. Subscribed, well deserved!
Your tutorials have been very helpful. Thank you for getting me started into Godot. I was fairly lost until I found your tutorials and you quickly answered a lot of questions that got me going quickly.
Character movement script is outdated. You must use CharacterBody2D instead. I got the following from trimming down and adjusting the code from Godots official 2D game guide: extends CharacterBody2D signal hit @export var speed = 200 # Called every frame. 'delta' is the elapsed time since the previous frame. func _process(delta): var velocity = Vector2.ZERO # The player's movement vector. if Input.is_action_pressed("right"): velocity.x += 1 if Input.is_action_pressed("left"): velocity.x -= 1 if Input.is_action_pressed("down"): velocity.y += 1 if Input.is_action_pressed("up"): velocity.y -= 1 if velocity.length() > 0 : velocity = velocity.normalized() * speed position += velocity * delta
Here's a working script by Chatgpt: extends KinematicBody2D var velocity : Vector2 = Vector2() var direction : Vector2 = Vector2() func read_input(): direction = Vector2() # Reset the direction vector if Input.is_action_pressed("up"): direction.y -= 1 if Input.is_action_pressed("down"): direction.y += 1 if Input.is_action_pressed("left"): direction.x -= 1 if Input.is_action_pressed("right"): direction.x += 1 velocity = direction.normalized() # Normalize the direction vector velocity = move_and_slide(velocity * 200) func _physics_process(delta): read_input()
@@ufoyyyccc1040 chatgpt's knowledge cutoff is in 2021, which is way before kinematicbody got replaced by characterbody. The script you sent would not work.
Yes it is deprecated, godot 4.x is completely different from godot 3.x, in 4.x move_and_slide() dosen´t take any kinda of parameters you need to set the variable he called "velocity" with a different name and assign the global velocity of the class CharacterBody in code to this new variable.
@@ufoyyyccc1040 Don´t trust ChatGpt, most of it´s codes is a jigsaw stitched together, and they have notorious flaws, soon or later it won´t work anymore.
If you're making this tutorial with Godot 4.x some nodes and resources names have changed, eg KinematicBody2D has become CharacterBody2D. You can find the changes between versions in the Godot docs "Migrating to a new version"
Tip/request for future videos: RUclips shows your video as having -25dB volume level. That is far too low. I have you at 100% and my sound system at middle volume level and can almost not hear you speaking. You shouldn't go below -5dB on your master volume.
Followed along with this recently, there are some changes between the version of Godot that was used and Godot 4 which I used. However once you figure out the new tileset/tilemap controls and make sure to use the character2d instead of the kinematic node type then it works pretty well for learning.
o... m... g... there was someone talking! But the audio is so incredible quiet I had to pump my volume to 100%. Please, god, don't let me forget it after the video... please please please (this functions also as critique! Don't upload "I hear just fine on headset"!!) Stay crunchy.
This was wildly difficult for me because of the different versions. I figured some stuff out slowly, but there are some issues I can't resolve without ending up in a deep rabbit hole of functions.
4:51 "were just gonna save it (the scene)" But... How? What did you click on? I cant see any menu youre using because of text on the screen blocking the left side, and you don't tell us what hotkey if any you are using.
I will be attempting to recreate a game I made in Construct 3 for a tutorial using Godot this weekend. Your video should make that much easier. 😁 Hopefully your tutorial takes the top spot over the other tutorials I had to click through to get here. I'll be slowly going through your other videos as my new endeavor continues. Cheers!
I'm excited to jump on the GODOT train when 4.0 comes out. Till then I'll be working on sprites. @10:00 I dont know what they changed in the 4.0 alpha, but I was unable to set my player as a KinematicBody2D and chose something else, thus the tutorial code to move the player did not work. When I first added a new script to the player, Godot tried to automatically build one for me but it was set up as a platformer with gravity so the player immediately plummeted. I deleted the script and followed your instructions but could not pass a boolean to the non "KinematicBody2D" so it crashed. I bet if I did it again I could figure out what parts of the automatically created script to delete and I could incorporate your tutorial inside the remaining code. It may also be that parts of the KinematicBody2D are missing from the current 4.0 Alpha release. Awesome tutorial, but like I said, i'll work on other gamedev skills till 4.0 comes out.
Just use 3.4 or whatever the most stable version that's not 4. I started learning Godot with no programming experience, before this I was mainly working on music, sound effects, and art.
Tried watching but the sound effects like the ding are so loud and if I crank it down so it isn't ear ringing your voice is so quiet I struggle to hear you
I chuckled at this part. GDScript is pretty much a superset of Python, nothing JS about it, with a very few engine-specific built-in to the interpreter. From my understanding, it was originally Python during the early development and design of the engine, but there were some obstacles regarding memory management, so they opted for a custom language based on it that they had greater control over. My personal opinion is that they would have been better off using a popular language already in wide usage,and popular, but GDScript is extremely simple for novice users to piece together scripts without programming experience, so they did succeed very well on that important point.
even at 75 percent speed you move very quickly and speak at a very low volume. i'll have to put this in a que for much later on when i'm more familiar.
Hi! Im learning Godot actually and I followed your tutorial. My player dont want to walk (W,A,S,D isnt working) - I already checked the script with yours but its 1:1 the same....did you have any idea? Greetings from Germany, keep the good work!
Looks good but this video was too fast, too zoomed out and not really a step by step. Mister Taft Creates made a similar series for Unity but it was much slower and broken down over several videos
Hi, i love your tutorial but i have a bug: Is the code: extends KinematicBody var velocity : Vector2 = Vector2() var direction : Vector2 = Vector2() func read_imput(): velocity = Vector2()
if Input.is_action_pressed("up"): velocity.y -=1 direction = Vector2(0, -1)
if Input.is_action_pressed("down"): velocity.y -=1 direction = Vector2(0, 1)
if Input.is_action_pressed("left"): velocity.x -=1 direction = Vector2(-1, 0)
if Input.is_action_pressed("right"): velocity.x -=1 direction = Vector2(1, 0)
func _physics_process(delta): read_imput() App say: " The argument "delta" is never used in the functions '_physics_process'. If this is intended, prefix with an underscore: '_delta' How i can fix the bug ?? Thanks
Not necessarily a bug, just a little warning. Godot just wants to make sure you didn't plan to use "delta". If not just change it to "_delta" in the process function.
Couldn't figure out why my code wasn't working even though mine's pretty much a copy of the example. Then, figured out that apparently the amount of indentation a line has plays a part in whether the code works or not.
Is there a particular reason why you specifically cast the velocity and direction variables to Vector2? Since GDscript is dynamically typed, that seems rather pointless to me as the variable is going to be a Vector2 as soon as you assign a Vector2 value - which is instantly, since you instantiate it right away. But maybe I'm missing something?
The only reason you would cast variables in 3.x is for better warnings/errors and for 'cleaner' code (though that's subjective). In Godot 4 there is an actual performance gain when using static typing :>
Somehow on the player script line 26 doesnt work it says error and i dont know why and how i should fix it ive tried so long now but nothing seems to work.
Making maps on this engine with rpg maker assets is hard. Be easier to just hand draw the world IMO. Is this engine pixel based movement or tile based?
I just can't get the camera to work for some reason and the move_and_slide function keeps causing a error. XD Edit: Ok, I figured out what happened to the camera, it was just the main scene that was defined incorrectly, if someone has an issue with the camera like me you can fix it by selecting the main scene as your world. And it turns out that move_and_slide only works if you "extends" from the "kinematicBody2D" at the top, yeah I had left it as "extends node" XD
My brother in Christ, im literally learning how to Code and use all these functions on my PC that i never used and never knew existed from watching this video. And how to use godot of course as well. So first: im either a hidden genius, second: its not that hard to learn, or third: this video is damn good. I think its a combination of all 3😌 A bit more explanation would be good tho, i always pause and rewind the video to study what exactly you did there
For some of you having trouble here's a working script by Chatgpt: extends KinematicBody2D var velocity : Vector2 = Vector2() var direction : Vector2 = Vector2() func read_input(): direction = Vector2() # Reset the direction vector if Input.is_action_pressed("up"): direction.y -= 1 if Input.is_action_pressed("down"): direction.y += 1 if Input.is_action_pressed("left"): direction.x -= 1 if Input.is_action_pressed("right"): direction.x += 1 velocity = direction.normalized() # Normalize the direction vector velocity = move_and_slide(velocity * 200) func _physics_process(delta): read_input()
@@rxgravite1925 In my case, I put the 2 last lines, normalize and move slide, inside the right input verification. After backspacing it to be in the func read input, it worked.
awesome video, but please tone down the sfx, I had to crank up the volume because your voice is silent, then ill be deafened because of the ping sfx you used
Idk if you still need help with this, but after you attach the script to the player scene, SAVE your file before moving out of it (it being the player scene) or it will not apply the script to the player scene.
want to preface this by saying i am new to godot and something seems to be off with my movement code, I checked against yours and it is exactly the same, the only problem is with the velocity = velocity.normalized line, in the error list thing it says The method "normalized" isn't declared on base vector two, if anyone could help that be great. thank you for any help!
I know I'm two months late, but from what I'm gathering by trying to replicate your error, is that it's caused by a typo in the method you're trying to call(i.e. "normalized()").
In British English actually GOD-oh, in French (arguably the "correct" pronunciation) both vowels are pronounced the same. God-OH is also acceptable. GO-dot just sounds like a pixel-based race game. 🤣 The name has something to do with French military boots and racing cyclists. Didi and Gogo's bowler hats are an optional reference to early Hollywood slapstick. Now you know.
You deserve a subscribe
Thank you for all of the feedback regarding the audio balance. I've started investigating how to improve the audio balance in my future videos, and believe I have a solution. Enjoy your time with GODOT, and consider checking out my other GODOT tutorials if this one tickles your fancy 😀
My code isn't working
@@rembottherobot3418 Welcome to game development. ;)
@@rembottherobot3418 the real problem is when your code always works
can you make full course top down 2D using GODOT, I will even pay it for full course cus the way you explain it simple and not complicated, I tried using unity and mostly I got confuse on my own scripts
Volume is a lil bit too low
Thanks for the help, if anyone else had trouble reading the code.
I've Copy and pasted it from my exercise...
extends KinematicBody2D
var velocity : Vector2 = Vector2()
var direction : Vector2 = Vector2()
func read_input():
velocity = Vector2()
if Input.is_action_pressed("up"):
velocity.y -= 1
direction = Vector2(0, -1)
if Input.is_action_pressed("down"):
velocity.y += 1
direction = Vector2(0, 1)
if Input.is_action_pressed("left"):
velocity.x -= 1
direction = Vector2(-1, 0)
if Input.is_action_pressed("right"):
velocity.x += 1
direction = Vector2 (1, 0)
velocity = velocity.normalized()
velocity = move_and_slide(velocity * 200)
func _physics_process(delta):
read_input()
thank you, my code did not work but when i coy and pasted yours it did so thx
Thank you for this! Had to even install one of those text comparison apps and found out the reason my code wouldn't work even though all the text was the same was because of a difference in indentation, having placed the velocity = velocity.normalized() lines all the way to the left
thanks a ton! I mistakenly put Input_is_action_just_pressed instead of Input.is_action_pressed so copy pasting your code really help.
Really interesting but, please, zoom on code, it is barely readable
@CaptGooey i was on 1080p60 HD and still had trouble
The zoom window thing still exists for windows 10
Doesn't even matter for coding we have chatgpt3 already
@@kentadran ChatGPT's code is dreadfully bad
@@bruoche I use ChatGPT-4 for coding problems, it's not "dreadfully bad" as you mentioned.
my previous comment aside, this was genuinely hugely helpful. please consider doing more in this series. great work.
A fantastic video for those who are impatient to see their assets come to live fast and even for a free evening where you want to make a game for yourself. Magnificent to get hyped and keep learning, without all the initial hassle of reviewing thousand settings, their usage and such. Subscribed, well deserved!
Your tutorials have been very helpful. Thank you for getting me started into Godot. I was fairly lost until I found your tutorials and you quickly answered a lot of questions that got me going quickly.
Character movement script is outdated. You must use CharacterBody2D instead. I got the following from trimming down and adjusting the code from Godots official 2D game guide:
extends CharacterBody2D
signal hit
@export var speed = 200
# Called every frame. 'delta' is the elapsed time since the previous frame.
func _process(delta):
var velocity = Vector2.ZERO # The player's movement vector.
if Input.is_action_pressed("right"):
velocity.x += 1
if Input.is_action_pressed("left"):
velocity.x -= 1
if Input.is_action_pressed("down"):
velocity.y += 1
if Input.is_action_pressed("up"):
velocity.y -= 1
if velocity.length() > 0 :
velocity = velocity.normalized() * speed
position += velocity * delta
thank you so much, i could'nt make it work
Great video! Hope you'll do more on RPGs in Godot. My only suggestion would be to zoom in when showing any code. That'd be helpful. Thanks again!
Deprecated.
KinematicBody2D has been replaced by CharacterBody2D, and move_and_slide() refuses to work with it.
having the exact same problem
Here's a working script by Chatgpt:
extends KinematicBody2D
var velocity : Vector2 = Vector2()
var direction : Vector2 = Vector2()
func read_input():
direction = Vector2() # Reset the direction vector
if Input.is_action_pressed("up"):
direction.y -= 1
if Input.is_action_pressed("down"):
direction.y += 1
if Input.is_action_pressed("left"):
direction.x -= 1
if Input.is_action_pressed("right"):
direction.x += 1
velocity = direction.normalized() # Normalize the direction vector
velocity = move_and_slide(velocity * 200)
func _physics_process(delta):
read_input()
@@ufoyyyccc1040 chatgpt's knowledge cutoff is in 2021, which is way before kinematicbody got replaced by characterbody. The script you sent would not work.
Yes it is deprecated, godot 4.x is completely different from godot 3.x, in 4.x move_and_slide() dosen´t take any kinda of parameters you need to set the variable he called "velocity" with a different name and assign the global velocity of the class CharacterBody in code to this new variable.
@@ufoyyyccc1040 Don´t trust ChatGpt, most of it´s codes is a jigsaw stitched together, and they have notorious flaws, soon or later it won´t work anymore.
If you're making this tutorial with Godot 4.x some nodes and resources names have changed, eg KinematicBody2D has become CharacterBody2D. You can find the changes between versions in the Godot docs "Migrating to a new version"
Immediate thumbs up for having taken the time to learn how Godot is pronounced. It shows an admirable level of attention to detail. Thank you.
Tip/request for future videos:
RUclips shows your video as having -25dB volume level. That is far too low.
I have you at 100% and my sound system at middle volume level and can almost not hear you speaking.
You shouldn't go below -5dB on your master volume.
And the bell sounds were far too loud relative to the voiceover.
Yeah, it sounds very low on volume on my phone
Liked the video a lot.
A tip for next time: try to capture stuff in lower resolution, so that the text is more readable on smaller screens.
I’m a godot newbie but gdscript seems more like python syntax vs javascript
i'd say more than python ngl
it literally is python with minor changes
Yeah, first time I've heard that comparison tbh.
And I'll be honest ... thank god it's NOT like javascript.
Great content. Only feedback is the volume of your voice feels low and distant, your system's volume is a lot louder.
That ding sound at the beginning hurt my ears
Followed along with this recently, there are some changes between the version of Godot that was used and Godot 4 which I used. However once you figure out the new tileset/tilemap controls and make sure to use the character2d instead of the kinematic node type then it works pretty well for learning.
good video. two things imo though, audio too low and when on the scripting would be helpful to have a zoomed in view available.
i cannot see the code myself sadly :(
Thank Godot! We no longer have to wait for Godot.
Sound in this video is very silent.
I implemented it.. it works. Now I just need to make the Escape key close the game. :D
Awesome tutorial! as full stack dev just jumping in this quick is amazing
I only go right and I made sure everything is correct
Wish this was updated :(
I am surprised to see a video where medium audio is actually medium audio. Love it!
o... m... g... there was someone talking! But the audio is so incredible quiet I had to pump my volume to 100%. Please, god, don't let me forget it after the video... please please please (this functions also as critique! Don't upload "I hear just fine on headset"!!)
Stay crunchy.
This was wildly difficult for me because of the different versions. I figured some stuff out slowly, but there are some issues I can't resolve without ending up in a deep rabbit hole of functions.
Damn you really hammer that enter key lol
4:51
"were just gonna save it (the scene)"
But... How? What did you click on?
I cant see any menu youre using because of text on the screen blocking the left side, and you don't tell us what hotkey if any you are using.
Ctr s
I will be attempting to recreate a game I made in Construct 3 for a tutorial using Godot this weekend. Your video should make that much easier. 😁
Hopefully your tutorial takes the top spot over the other tutorials I had to click through to get here. I'll be slowly going through your other videos as my new endeavor continues.
Cheers!
I'm excited to jump on the GODOT train when 4.0 comes out. Till then I'll be working on sprites.
@10:00 I dont know what they changed in the 4.0 alpha, but I was unable to set my player as a KinematicBody2D and chose something else, thus the tutorial code to move the player did not work. When I first added a new script to the player, Godot tried to automatically build one for me but it was set up as a platformer with gravity so the player immediately plummeted. I deleted the script and followed your instructions but could not pass a boolean to the non "KinematicBody2D" so it crashed. I bet if I did it again I could figure out what parts of the automatically created script to delete and I could incorporate your tutorial inside the remaining code. It may also be that parts of the KinematicBody2D are missing from the current 4.0 Alpha release.
Awesome tutorial, but like I said, i'll work on other gamedev skills till 4.0 comes out.
Just use 3.4 or whatever the most stable version that's not 4. I started learning Godot with no programming experience, before this I was mainly working on music, sound effects, and art.
KinematicBody2D has apparently, been replaced by CharacterBody2D
@@sakules Thank you sir! That was what I was thinking and about to search an answer or post to ask for clarification!
Andrew Hoffman you are Hyun right then you are really god at stickman fights
This Was So Helpful! If It Wasn't For This I Wouldn't Be Using Godot.
Line 26:Function "move_and_slide()" not found in base self.
Sure wish I could hear this video, looks really helpful.
The audio is barely audible. I usually have to turn youtube down, but i have everything cranked and can barely hear you.
i dont think i have the right one. Options are missing throughout the tilemap part. I'll have to come back later. Its 4am
I think I'm seeing the same thing. We're on version 4.1.1 right now.
It's Godot 3.4.2
Need more sound volume in the future.
Tried watching but the sound effects like the ding are so loud and if I crank it down so it isn't ear ringing your voice is so quiet I struggle to hear you
1:29 Gdscript is a lot more similar to Python than to Javascript.
I chuckled at this part. GDScript is pretty much a superset of Python, nothing JS about it, with a very few engine-specific built-in to the interpreter. From my understanding, it was originally Python during the early development and design of the engine, but there were some obstacles regarding memory management, so they opted for a custom language based on it that they had greater control over. My personal opinion is that they would have been better off using a popular language already in wide usage,and popular, but GDScript is extremely simple for novice users to piece together scripts without programming experience, so they did succeed very well on that important point.
Calling this an "RPG" is a bit of a stretch lol. Cool video, nevertheless. Would love to see you work on this some more.
What would be a better engine for a top down JRPG like the old Final Fantasy or games you’d make in the RPG Maker engine; Godot or Unity?
Godot
Thank you soo much for making these videos!
even at 75 percent speed you move very quickly and speak at a very low volume. i'll have to put this in a que for much later on when i'm more familiar.
Why is his volume set to .7%?
Thank you so much! You helped me a lot! I can't thank you enough, so.... New subscriber!
anyone know why my snapping grid doesnt scale down to 16 pixels when I'm creating a tileset and selecting individual tiles from a larger image?
this was really helpful, thanks heaps!
Hi! Im learning Godot actually and I followed your tutorial. My player dont want to walk (W,A,S,D isnt working) - I already checked the script with yours but its 1:1 the same....did you have any idea? Greetings from Germany, keep the good work!
Pretty new too but did you go to the input map and add the keybinds?
@@aquario1007 I was thinking exactly the same.
Is there something different between 3.4.2 and 3.4.4, because this code, specifically the player movement code, does not work.
Yeah I guess, Value "Move_and_slide" have type bool and cant work with variable Vector2. I got this error
so godot has an isometric mode and there are some isometric assets out there. is the programming process the same when doing 2d isometric style?
3:39 headphone user warning ⚠️
Looks good but this video was too fast, too zoomed out and not really a step by step. Mister Taft Creates made a similar series for Unity but it was much slower and broken down over several videos
Can't see "current" in camera 2D is there an alternative to that check box?
it was removed in godot 4 this tutorial is pretty outdated it being 2 years old
What about people WITH programming experience, surely I can avoid ui stuff by coding right? But no one talks about full customizability with code
This helped so much!
very good introduction video
Hi, i love your tutorial but i have a bug:
Is the code:
extends KinematicBody
var velocity : Vector2 = Vector2()
var direction : Vector2 = Vector2()
func read_imput():
velocity = Vector2()
if Input.is_action_pressed("up"):
velocity.y -=1
direction = Vector2(0, -1)
if Input.is_action_pressed("down"):
velocity.y -=1
direction = Vector2(0, 1)
if Input.is_action_pressed("left"):
velocity.x -=1
direction = Vector2(-1, 0)
if Input.is_action_pressed("right"):
velocity.x -=1
direction = Vector2(1, 0)
velocity = velocity.normalized()
velocity = move_and_slide()
func _physics_process(delta):
read_imput()
App say: " The argument "delta" is never used in the functions '_physics_process'. If this is intended, prefix with an underscore: '_delta'
How i can fix the bug ??
Thanks
Not necessarily a bug, just a little warning. Godot just wants to make sure you didn't plan to use "delta". If not just change it to "_delta" in the process function.
i have a bug too Too few arguments for "move_and_slide()" call. Expected at least 1.
Near the end its: Velocity = move_and_slide(velocity * 200)
the delta thing should be fine
Couldn't figure out why my code wasn't working even though mine's pretty much a copy of the example. Then, figured out that apparently the amount of indentation a line has plays a part in whether the code works or not.
You are amnazing
very cool tutorial, thank you
thanks!
Thanks so much for making this this i just picked up the software and it works great
where did you get those keybindings from? there's none in my godot.
can you make a tutorial on adding background music and sound effexts
thank you so much
a bit of a stretch calling this an RPG but i wish you would do more advanced tutorials and provide a github link for what you have posted
Is there a particular reason why you specifically cast the velocity and direction variables to Vector2?
Since GDscript is dynamically typed, that seems rather pointless to me as the variable is going to be a Vector2 as soon as you assign a Vector2 value - which is instantly, since you instantiate it right away.
But maybe I'm missing something?
The only reason you would cast variables in 3.x is for better warnings/errors and for 'cleaner' code (though that's subjective).
In Godot 4 there is an actual performance gain when using static typing :>
Somehow on the player script line 26 doesnt work it says error and i dont know why and how i should fix it ive tried so long now but nothing seems to work.
Good tutorial but please fix volume...mic is really quiet and the notifications are blasting my speakers when I turn my volume up to hear better.
seriously good video
Dings are too loud! And cant hear what you're saying. Please try fixing audio.
4:49 "so we're just gonna save it" dude what did you do there
CTRL+S (Save File)
Making maps on this engine with rpg maker assets is hard. Be easier to just hand draw the world IMO. Is this engine pixel based movement or tile based?
I just can't get the camera to work for some reason and the move_and_slide function keeps causing a error. XD
Edit: Ok, I figured out what happened to the camera, it was just the main scene that was defined incorrectly, if someone has an issue with the camera like me you can fix it by selecting the main scene as your world.
And it turns out that move_and_slide only works if you "extends" from the "kinematicBody2D" at the top, yeah I had left it as "extends node" XD
My brother in Christ, im literally learning how to Code and use all these functions on my PC that i never used and never knew existed from watching this video. And how to use godot of course as well.
So first: im either a hidden genius, second: its not that hard to learn, or third: this video is damn good.
I think its a combination of all 3😌
A bit more explanation would be good tho, i always pause and rewind the video to study what exactly you did there
Very nice tutorial, but I feel like you could've explained the animations.
for some reason my collision doesnt work
even though i have saved and written all the code correctly.
But this isn't the complete, how do you add enemies how do u add attack movements etc?
For some of you having trouble here's a working script by Chatgpt:
extends KinematicBody2D
var velocity : Vector2 = Vector2()
var direction : Vector2 = Vector2()
func read_input():
direction = Vector2() # Reset the direction vector
if Input.is_action_pressed("up"):
direction.y -= 1
if Input.is_action_pressed("down"):
direction.y += 1
if Input.is_action_pressed("left"):
direction.x -= 1
if Input.is_action_pressed("right"):
direction.x += 1
velocity = direction.normalized() # Normalize the direction vector
velocity = move_and_slide(velocity * 200)
func _physics_process(delta):
read_input()
Isn’t GDscript based on python?
My player can only move right and diagonal right up/down. I'm confused.
I figured it out. It was the indentation.
yeah i have the same problem and im not sure what to do ?
@@rxgravite1925 In my case, I put the 2 last lines, normalize and move slide, inside the right input verification. After backspacing it to be in the func read input, it worked.
@@rxgravite1925 nesting
@@StrandedClone what does that mean😭
For me the preview of the game doesn't work any fixes?
My wasd Movement keeps traveling in the direction of the first key pressed FOREVER!!! how do i correct this?
my character does not move, my code gives no errors, I did attach script to the player.
Possible reasons why this could be? Possible solutions? TIA
heyy, idk whats happening but it only lets me move left and diagonal i have absoloutly no clue how to fix it can someone please help ?
Thanks for the video though I must say I have a friend like you who really SMACKS that enter key ✌😂
When typing the movement script section I did not have the same auto-complete prompts appear for me. Is there a setting to enable this?
think you
awesome video, but please tone down the sfx, I had to crank up the volume because your voice is silent, then ill be deafened because of the ping sfx you used
Why cant I hold wasd down to move? I have to tap them repeatedly. It's probably because I'm on chromebook but idk
are you sure you used Input.is_action_pressed() and not something slightly different?
My left and down do not work how can I fix this?
What was direction for?
does anyone know how to add a sprint input for the code used here?
Getting the Player sprite to move? I can’t get him to move.
Idk if you still need help with this, but after you attach the script to the player scene, SAVE your file before moving out of it (it being the player scene) or it will not apply the script to the player scene.
the dings are awful my man, turn em down my guy. I liked the video though!
want to preface this by saying i am new to godot and something seems to be off with my movement code, I checked against yours and it is exactly the same, the only problem is with the velocity = velocity.normalized line, in the error list thing it says The method "normalized" isn't declared on base vector two, if anyone could help that be great. thank you for any help!
I know I'm two months late, but from what I'm gathering by trying to replicate your error, is that it's caused by a typo in the method you're trying to call(i.e. "normalized()").
please, for the love of all that is holy, turn down the volume on the ping noises
In British English actually GOD-oh, in French (arguably the "correct" pronunciation) both vowels are pronounced the same. God-OH is also acceptable. GO-dot just sounds like a pixel-based race game. 🤣 The name has something to do with French military boots and racing cyclists. Didi and Gogo's bowler hats are an optional reference to early Hollywood slapstick. Now you know.