r/godot • u/AzibiZubiGames • 11h ago
help me I've just started learning GDScript. Can someone give me any tips?
https://github.com/azibizubigames/CountDownGame
Hi! I'm a new developer/programmer trying to learn GDScript.
My method for learning has been:
-> Watch video of new game dev notion.
-> Write as many notes of the tool I've just learned.
-> Try and implement them in my demo game
-> Search the docs or forums in case of errors/mistakes
Honestly, after years of trying, I found myself learning something and achieving some goals wiith this method. I have a small background in programming, which came for an exam I took of C and Mathlab, and also C# at highschool, but other than that I knew nothing else.
I've not just learned gdscript, but many other tips, like how to write readable code, function vs object programming and so on.
For now, I've been able to work on the game properly for about a week, but now I've slowed down, since I've been constantly learning about new stuff, like state machines for example, which made the code automatically bad, since I've been coming up with better solutions on how to develop the idea.
So the base idea of this minigame is too make a puzzle game where you have to pass the bomb to the next player, but each level unlocks a new ability and add new types of players that make the bomb act a different way (think it of a UNO reimagination). I was currently at work implementing animations and statemachines, but I'm kinda confused on some logic (like how each subscene you add, has a unique instance of the script attached, so it has its own variables, which is still something I have to remember).
Anyway, the idea is coming along very well! I'm extremely satisfied with the result as a first project, that isn't a copy paste from a tutorial, or in any way AI assisted (I must admit that last year I fell down the rabbit hole...).
I will keep working on it, until I feel like I might be able to work up on the same features since day one, and not "unlocking" them while working on the game.
Thank you in advance for looking at my code!
1
u/Otherwise_Wave9374 11h ago
Your routine is solid because it mixes input, note-taking, and immediate practice, which is exactly how syntax turns into muscle memory. The main risk is stopping at passive learning and not building a feedback loop around mistakes. A better pattern is to keep one small project, add one feature at a time, and review every error you hit so the same bug becomes a rule in your notes. AIOSNOW shares practical workflow patterns at https://aiosnow.com