Declutter Your Godot 4 Project: Singletons/Autoloads All Over The Place... 

does this mean that preload approach will reset all variables on scene change and class_name approach will persist throughout whole app run?

What if you need to reset the counter at any instance, where would it be the best place to do so?

thanks, the preload felt clunky for someone with a oop background, this is perfect

Thanks for the suggestion :) Will keep it in mind.

Firebelley Games has a video that was key to me starting to understand composition. ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-rCu8vQrdDDI.html Would recommend

@@GdquestPlease! this is probably one of this biggest things i struggle with after switching from unity to godot

Me too!

The best one I had seen so far for composition was this one: ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-74y6zWZfQKk.html How You Can Easily Make Your Code Simpler in Godot 4 by Bitlytic

Not really sure I understand this. Doesn't this just mean creating two Autoload Singletons? The event bus and the "Singleton Death Handler"?

@@bahamajo the global event bus should be an autoload (an established pattern) , the statistics manager can be wherever's appropriate. This stats management depends on your games needs. The idea here isn't "Singleton/autoloads need to be avoided" it's that "error prone design patterns and leaky abstractions need to be avoided". If you were directly changing autoload members from another class, this would also be an anti pattern. Improper uses like these led to autoloads being loathed. When you avoid accessing member variables directly and only mutating state through async events (or at least methods), your system is easier to maintain and refactor later. This is typically summed up as the "Law of Demeter". Static variable usage may make sense in some use cases, but in general if you have other "non owner" classes manipulating these, it can be more error prone and harder to keep track of what's going on (and refactoring challenges mentioned above). Please feel free to ask anything else or if this perhaps was unclear.

Thanks for the feedback @@KyleLuce!

Note that this applies everywhere in programming, not only in game programming. It's strange that, in every other programming field (e.g. Web dev), global variables are banned and mostly avoided, meanwhile here in the game dev industry people make tons of tutorials on how to use them without explaining the downsides.

@@KyleLuce Event bus is a really powerful pattern. I use it all the time, it's a pillar of maintainable code in Godot, along with StateMachines and Composition over Inheritance.

would the syntax for that be like this? var VariableName: ClassName.static_var = variable

​@@Ichthyoid it would be: var VariableName: Type = ClassName.static_var

Daniel's example is correct as for testoftestris: tested earlier today to verify and yep you can just use ClassName.StaticVar from any node in the scene, even if none of the nodes present in scene are said class. The remote view won't show static variables in playtest as far as I can tell so one of those debugging plugins or just classic print() will be how you peak at it in playtest. (Please feel free to prove me wrong, i can easily have missed it but I spent a solid few minutes looking and not seeing any mention of it in the remote views or in debugger)

class_name Mob static var deleted_count := 0 static var hurt_count := 0 ... If you use a class name, you can avoid using preload(), and you can access Mob.deleted_count or Mob.hurt_count from anywhere in the project.

I hear you. We've actually used it to make multiple apps and we love it too. The whole workflow is pleasant from fast prototyping with a visual editor, to UI design, and the OS abstraction is excellent. Definitely planning a course. I would really appreciate it if at some point you could send me an email at nathan@gdquest.com describing your needs. It might help focus the curriculum when we get to it (GDQuest is a very small team...). Thanks for the comment and the trust. :)

@Gdquest alright ill send an email today thanks for replying fast.

Probably, if there are no other instances which could held the values, then static variables are gone

Agreed

On this channel. Watch our latest Short for a roadmap. ru-vid.comv7d8uYw59jk If you know Python, Godot will feel natural to you because GDScript is basically Python for Gamedev.

Yes, you will have to write the saving system though of course.

Are you referring to your own app or our app to Learn GDScript?

Your application for learning gdscript

We have no plans to port it to android in the immediate future for reasons related to reposiveness and the editor.

nice!

Thank you!@@qingxian3870

@@psilon6999 yes I did! I found it to be a great course, and I fully recommend it. Everything he taught has stuck with me and I feel much more confident in engine.

Welcome :)

They will be different even if identically named. Each has its own scope limited to its class. But you can still access static variables of some class from anywhere by preceding the variable by its class name.

Generally you can do whichever seems simplest to you and see if you have a problem. But you do always need to set an owner on nodes you want to save. We'll consider a video on the subject!

​@@GdquestHI, Sorry I took so long to reply. Thank you for considering a video on the subject, I look forward to it. Again sorry for the way long timeframe.

Sure. I will link it in description.

Yes

You can use static functions

@@Gdquest oh, sorry for misunderstanding. I thought about some kind of function that would activate per each class instance when called from somewhere. For now the only option is to use singleton for that so it require a lot more extra code.

Godot 4.1 and later.

Shaming people for using something that you personally do not like is not a way to get them on your side. I prefer gdscript myself, but have used many languages before, even C# for years. It is just a matter of preference, but for me it is for the efficiency and speed at which I can write gdscript. But each language has its pros and cons. Cheers.

Advocating that people consider DSLs toys would not improve industry standards. As a gamedev specific language, GDScript works well for most use cases and when it's needed, we use C++ or C#. But feel free to use C# across the board. Industry standard should evolve to recommend what is most applicable to your use case. Languages, like engines, are tools: means to an end. If your preference is to pick up and stick to only one tool, by all means.

@@Gdquest you position yourself as one of the (if not THE ) main advocates of the engine, you have quite a big following and basically you seem to make a living mostly from the work around the engine. On the same hand you completely neglect such important topics as real-world usage of the tools and what industry actually needs. Do you really believe strong players, like companies or studios will switch their workflow to a semi-scripting language developed in recent yeards, with no serious tooling around it (debuggers, profilers, analyzers, refactoring) for all their codebase? From what we might observe is - you are targeting mostly solo-devs or ocassional users who just tinker with the engine from time to time, building toy games over the weekend. Have you ever considered focusing more on de-facto standards like .NET or maybe even C++ - and filling that missing gap for some serious usages of the engine? No offense, but right now, sugar-like graphics, bouncy vibrant music and python-simple-like scripting would mostly attract people entering game development - but if that's your ACTUAL target audience, not the A-AAA studios, and I am all wrong - I am taking my words back then...