Godot explained: how nodes and scenes support cross-platform game development

Godot is a cross-platform engine for 2D and 3D games whose editor, runtime, and much of its tooling are developed in public. The repository had about 114,470 stars when collected, and maintenance release 4.7.1 addressed stability and usability in July. Its defining choice is the node, scene, and signal model, paired with an MIT license that permits source changes and royalty-free distribution.

Typical uses include independent 2D games, small and medium 3D work, teaching prototypes, interactive exhibits, and products that need custom engine modules. The editor brings scene construction, animation, scripting, imports, debugging, profiling, and export into one application. GDScript supports a short iteration loop, C# is an official option, and C++ or GDExtension can handle lower-level extensions.

A Node represents one focused object, while a Scene stores a reusable tree of nodes. At runtime the main scene joins the SceneTree, which drives lifecycle callbacks through parent-child relationships. Signals connect events without forcing the sender to know the receiver. Rendering, physics, audio, and navigation use dedicated servers. Larger projects still need rules for scene boundaries, resource ownership, and autoloaded singletons.

The engine is mainly C++ and builds with SCons. GDScript is closely integrated with the editor, while the C# build depends on .NET. The repository contains platform backends, render drivers, the scene system, editor, modules, and third-party code. Godot does not require a traditional ECS. Performance-sensitive work may use fewer nodes, direct server APIs, or native extensions, and the Forward+, Mobile, and Compatibility renderers expose different capabilities.