⚠️ Article May Be Outdated
This article was last updated 1 year 3 months ago. The content may no longer be accurate or relevant.
I’ve used Godot to make some small games (or small things that might not be games). Although each project’s development time wasn’t long and the project scale wasn’t large, I still gained quite a bit of experience. So I’m recording it here to remind myself.
If you have your own experience, feel free to share in the comments.
Efficiency
- Before making a new feature, search first to see if there’s an existing plugin. Even if it’s an outdated plugin, you can learn the approach from it.
Tips
- Use signals more, avoid cumbersome node access.
- Avoid frequently switching scenes (
change_scene_to_file()method), otherwise the performance overhead is large. Consider using aMainroot node to organize the scene tree. - Avoid high-consumption operations in
_process()(or other frequently called methods), such as loading assets. - Try to use the
@exportmethod to load nodes with complex paths, avoid writing node paths directly in scripts, so there won’t be problems after changing node paths. - Don’t forget when using GDScript that some methods already exist in C#.