Oohhhhhhhhh, if i use a seedValue to generate the points, i can reach the same pattern all the time. Also, if i put each point with differenct R i can set different strats to use like filling trees and rocks, or first rocks then trees, but rocks has radius of 15 and trees of 5, soo trees are more close than rocks in a florest like, but in a mountain i can just switch both and had more rocks together and few trees as well... Dude, i need to code this, not mind, but i will try my own version, my quadTree is not perfect, but works to me, also, my A* pathfinder almost worked, the issue was trying to use it at the same time to a really large of entitys, in the maze test that are really much more complex than any real case for now, and i not implemented path reusability or even lowering grid levels to just get arround the correct coords before getting even closer, soo, my code is kinda raw, but already works very well for a single entity going into a maze I guess i can make this as well to improve my procedural generation even further LOL

C# and C++ have a massive community so there is there, that means you just need to know what you are looking for they are not originally designed for game programming but had business and scientific backings

​@DeepDiveDevelop I never tested it but I always use typed because it helps me a lot staying between desired results. I never thought that not doing it will have a performance cost. Good to know it, thank you.

Thank you for making this video, I've heard the same answer from others when it comes to the performance gain of static typing, this help's reinforce their statements. I forgot that you could set the editor to error at non-static types, so thank you for that reminder.

I always static type everything simply for auto complete purposes.

tl;dr Use staticly typed variables bc gdscript can decide what it doesn't need to do, making everything faster. Excellent Untyped Declaration tip too. Great video, thanks. Subbed.

Static types make compile time optimization a reality also..

Hey thanks this was actually helpful even if not with performance it was with cleaner code and the video was right to the point.

nah bro. cause i really thought that it was going to be something that i didnt know, fak u 😢😢😢😢😢😢

I hate dynamic typing. Static typing just solves so many issues and, in my opinion, reads better. I think in types and values, not just values.

Good thing I mostly learned Godot not knowing how to make variables any other way than Static types

I'm slightly disappointed cause I was already using these Good video tho

Good to know, i thought is was like in python where it does not give you more performance. Also it can prevent you from generating bugs. So its probably worth all the time - even in non-performance-critical parts of the projects.

Great game and devlog! I am pretty new to Godot myself, but I am doing something similar to you--making devlogs on game jams/small projects. Good luck to you in your pursuits!

I do miss the days when you had no "variable" types and had to follow strict typing.

This simple example should be in the godot documentation with an explanation - you can use the Variant type, but with a 30% performance loss.

Personally, I use and recommend all the editor warnings, except for INFERRED_DECLARATION. As a Rust/Golang enjoyer, I simply can't understand why would inferred types ever be considered a negative thing, and the verbosity in GDScript (especially with enums) without type inference is unbearable. What really bothers me with GDScript is that static typing doesn't give you static analysis. Even if your variables are typed statically, the values assigned to them, member access, method calls, etc. are _sometimes_ evaluated only at runtime. So I need to run the game to learn that something doesn't exist because I renamed it, even though Godot knows the specific type, and should statically know that it doesn't have that member.

Wait, you Neanderthals seriously program without declaring variable types?

It's like remembering to put % after everything in QBASIC that should be an int.

How do you do the terrain creation in Asesprite at 6:38 ?

Hey that's super cool, I thought these are just type hints like in python. I guess I didn't bother reading the full manual and didn't realize these are proper static type declarations. Thanks!

There's one more important benefit, namely you will get autofill depending of type of variable/packed_scenes/texture/resource/nodes/etc. It really helps when you are using resources and classes and passing them from editor - i think its on by default but If you dont see them You access them through "Editor" -> "Text Editor" -> "Completion" -> "Add Type Hints".

Awesome. I didn't know this. Thanks. 🫡

I wondered what are the implications of using the ':'. Now I know. Thank You!

Nice video! But how are you calculating your speedup at 2:33? 1 - static_time / dynamic_time is not the speedup, idk know what that is lol. I guess the phrase A is x% faster than y is somewhat ambiguous. I guess a reasonable way to interpret that is to look at the amount of time it takes less than the base case (as a percentage of the base case). So then 40% faster than 100 would be 100 - 40%*100 = 60. Defined like that you would calculate it like this: (static_time - dynamic_time )/static_time = 1 - dynamic_time /static_time. So I guess your version is like how much more time does dynamic take than static as a percentage of static? I don't even know at this point lol, my head hurts. Also, generally speed tests in debug mode can behave pretty different than in release mode, so testing is release mode would be better. Idk how much that applies to godot, but its probably better to test for the case of a released game than a debug build. But as I said, nice video :)

I always use static typing (Haskell refugee), but it never appeared to me how much of a performance increase it is for Godot.

I came from Java(my first language), it's the only one I know before trying and started to learn Godot and GDScript a week ago. Coming from a C based language, I'm too used in declaring the data types, so I started doing that right away after finding out I can do it 😅 I'm learning Python alongside GDScript right now… I hate Py.

Bonus: If you go to Editor>Editor Settings> TextEditor > Compilation and enable "Add type hints." Every inbuilt function when you select from the snippets will also have their return type.

I am a C++ dev who uses godot. Since I learned c++ before gdscript, I can't stop declaring datatypes😅

Another advantage of static typing is intellisense support.

Thank you so much !

How would that make things faster? (Not saying it doesn’t I just don't understand how that would effect it)

does giving static return types to functions also help?

worth the watch for the knowledge that I can set untyped declarations to throw errors alone, knowing it improves performance is the icing on the cake 😂 great video, thank you for the info.

Great Video!

1:20 the first thing I noticed was that the movement was done in _process and not _physics_process

Bro WHAT I thought programmers were just being fancy and organized by doing that, nobody told me it boosted performance by 60% lmao Thank you!

thanks for the tip. i knew of static typing i just didn't know why i should use it. i have a small game underway but luckily i'm not very deep yet so i can change the code to static typing :)

You can avoid explicit types at assignment, and still get static typing, by using the shortcut: var total := 100 Instead of var total : int = 100 A little tip that reduces boiler plate when the types are already easily readable in code. ( This pattern is also in other popular languages: Kotlin, C++ (auto), etc)

I've been hammering my head against this wall trying to learn programming as a hobby for 5-6 years now. I've run across this concept of static vs dynamic typing so often and it always confused me so I just thought "I'll worry about it tomorrow I guess." Somehow this video just really simplified it and something clicked for me. Thank you!

Interesting

bro inherits from characterbody2d and uses _process function instead _physics_process where all physics objects should be, but shows amazing tip LMAO

next time just state what you're doing up-front, then elaborate on it, and i might actually believe you're a genuine person

Holy shit! Thanks man this has drastically improved my performance

I watched a couple of GDQuest videos, and he does that, but I never heard explanation. Thank you!

Huh, I thought my code was running faster because coding skills were improving. Might just have been because I swapped fully to static typing as the other languages I use also use it (TypeScript, Swift).

3:09 If you press CTRL+R, you will enable "replace". You can simply replace all "=" with ":=", and anything after a paranthesis "()" with "() -> void" to fix all errors.

Omg my prediction was spot on. Static type EVERYTHING!

Coming from Unity I already did this as standard practice, good to know this actually helps performance lol!

I'm not against type hinting and i use it all the time, i'm gainst micro optimising stuff while the issue is the used functions themselves. looking at speed of type hinted or not should be the very last optimisaiton step before you give up and go to c# or c++ to do the slow algo. gdscript is fast enough to run 10k agents through a maze if you setup the data correctly. if you just use tilemap with nav layer and navigation agents you get only 500 tho before it falls below 60 fps. even worse if you need to be able to change the maze at runtime.