Learning new features

Godot is a feature-rich game engine. There is a lot to learn about it. This page explains how you can use the online manual, built-in code reference, and join online communities to learn new features and techniques.

Making the most of this manual

What you are reading now is the user manual. It documents each of the engine's concepts and available features. When learning a new topic, you can start by browsing the corresponding section of this website. The left menu allows you to explore broad topics while the search bar will help you find more specific pages. If a page exists for a given theme, it will often link to more related content.


The manual has a companion class reference that explains each Godot class's available functions and properties when programming. While the manual covers general features, concepts, and how to use the editor, the reference is all about using Godot's scripting API (Application Programming Interface). You can access it both online and offline. We recommend browsing the reference offline, from within the Godot editor. To do so, go to Help -> Search or press F1.


To browse it online, head to the manual's Class Reference section.

A class reference's page tells you:

  1. Where the class exists in the inheritance hierarchy. You can click the top links to jump to parent classes and see the properties and methods a type inherits.

  2. A summary of the class's role and use cases.

  3. An explanation of the class's properties, methods, signals, enums, and constants.

  4. Links to manual pages further detailing the class.


If the manual or class reference is missing or has insufficient information, please open an Issue in the official godot-docs GitHub repository to report it.

You can Ctrl-click any underlined text like the name of a class, property, method, signal, or constant to jump to it.

Learning to think like a programmer

Teaching programming foundations and how to think like a game developer is beyond the scope of Godot's documentation. If you're new to programming, we recommend two excellent free resources to get you started:

  1. Harvard university offers a free courseware to learn to program, CS50. It will teach you programming fundamentals, how code works, and how to think like a programmer. These skills are essential to become a game developer and learn any game engine efficiently. You can see this course as an investment that will save you time and trouble when you learn to create games.

  2. If you prefer books, check out the free ebook Automate The Boring Stuff With Python by Al Sweigart.

Learning with the community

Godot has a growing community of users. If you're stuck on a problem or need help to better understand how to achieve something, you can ask other users for help on one of the many active communities.

Il miglior posto per fare domande e trovarne di già risposte è il sito ufficiale Domande e Risposte. Queste risposte appaiono nei risultati del motore di ricerca e vengono salvate, permettendo altri utenti di beneficiare dalle discussioni sulla piattaforma. Appena hai fatto una domanda lì, puoi usare il suo link in altre piattaforme social. Prima di fare una domanda, assicurati di controllare risposte già esistenti che potrebbero risolvere il tuo problema su questo sito o utilizzando il tuo motore di ricerca preferito.

Formulare bene le tue domande e provvedendone i dettagli aiuterà gli altri a darti risposte migliori e più veloci. Raccomandiamo di includere le seguenti informazioni quando si fa una domanda:

  1. Descrivi il tuo obbiettivo. Dovresti spiegare cosa stai cercando di ottenere tenendo in conto il design. Se stai avendo problemi nel far funzionare una soluzione, potrebbero esserci diverse, più semplici soluzioni che raggiungono lo stesso obbiettivo.

  2. If there is an error involved, share the exact error message. You can copy the exact error message in the editor's Debugger bottom panel by clicking the Copy Error icon. Knowing what it says can help community members better identify how you triggered the error.

  3. If there is code involved, share a code sample. Other users won't be able to help you fix a problem without seeing your code. Share the code as text directly. To do so, you can copy and paste a short code snippet in a chat box, or use a website like Pastebin to share long files.

  4. Share a screenshot of your Scene dock along with your written code. Most of the code you write affects nodes in your scenes. As a result, you should think of those scenes as part of your source code.


    Also, please don't take a picture with your phone, the low quality and screen reflections can make it hard to understand the image. Your operating system should have a built-in tool to take screenshots with the PrtSc (Print Screen) key.

    Alternativamente, puoi usare un programma come ShareX su Windows oppure FlameShot su Linux.

  5. Condividere un video dell'esecuzione del tuo gioco può davvero essere utile per risolvere i problemi del tuo gioco. Puoi usare programmi come OBS Studio e Screen to GIF per registrare il tuo schermo.

    Puoi usare servizi come streamable o un cloud provider per condividere gratuitamente i tuoi video.

  6. Se non stai usando la versione stabile di Godot, per favore menziona la versione che stai usando. La risposta può essere differente in base alle caratteristiche a disposizione e l'evoluzione continua dell'interfaccia.

Seguire queste linee guida massimizzerà le probabilità di ricevere la risposta che stai cercando. Risparmieranno tempo sia a the che alle persone che ti stanno aiutando.

Tutorial della comunità

This manual aims to provide a comprehensive reference of Godot's features. Aside from the 2D and 3D getting started series, it does not contain tutorials to implement specific game genres. If you're looking for a tutorial about creating a role-playing game, a platformer, or other, please see Tutorial e risorse, which lists content made by the Godot community.