I suck at writing scripts, any good relevant tutorials?

Question

Above.

My spelling and grammar has always been excellent, that's not the problem.

Amelina

Answer 1

This is Godot 3 code but you shouldn't have a problem tweaking for Godot 4 once you learn the basics, just a matter of checking documentation in most cases and people here have been posting about stuff that has been missed out.

Carpus

Answer 2

It's not Godot at all, but I copied this dude's scripting style as much as it could be applied to Godot and it helped a ton.
Besides that, his scripting projects are fun to look at when you need an hour to do nothing and don't mind learning.

Like anything else, it's up to copying your role models and practicing.

Peltry

Answer 3

No worries, this Godot 3 code is a great starting point. When you're ready to dive into Godot 4, it's mostly about adapting and consulting the docs. Folks here have been sharing some handy tips for the stuff that might have slipped through the cracks. Keep it up and happy coding! 👍😄

Belldame

Answer 4

It's more work, but to anyone learning GDScript without previous coding experience I'd recommend also learning really any mainstream programming language. Python, C#, etc... I think (in practice!) the biggest difference between high level programming languages is syntax, the "skills" should persist regardless of what you use... But I bet you'll have an easier time understanding the basics of a more generic language that millions of people use, than a language made for one specific program and purpose :-)
As an example: there's plenty tutorials, classes, online services and so on made to teach Python to absolute beginners, but most Godot resources kinda assume that you already know how to read code. Which if you don't, chances are you'll end up copying without learning what it does.

*Plus if you learn C# you can also use it in Godot ;-) this is the end of my C# propaganda
**Also not that copying code is inherently bad, I copy my co-workers code all the time, but copying something without understanding why it worked is rarely a good idea

Semeiology

Answer 5

this right here. I did some learning on Python and that helped with GDScript, even if there are some differences, the syntax is close enough.

Honestly, the best thing to do is practice. Build little games and develop your toolset. I find that a lot of the tutorials online essentially amount to copy work. Not a terrible thing, but copy work on code doesn't make you a programmer. Just ask ChatGPT. It's much better to build a project and understand how that code interacts with everything else that will promote comprehension. Break code you find too: it's also helpful to know how things connect and what breaking them will do (ask circuit benders how that helped them learn electronics).

Someone in a dev group I was in said "you make ten bad games before you make a good one." Make a list of really easy projects, maybe watch how other people do it, then try to do it yourself.

Corelative

Answer 6

It's hard at first, but when it clicks and you understand how you need to design your code, then it's just a game of looking for the appropriate functions to use and syntax.

Ratter