What to compare
- project type and target platforms
- engine version and release channel
- scripting and automation interface
- import, export and asset pipeline
- licence for engine, scripts and assets
Read the sources
Godot Engine documentation ↗
The official manual and class reference for the Godot 2D and 3D game engine, including scripting and export guides.
Public documentation. The stable and latest branches can differ; select the one that matches the engine version in use. The engine is MIT-licensed and the documentation is CC BY 3.0. Plugins, assets and templates keep their own licences.
Godot download archive ↗
Every official Godot release, including development, pre-release and release-candidate builds, with links to release news and changelogs.
Read the news and changelog for the exact build. This collection downloads nothing. Treat development and pre-release builds as test material. Back up a project before opening it in a newer engine version.
Blender release notes ↗
Release notes for each Blender version, including long-term support releases, with links to detailed notes such as Python API changes.
Public pages. The detailed notes and the Python API reference are on Blender's developer and documentation sites, which can show a browser check to automated readers. Blender is GPL software, and Blender states that published scripts using its Python API must use a GPL-compatible licence.
Babylon.js documentation ↗
Guides, API reference, what's new and breaking changes for the Babylon.js web rendering engine.
Public documentation. Read the breaking changes page before moving a project to a new major version. The documentation states that its code samples are Apache 2.0 unless otherwise stated. Check the terms of models and textures separately.
Babylon.js releases ↗
Tagged Babylon.js releases with change notes from the official repository.
Read the release notes on GitHub, or use the GitHub Releases API with its request limits. Apache-2.0 licensed. Pin the package version and compare rendered output before upgrading a published scene.
When to look again
At project start, before a major engine upgrade, and when a required platform or export format changes.
Give your agent this question
Compare the named engines for the supplied project. Cite official documentation for scripting, export and platform support, note version-specific limits, and propose a small prototype that tests the riskiest requirement. Do not install or download anything.