godotengine/godot
Lore
The history of this codebase, in eras.
Pre-OSS (2007 – February 2014)
Godot started out as a proprietary in-house engine at OKAM Studio, written by Juan Linietsky ("reduz") and Ariel Manzur ("punto-") for client and self-published games. The earliest commit visible in git log is dated 2013-04-10 — Add Matrix32/Vector2Array support for marshal library — but the bulk of the engine had been in development for years prior, gradually accreting features (custom 2D engine, scene tree, the precursor to GDScript) on a closed-source codebase.
The pre-OSS history was rebased into a clean snapshot before the open-source release, so the public history starts shortly before the open-source switch.
The open-source era begins (February 2014)
The defining commit:
0b806ee0fc 2014-02-09 GODOT IS OPEN SOURCEThat's the day the engine became MIT-licensed and was published on GitHub. Two days later, the very first community PRs began landing — typo fixes, a Camera2D::Rotating property, build instructions for various platforms.
The early days had the texture of any newly-open-source project: ad-hoc commit messages (hoho, ho, readme changed all on day 1), a small core team doing most of the work, and a steady stream of contributors discovering the codebase and patching the obvious things.
Godot 1.0 stable (December 2014)
Ten months after open-sourcing, version 1.0 shipped (tag 1.0-stable, 2014-12-15). The 1.x series stabilized:
- A scene-tree-based architecture where every game object is a
Nodewith an inheritance hierarchy. - Custom-built editor written in the engine itself (Godot has always eaten its own dog food).
- GDScript as the primary scripting language — Python-influenced syntax, dynamic typing, minimal runtime.
- An editor that supported Linux, Windows, macOS, and exporters for HTML5, Android, iOS.
Godot 2 (2016)
2.0-stable (2016-02-22) and 2.1-stable (2016-08-09) brought:
- A redesigned editor with docks and a more modern theme.
- Improved 2D engine; the start of seriously good 2D-first workflows.
- An asset library inside the editor.
- Better C++ modules system.
The "2D-first, 3D-also" reputation Godot still has today was cemented during this era.
The renderer rewrite — Godot 3 (2018 – 2022)
Godot 3 (3.0-stable, 2018-01-29) was the first multi-year cycle:
- Brand-new rendering engine based on OpenGL ES 3.0 with PBR materials, GI probes, and a much more capable scene compositor.
- GDNative — the precursor to GDExtension — letting native code plug into the engine without recompiling it.
- Bullet Physics as the 3D engine; the older internal physics was kept for 2D.
- Mono / C# support shipped in 3.1 (2019).
- VR support (initially via custom XR APIs, eventually OpenXR).
- The 3.x series ran through 3.2, 3.3, 3.4, 3.5, and 3.6 (the latest 3.x) — 3.6 shipped 2024-09-08, well after 4.0, because 3.x is the LTS branch many production games still use.
Some commits from this period stand out for their reach:
- 2020-06-20 —
Move Haiku platform port to external repository. Haiku was once a first-class supported platform; this was the era when several long-tail platforms moved out to make room for the 4.x rewrite. - 2022-02-08 —
Clarify SNAME usage. TheSNAME("foo")macro for cachedStringNames became standard around this time.
Godot 4 — The Great Rewrite (2023)
4.0-stable shipped on 2023-03-01 with a victory-lap commit message:
92bee43adb 2023-03-01 Bump version to 4.0-stable \o/This was a massive scope:
RenderingDevice+ Vulkan: a vendor-neutral GPU API, with Vulkan as the reference backend. Direct3D 12 and Metal followed in 4.x point releases.- Two new render paths: the clustered Forward+ renderer and the Mobile renderer.
- GDScript 2.0: optional static typing, lambdas, the
awaitkeyword, type-aware autocomplete, much faster VM. - New physics for 4.x: GodotPhysics3D was retained, but Jolt Physics arrived as a built-in module in later 4.x releases.
- New navigation servers (2D + 3D), new audio server features, new animation tree.
- OpenXR as the primary XR backend, replacing the older custom plugin model.
- C# on .NET 6 (then 8) instead of Mono on classic .NET Framework.
- Hot-reloadable native code via GDExtension, replacing GDNative.
In the rewrite, almost every subsystem was refactored in place. The git log from 2022-2023 is dense: an average of ~14-15 commits per day for two solid years.
4.x cadence (2023 – 2026)
Once 4.0 stabilized, the project moved to a fast 4.x cadence:
| Version | Released | Theme |
|---|---|---|
| 4.0-stable | 2023-03-01 | The rewrite ships |
| 4.1-stable | 2023-07-05 | Stability |
| 4.2-stable | 2023-11-29 | Polish + Direct3D 12 baseline |
| 4.3-stable | 2024-08-15 | Jolt as default 3D physics, AnimationMixer, multi-window editor |
| 4.4-stable | 2025-03-03 | Editor UX, GDScript improvements |
| 4.5-stable | 2025-09-15 | |
| 4.6-stable | 2026-01-25 | Latest stable |
| 4.7-beta | (in dev) | Current master |
The cadence is roughly six months between minor releases, with patch releases for stability.
The current commit, a0375dde96, sits on master mid-way through the 4.7-beta cycle.
What changed, what didn't
Across all eras, two things have stayed consistent:
- The scene tree. The fundamental architectural choice —
Nodes in a tree, withNodes acting as modular feature units — is the same in 1.0 and 4.7. New node types appear, old ones are deprecated, but the model survives. - The MIT license + the contributor model. Same MIT terms, same fund (the Godot Foundation since 2022), same emphasis on community-led development.
Two things that have changed dramatically:
- The renderer. GLES2 (Godot 1) → GLES3 (Godot 2/3) → RD-based with Vulkan/D3D12/Metal (Godot 4).
- The build system's reach. What once compiled for ~6 platforms now spans Linux/BSD, Windows, macOS, Android, iOS, visionOS, and the Web, with several render-path × driver × architecture combinations in each.
The CHANGELOG.md at 238 KB and the more than 3,700 lifetime contributors quantify the rest of the story: a once-personal engine became the largest open-source game engine by contributor count, and is still accelerating.
Built by Factory AutoWiki from public repository content. It is a generated preview for codebase exploration, not source-maintained documentation.