Only halfway through the video but I gotta say this tutorial is top notch my man. I was pulling my hair out trying to get this stuff working but you've clarified so many things for me.
Thanks for the video) Was going to make exactly such interactions, except that I was planning to have multiple "features" of objects, one of which would be "Interactable".
lol just found your channel like 2-3 days ago and was translating all the interaction stuff from godot 3 video to my 4.2 version XD could of just clicked on your channel to find this updated one smh either way im gonna watch it!
Thank you for your tutorial. The textures in your videos look amazing. Do you create them yourself? Could you please share your workflow? How do you create the normal maps?
I'm glad you like them! Yes, I make them using Gimp and Krita. I hand paint all the textures and roughness map. For the normal maps, I draw the depth map (black is deep, white is shallow) and use the normal map filter in Krita to generate the final result.
CharacterBody vs RigidBody collisions tend to be that way. I haven't found an all-in-one fix for it, but depending on your game, you can make both the player and the object be either both rigidbodies or both characterbodies. You can also try the Jolt physics plugin but I'm not sure if it'll fix the issue.
Very nice video, the animations a pretty cool :D Btw, when you set in the code to show what button to press, how can I make it show the mouse buttons like LMB or RMB? The code shows any other button, but the mouse ones it onlu shows "[]" This is the code i'm referring to: action.as_text_physical_keycode()
Heyo! So sorry for the late reply, but I found the solution! You should update the code in Interactable.gd like so: if action is InputEventKey: key_name = action.as_text_physical_keycode() break elif action is InputEventMouseButton: key_name = action.as_text() Hope this helps! Also, I'll push this code to the github repo. Thanks for the question!
hey bro, can you make a graph edit and graph node tutorial, because I have an idea to make a game engine with godot with visual script as the script component.
You made a causality dilemma because where do keys come from? And if you need a key to open a chest then where do you get the key to open a locked door? 🤯
I have a quick question: If I wanted to make it so that you had to hold down an action key for a certain amount of time and have a progress bar on the screen that shows how far along the interaction is, how would I go about that?
I've shared all the necessary information about the button in this video. However, I can understand I didn't explain some of the Godot features thoroughly. You can watch my Godot 3 interaction video for some clarity or there's also plenty of videos on RUclips explaining Godot raycasts, area3D and signals (3 of the Godot features used in this video). But yeah, I plan on making much smaller videos in the future explaining these concepts for beginners. Cheers!
You add an Area3D node to the door scene, and add a CollisionShape to the Area3D. Then attach the interactable.gd script to the Area3D, connect the signals to the door script. Boom! Profit.
5:58 i added the if collider is Interactable: line but now it wont show any prompt messages but it wont work without the line im on 4.2.2 is that why it no longer works?
can you please check if you set the raycast to ignore its parent. Because in most cases, it turns out that the raycast is constantly detecting the player's collisionShape, hence no prompt message. This setting might be different for 4.2.2, I'm not sure.
Ok, so I am not a code guru or anything so I more just want to ask a question. Couldn't you just use an Enumerator Variable and then just add the code together? Is there a better reason why you use a Custom Class, rather than an Enumerator? And could someone explain what case states would be good for Custom Class VS. Enumerator?
To be frank, I'm not that bright myself, so maybe your approach would work just as well, if not better. Can you tell me more about the Enumerator approach a bit?
@@NagiDev Well with an Enumerator, and I am only touching surface level stuff here as I am still new to coding, but as I understand it you could create an Export Enumerator String Variable with a list of object names then use a Match script in it's own function that will automatically set variables, Names, and Interact buttons, etc. under each match case. Example match string (string Var): "String name": set variables to values. Then you just put that script onto an interactable object which will then show a dropdown in the Inspector. And when you change that Enum String to whatever the object is whether it's a "Button", "Switch", "Key", etc. and each can have it's own functions, calls, and variable sets. under each match state, so you could make the key update a key count var elsewhere, or use the toggle system. This is just a rough breakdown of how I would do this. That's in part why I am asking for some case states for why you would use a custom class over an enum. Hope that makes sense. ^^ Great video though.
@@BreezyDefrag well, that seems like an interesting way to handle it. However, from my past experiences (read, blunders) I try to steer away from putting all the code in one file. With the custom class, Interactable.gd can have all the code that would be common among all the interactive objects (prompt message, interaction logic, etc), while any logic specific to an interactive object can remain in its own script. Say, you want the button to play a press animation when interacted with. That code would only remain in the button's script. Hope you see my point of view. And yes, for a very basic use case, the enumerator method seems more easier to make, I'm just trying to make the system capable of being extended and customized.
@nan0core25 Click on my name under the video to open my channel page, go to the videos tab, and you'll find the video "How to Code Player Health And Fall Damage in Godot 4" ruclips.net/video/X6gfjdXckpA/видео.htmlsi=eWXttE4eFze7ZGxp
So im getting an error after typing if collider is interactable: Prompt.text = collider.prompt_message Its rhe if statements thats not working its giving me a couldnt not parse global class error
My game immediately crashes whenever I lok at any non-interactable object once I input the code from 7:23, the replacement of interact with collider.prompt_input. I got no clue on ohow to fix this, pls help also, the game just crashes whenever I press on any surface that isnt interactable
I have just decided to copy and paste your code to not bother with the headache, thabk you for the video and everything tho, once I open my pc I will tell the error message
I mentioned it in another reply, but basically you add an Area3D node to the door scene, add a CollisionShape to it, add the interactable script to the area, and finally connect the signals like in the video.
If you don't want to rotate the raycast with the parent, you can set it as top level in the inspector, and then set it's position the same as the parent in the physics process function.
@@NagiDev thank you! I fixed it by myself yesterday, turns out my Raycast3D was actually working, it was just inside Area3D and aftwr moving it's origin a little bit away, everything got fixed
Enable debug collision shapes from the debug menu and check if the ray cast may be detecting the player body itself. Or maybe you've set the collision layer of the raycast/collision object to some other value?
This could be due to a few reasons: - you might've forgotten to define it in the interactable.gd script - maybe you named the signal differently in the script - maybe the script if not attached to the node - maybe you haven't saved the script yet, so the signal is not showing up in the inspector Please let me know if I can help, I'd be happy to do so
bro i wanna say it still feels kinda with all of this much and stuff in scene can u please make a simplified vedio for this again just implementing these systems simple scene altho it seems really goodd for future proof but as a beginner its hard pleaseeeeeee make easy and simplified one 🥲🙏🙏🙏🙏
@@NagiDev i wont say the whole vedio but for me the whole part for adding functinallity to button were difficult cuse according to me there was so much going on i could wrap my head around most of the things thats why i need a simplified verison and yeaaa overallllll great vedioooooo will ceratinly help me in future also can u make a simplified version for pickables stuff like torch will be gratefull for that 🥲🙏
@quiet5445 ah got it. So the thing is, you can define custom signals in a script which shows up in the node tab (beside the inspector) when you have the node with that script selected. In this video I created a custom signal "interacted" and connected it through the node tab to various functions in other scripts. So for example, button (Interactable.gd) -> interacted signal -> do_something() (function) Basically when the interactRay interacts with an Interactable node, the node emits the interacted signal, this signal can be connected to any number of functions in any script. So, when the interacted signal is emitted by that node, all the connected functions are called, and we can put the code we want to run inside these functions like we did in the video. I hope this helps you understand what's going on in the interaction system. If you still have doubts, feel free to contact me over at Discord @nagidev. Also, I would suggest you to learn more about Godot signals since they are really powerful for all sorts of things.
@@NagiDev thanku very much im just starting on this 3d project and your tutorial be of so much of help as there arent much tutorial on godot 4 on top of that you might not find what youre looking for altho interaction isnt that specific but still there isnt any vedio on youtube other than u that actually helped plus your the only one that replies tbh since getting replies from youtube channels nowdays is next to impossible until unless you comment on a recent vedio surely i would follow u on discord
Hi bro, your videos are really cool, I can see how much you put into each of them. I would like to ask you about shapecast nodes, what get_collider index does ask for? I really need help😢
A tutorial video that doesn't FEEL like a tutorial is my thing, great video!
Only halfway through the video but I gotta say this tutorial is top notch my man. I was pulling my hair out trying to get this stuff working but you've clarified so many things for me.
bro TYSM for these tutorials!
i never found any tutorials that are as interesting as yours tbh
This is amazing, great video man and welcome back, I hope you are planning on making more tutorials
Thank you, friend, for explaining more about what I've been confused about all this time
Awasome piece of knowlage !
Just want to say that your tutorials are great, they helped me a lot to learn Godot, thank you
Dude, your guides are great, keep up the good work, I'm looking forward to your videos about godot :)
I've been watching Godot tutorials for a while but this one is very interesting! I never thought about using an animation tree for a door!
The King returns! Also really great resource! Some of this stuff they updated in Godot 4 confused me haha, but it made sense after watching the video.
Thanks for the video) Was going to make exactly such interactions, except that I was planning to have multiple "features" of objects, one of which would be "Interactable".
Love your videos, I was worried you were gone after the long time since the last one great to see you're still at it
did you create the assets yourself or got them from somewhere? they look so nice!
Yeah, I made them myself for these tutorials. I'm glad you like it!
welcome back dude
Well made video! Thank you
lol just found your channel like 2-3 days ago and was translating all the interaction stuff from godot 3 video to my 4.2 version XD could of just clicked on your channel to find this updated one smh either way im gonna watch it!
Hey Nagi! I like your videos. Keep it up!
Excellent content bro. Sub’d within a minute. Look forward to your upcoming videos; will catch-up with your catalogue.
amazing video mr nagi keep em coming
Your videos are great, keep up the good work!
This is really well done
Amazing work. Keep it up.
You the GOAT no cap
Duuuude where have you beeen?!
Great video, also, can you do a video about enemy movement and animation?
If you do I'll subscribe :)
deal
Thank you for your tutorial. The textures in your videos look amazing. Do you create them yourself? Could you please share your workflow? How do you create the normal maps?
I'm glad you like them! Yes, I make them using Gimp and Krita. I hand paint all the textures and roughness map. For the normal maps, I draw the depth map (black is deep, white is shallow) and use the normal map filter in Krita to generate the final result.
I should probably stream my workflow someday lol.
Nagi when the player collides with a physical object, the physical object penetrates the wall or the ground. How can I fix this?
CharacterBody vs RigidBody collisions tend to be that way. I haven't found an all-in-one fix for it, but depending on your game, you can make both the player and the object be either both rigidbodies or both characterbodies. You can also try the Jolt physics plugin but I'm not sure if it'll fix the issue.
@@NagiDev jolt physics didn't fix anything the last solution make player and the object with rigidbody
Thx Nagi😊🙏🏿♥️
Very nice video, the animations a pretty cool :D
Btw, when you set in the code to show what button to press, how can I make it show the mouse buttons like LMB or RMB?
The code shows any other button, but the mouse ones it onlu shows "[]"
This is the code i'm referring to:
action.as_text_physical_keycode()
Heyo! So sorry for the late reply, but I found the solution!
You should update the code in Interactable.gd like so:
if action is InputEventKey:
key_name = action.as_text_physical_keycode()
break
elif action is InputEventMouseButton:
key_name = action.as_text()
Hope this helps! Also, I'll push this code to the github repo. Thanks for the question!
@@NagiDev No problem, thank you so much! that really helps! :D
hey bro, can you make a graph edit and graph node tutorial, because I have an idea to make a game engine with godot with visual script as the script component.
Could you make a tutorial for a pick up and drop system similar to granny ?
you should make a 3D dialogue tutorial pls
Already working on that lol
@@NagiDev thank you I love you nagidev i hope both sides of your pillow are cold tonight
You made a causality dilemma because where do keys come from? And if you need a key to open a chest then where do you get the key to open a locked door? 🤯
I did not sign up for this 😭
I have a quick question: If I wanted to make it so that you had to hold down an action key for a certain amount of time and have a progress bar on the screen that shows how far along the interaction is, how would I go about that?
Can show the blue border live player interacting with object
Sorry, I don't understand the question
do you know how to implement a mouse click into this? ive tried to do replace E with LMB or RMB and it shows up invisible
Everything was going well until the 04:31 label was not projected.
Hi! can you please share in detail the issues you're facing?
Can you give me more videos explaining the buttons in detail in Godot?
What parts would you like to know more about?
@@NagiDev You can teach the necessary knowledge or use in a platform-style game
I've shared all the necessary information about the button in this video. However, I can understand I didn't explain some of the Godot features thoroughly. You can watch my Godot 3 interaction video for some clarity or there's also plenty of videos on RUclips explaining Godot raycasts, area3D and signals (3 of the Godot features used in this video).
But yeah, I plan on making much smaller videos in the future explaining these concepts for beginners. Cheers!
@@NagiDev Thanks you so much ❤
Great tutorial, if someone can help me out tho, how would I make a door without a button? So u can just interact with the door itself.
You add an Area3D node to the door scene, and add a CollisionShape to the Area3D. Then attach the interactable.gd script to the Area3D, connect the signals to the door script.
Boom!
Profit.
@@NagiDev Ty so much man!
5:58 i added the if collider is Interactable: line but now it wont show any prompt messages but it wont work without the line
im on 4.2.2 is that why it no longer works?
can you please check if you set the raycast to ignore its parent. Because in most cases, it turns out that the raycast is constantly detecting the player's collisionShape, hence no prompt message. This setting might be different for 4.2.2, I'm not sure.
Ok, so I am not a code guru or anything so I more just want to ask a question. Couldn't you just use an Enumerator Variable and then just add the code together? Is there a better reason why you use a Custom Class, rather than an Enumerator? And could someone explain what case states would be good for Custom Class VS. Enumerator?
To be frank, I'm not that bright myself, so maybe your approach would work just as well, if not better. Can you tell me more about the Enumerator approach a bit?
@@NagiDev Well with an Enumerator, and I am only touching surface level stuff here as I am still new to coding, but as I understand it you could create an Export Enumerator String Variable with a list of object names then use a Match script in it's own function that will automatically set variables, Names, and Interact buttons, etc. under each match case. Example match string (string Var): "String name": set variables to values. Then you just put that script onto an interactable object which will then show a dropdown in the Inspector. And when you change that Enum String to whatever the object is whether it's a "Button", "Switch", "Key", etc. and each can have it's own functions, calls, and variable sets. under each match state, so you could make the key update a key count var elsewhere, or use the toggle system. This is just a rough breakdown of how I would do this. That's in part why I am asking for some case states for why you would use a custom class over an enum. Hope that makes sense. ^^ Great video though.
@@BreezyDefrag well, that seems like an interesting way to handle it. However, from my past experiences (read, blunders) I try to steer away from putting all the code in one file. With the custom class, Interactable.gd can have all the code that would be common among all the interactive objects (prompt message, interaction logic, etc),
while any logic specific to an interactive object can remain in its own script. Say, you want the button to play a press animation when interacted with. That code would only remain in the button's script. Hope you see my point of view.
And yes, for a very basic use case, the enumerator method seems more easier to make, I'm just trying to make the system capable of being extended and customized.
13:25 when make the gamestate?
Yeah, we made the gamestate autoload in the previous tutorial.
@NagiDev Hey, thanks for the awesome tutorial! Can you share the link of this tutorial? I'm stuck on this part too
@nan0core25 Click on my name under the video to open my channel page, go to the videos tab, and you'll find the video "How to Code Player Health And Fall Damage in Godot 4"
ruclips.net/video/X6gfjdXckpA/видео.htmlsi=eWXttE4eFze7ZGxp
So im getting an error after typing
if collider is interactable:
Prompt.text = collider.prompt_message
Its rhe if statements thats not working its giving me a couldnt not parse global class error
is the class name interactable (with a small i) or Interactable (with a capital I) in your interactable.gd script?
@@NagiDev with a capital I for both
Are you using capital i in your condition as well?
If so, have you saved to interactable.gd script?
Try to save and retry.
My game immediately crashes whenever I lok at any non-interactable object once I input the code from 7:23, the replacement of interact with collider.prompt_input. I got no clue on ohow to fix this, pls help
also, the game just crashes whenever I press on any surface that isnt interactable
can you share the error Godot shows on crashing?
I have just decided to copy and paste your code to not bother with the headache, thabk you for the video and everything tho, once I open my pc I will tell the error message
What if I want to open the door by directly interacting with it?
I mentioned it in another reply, but basically you add an Area3D node to the door scene, add a CollisionShape to it, add the interactable script to the area, and finally connect the signals like in the video.
@@NagiDev Oh, that seems pretty obvious haha I'm so dumb. Thank you so much for the quick reply!
@damnthishandleistaken calling people dumb is not allowed (especially when that person is yourself). You're still learning, it's okay.
I have a question, what can make Raycast3D not rotate with parent object?
If you don't want to rotate the raycast with the parent, you can set it as top level in the inspector, and then set it's position the same as the parent in the physics process function.
@@NagiDev thank you! I fixed it by myself yesterday, turns out my Raycast3D was actually working, it was just inside Area3D and aftwr moving it's origin a little bit away, everything got fixed
I am getting an error - 'GameState' not defined.
Where do i define it?
Gamestate is an autoload we coded in the previous tutorial. You can either watch that or simply copy the code from the link in the description.
Thankyou @@NagiDev
a little too fast for me i 'll just to watch it a few times. but seems really info
for some reason my raycast doesn't detect like at all
Enable debug collision shapes from the debug menu and check if the ray cast may be detecting the player body itself. Or maybe you've set the collision layer of the raycast/collision object to some other value?
my bad, i guess i have to make it a child node of the camera so it would go with my screen since i guess that's how I set up my code
If I only wanted to add the crosshair to the UI part, do I have to add script to the control node?
If you only want the basic crosshair, you don't really have to add any script.
@@NagiDev thanks!
Is anyone else unable to find the "Interacted" signal?
This could be due to a few reasons:
- you might've forgotten to define it in the interactable.gd script
- maybe you named the signal differently in the script
- maybe the script if not attached to the node
- maybe you haven't saved the script yet, so the signal is not showing up in the inspector
Please let me know if I can help, I'd be happy to do so
Oh wow, I found the fix. I overlooked 8:04... Sorry about that. Thank you so much for your help tho! you are def unrated!
bro where are u are u dead ???
bro i wanna say it still feels kinda with all of this much and stuff in scene can u please make a simplified vedio for this again just implementing these systems simple scene altho it seems really goodd for future proof but as a beginner its hard pleaseeeeeee make easy and simplified one 🥲🙏🙏🙏🙏
Sure. Can you share which parts were hard to understand?
@@NagiDev i wont say the whole vedio but for me the whole part for adding functinallity to button were difficult cuse according to me there was so much going on i could wrap my head around most of the things thats why i need a simplified verison and yeaaa overallllll great vedioooooo will ceratinly help me in future also can u make a simplified version for pickables stuff like torch will be gratefull for that 🥲🙏
@quiet5445 ah got it. So the thing is, you can define custom signals in a script which shows up in the node tab (beside the inspector) when you have the node with that script selected. In this video I created a custom signal "interacted" and connected it through the node tab to various functions in other scripts. So for example,
button (Interactable.gd) -> interacted signal -> do_something() (function)
Basically when the interactRay interacts with an Interactable node, the node emits the interacted signal, this signal can be connected to any number of functions in any script. So, when the interacted signal is emitted by that node, all the connected functions are called, and we can put the code we want to run inside these functions like we did in the video.
I hope this helps you understand what's going on in the interaction system. If you still have doubts, feel free to contact me over at Discord @nagidev. Also, I would suggest you to learn more about Godot signals since they are really powerful for all sorts of things.
@@NagiDev thanku very much im just starting on this 3d project and your tutorial be of so much of help as there arent much tutorial on godot 4 on top of that you might not find what youre looking for altho interaction isnt that specific but still there isnt any vedio on youtube other than u that actually helped plus your the only one that replies tbh since getting replies from youtube channels nowdays is next to impossible until unless you comment on a recent vedio surely i would follow u on discord
Hi bro, your videos are really cool, I can see how much you put into each of them. I would like to ask you about shapecast nodes, what get_collider index does ask for? I really need help😢