Godot Fundamentals

Godot is a free, open-source game engine: a program you use to build 2D and 3D games and other interactive applications, then export them to run on desktop, mobile, and the web. It gives you an editor, a scene system, and a scripting language so you write game logic instead of building an engine from scratch. It exists to make game development accessible without licensing fees.

itSoftware engineering

Don't Panic — Godot Fundamentals

Godot is a game engine, which is the program that handles the boring-but-essential parts every game shares — drawing pixels, playing sounds, noticing collisions, reading the controller — so the person making the game can spend their time on the game rather than on reinventing physics. It is free, it is open source, and it is released under the MIT license, a permissive licence that means you can ship a commercial game and owe nobody a cut. That last part is not a small detail; it is most of why people pick it.

Before engines like this, building a game meant building the machinery under it first, which is a splendid way to spend a year and never make a game. Godot hands you the machinery and one program to work in.

There is really one big idea, and everything hangs off it: composition. You build things out of small parts nested inside larger parts. A node is the smallest part and does exactly one job — draw a sprite, hold a camera, play a sound. A scene is a bunch of nodes saved together, and here is the pleasant trick: once saved, a scene behaves like a fresh node type of its own, which you can nest inside other scenes. So a character is a scene, a level is a scene holding character scenes, and the whole running game is one big tree called the scene tree.

The parts talk to each other through signals, which is just a node politely announcing "something happened" and other code choosing to listen. A button does not know or care what reacts when it is pressed. This keeps the pieces loosely attached, which is the difference between a project you can rearrange and one that shatters when you move a node.

Here is the thing that will surprise you: the hard part is not learning the buttons. The syntax of GDScript, the friendly built-in language, comes quickly. The genuinely tricky skill is keeping your scenes independent, so they work no matter where you plug them in. Wire a scene to assume its exact surroundings and it works beautifully — until the second time you use it, when it falls over. Learn to build self-contained scenes early and you save yourself a specific, well-documented kind of grief.

One more honest warning: movement that speeds up on a fast computer means you put it in the wrong per-frame slot instead of the fixed-rate physics process. Common, fixable, embarrassing.

Where to go next: the Intro is the full guided tour, the Cheatsheet is the dense reference for when you have forgotten which renderer is for the web, and the Field Notes are the things experienced developers wish someone had told them before their first project fell over.

Don't Panic — Godot Fundamentals

Relevant careers