Just found this channel, simple and cool editing. Good job ^_^. Also you can note that we can autoload scenes. For example I make an audioplayer autoload to play game music constantly.
just found this channel, your videos are the best on godot I have found, I hope you keep making these amazing resources. Super helpful to a beginner like me.
thank you so much for mentioning autoloads in your scene changing video. i searched for a method to save scene data across scene changes and couldn't find anything until that video lead me here also 10/10 video
Would it be favorable to make a player character an auto load function then? How would you store variables to the player and keep them the same otherwise?
If I understand correctly, you want to store variables to the player node (eg. playerHealth), and you want to access them globally/from other nodes? If that is the case, there are a lot of patterns you can follow to achieve this result: - you can do as you mentioned, which is storing the player character globally. (this may become hard to maintain/debug if a lot of nodes are making changes to the variables/fields of the player character) ~ consider using getters/setters to the variable to avoid unexpected changes. - you can use signals. For example, you can emit a custom signal when the playerHealth reaches 0. - you can access the value from the player node directly without storing it globally. For example, the parent scene, that contains the player, can have a node that accesses the playerHealth from the player node directly. (Again, this may become hard to maintain if a lot of nodes are accessing/modifying the node variables, so consider using getters/setters)
Thanks for the feedback. In later videos, I adjusted the text to be bigger, and I will make sure that the text is big and visible for future videos as well!
PLEASE never stop making these. This is S+ tier quality content ❤
For sure! Thank you! ❤
I'm new here and I agreed 💯
@@YouSupPop Thank you!
Just found this channel, simple and cool editing. Good job ^_^. Also you can note that we can autoload scenes. For example I make an audioplayer autoload to play game music constantly.
Thank you! Great use of autoloads : )
just found this channel, your videos are the best on godot I have found, I hope you keep making these amazing resources. Super helpful to a beginner like me.
Thank you! I am currently working on another one : )
Amazing for a quick revision session .
Thank you!
thank you so much for mentioning autoloads in your scene changing video.
i searched for a method to save scene data across scene changes and couldn't find anything until that video lead me here
also 10/10 video
Thank you very much!
Thanks! Hope you keep making more videos, this was very well done!
Thank you!
Nice. I wondered what Autoloads were used for and how they would actually be attached to a scene... good stuff!
Thank you!
Immensely helpful, thank you.
You are very welcome : )
informative, thanks
You're welcome!
I love your channel bro, keep it up!
Thank you!
found this top tier content by accident
Thank you very much!
Thank you, I learn new stuff!!
You are very welcome : )
i love your content, but some Graphic Text is too small,
@@hikenone Thank you, I will make sure to make the text bigger!
this might be usefull for managing multiple gamepads and players
I didn't know the viewport was the uber-parent. Feels like that has other opportunities and implications.
Thank you, Sir, 🙏🌺😇
You are very welcome, Sir 🙏🌺😇
@@JumboGamedev 🙏🌺😇
Okay though, good video but I NEED to know what your editor theme is. Looks sweet :)
I am using a custom preset:
- base color: 11124b
- accent color: ff0090
So this is how you save stats between levels?
Yes, autoloads can be used to save stats between levels.
Would it be favorable to make a player character an auto load function then? How would you store variables to the player and keep them the same otherwise?
If I understand correctly, you want to store variables to the player node (eg. playerHealth), and you want to access them globally/from other nodes?
If that is the case, there are a lot of patterns you can follow to achieve this result:
- you can do as you mentioned, which is storing the player character globally. (this may become hard to maintain/debug if a lot of nodes are making changes to the variables/fields of the player character)
~ consider using getters/setters to the variable to avoid unexpected changes.
- you can use signals. For example, you can emit a custom signal when the playerHealth reaches 0.
- you can access the value from the player node directly without storing it globally. For example, the parent scene, that contains the player, can have a node that accesses the playerHealth from the player node directly. (Again, this may become hard to maintain if a lot of nodes are accessing/modifying the node variables, so consider using getters/setters)
i can't read anything, please make the text bigger for the code
Thanks for the feedback. In later videos, I adjusted the text to be bigger, and I will make sure that the text is big and visible for future videos as well!