Видео

This tutorial only teaches the actual interaction mechanism. For multiplayer games you would have to manage the interaction state across the host and client depending on how you've structured your project.

I'm trying 😭

@@NagiDev np bro you probably busy with other stuff hope so next vid will be soon and Fantastic 🤙 edit:- please cover these topics - Sprint & stamina, enemy & Npc, it would be helpful

@Husk947 I'm working on NPC tutorial rn lol!

@@NagiDev maybe i saw a npc interaction in old godot 3 interaction tutorial so if you can make tutorial on enemy would be more important ig although npc is also cool

I'm not sure I understand

I guess QuickEdit seems like a similar app, although I haven't used it so I can't guarantee it will work

Yes, you'll have to use 2D variants of the nodes and update the code a bit and it should work.

What do you mean by that?

@@maxgevanssomething like @onready var db: DialogueBox = $CanvasLayer/DialogueBox

Its an autoload script that I created in the previous tutorial.

@NagiDev OK thx ( you r so fast wtf 🤣 )

hehe I just have a terrible upload schedule don't worry

Have you tried to select the DialogueNode and press delete key?

@@NagiDev Wow thanks for answering so quick :D - Sorry just figured out now. For Mac users, you can't just press Command + Backspace (as used to delete nodes and other things). In this case in particular, to delete Dialogue nodes, I had to press Fn+Backspace, then it worked. Again thanks for answering quick :))

@Vezu09 I'm sorry I don't have a mac so I haven't really tested the plugin over there. Feel free to contact me if you need any assistance with the plugin. I'm happy to help!

@@NagiDev Thank you for your concern, no problems, all sorted out :)

skill issue tbh lol

hehe

Now come back, it's been 5 months already 😂

I'm trying but video editing is hard 😭

@@NagiDev ik, I've been stuck on the intro of my first video for a few weeks now 😭

What version of Godot are you using?

@@NagiDev 3.5

You didn't write .x and .z after MoveDir. You code should look like: velocity.x = lerp(velocity.x, MoveDir.x * speed, accel * delta) velocity.z = lerp(velocity.z, MoveDir.z * speed, accel * delta)

@@NagiDev Thank you so much 😁

The easy method (which I used) is to open the gltf as an inherited scene, copy the mesh instance and paste it in your scene. An even easier solution is to just drag and drop the gltf in your scene.

yup I missed that part lol

Pretty much, yeah

If you don't want the button to be visible you can just skip the step of adding a mesh to it

@@NagiDev i mean, after interacting with it, i want it to go invisible. how exactly would i go about that?

To make the button invisible after interaction you can call hide() or $Button.hide() at the end of the _on_interacted() function that is triggered by the interacted signal. However the button would still be interactive even after being invisible. To prevent that, you can simply call queue_free() instead of hide() to delete the button after interaction; or you can create a variable to store whether the object is interactive or not and set it to false on interaction.

Will do! I'm just struggling to find motivation to get back to making more tuts

@@NagiDev ah rip I feel yah, any cool projects or what not?

nop, just sitting lol

@@NagiDev rip :c

Heyo! Can you please compare your code with the code I shared in the description? If you still can't figure it out feel free to contact me over discord and I'll see what I can do to help!

You can customise the look of each element through Godot's theming system. You can read the documentation for that or watch some tutorials (although it's pretty easy to pick up).

@@NagiDev ohh ok I get it, I had to add a whole theme to the DialogueBox node, not just theme override

Your raycast is detecting a CSGBox and trying to get the prompt_message property from it. Enable "show collision shapes" from the debug menu and check if the raycast is detecting another object in the way.

Also, did you skip the condition check in the code? Please check if you skipped some part of the code as that may explain this error.

@@NagiDev Thanks it works

this could mean either of these scenarios: - you haven't attached the script to the object - the raycast is detecting another object in the way - you skipped the condition checks in interactRay script - you probably misspelt the word somewhere Try to compare your code with the one in the description to see if you missed something?

@@NagiDev Still, doesn't work. Thanks for the tutorial anyway.

@@NagiDev Never mind the raycast detects another object. How can I prevent the raycast from colliding to another object?.

You can put the object on a different collision layer and make it the raycast's mask to that layer. But I must warn you this way your raycast would be able to detect objects through walls.

Does it just freeze the player or does Godot throw an error message as well?

​​@@NagiDevon mobile u cant see error message on a crash as u have to close the whole program something I hope they fix. After looking letter by letter I eventually saw I put state_value instead of set_value in the game state.gd that was a annoying 30 minute mistake, my bad!

yeah, game didn't get enough downloads lol

For anyone with a similar issue, I've figured it out. While the variables are stored in the dialogue tree resource, that is not where you want to update them. If you do, you will have to set the dialoguebox.data to null and back to the dialogue tree. This is because the variables are set in the dialoguebox in the set function of the data variable. So instead you can modify the variables stored on the dialoguebox node instead.

The variables are stored in $DialogueBox.variables, however, you must note, their initial value at the start of the game would be the ones you set from the dialogue editor, and when changed during a dialogue by the Set node would have those changes for the rest of the game (only resetting once the game closes) just like amy variable in a gd script. If you want to set one of the variables to a value outside of the dialogue data, in the ready function, you can simply do: func _ready(): $DialogueBox.variables["COINS"] = player_coins here, change the key "COINS" and variable player_coins accordingly. To synchronise the values across the variable stored in the DialogueBox and the variable in a script (say player.gd) make sure to either: 1. Simply copy the variable value back to the script at the end of the dialogue (by connecting the dialogue_ended signal) func _on_dialogue_ended(): player_coins = $DialogueBox.variables["COINS"] 2. Or connect the variable_changed signal and update your variable there: func _variable_changed(key, value): if key == "COINS": player_coins = value Hope this clarifies the issue!

It took me a long time to edit 😭😭