// the find
Redot-Engine/redot-engine
Redot Engine – Multi-platform 2D and 3D game engine
Redot is a fork of Godot 4.x that broke off in September 2024, positioning itself as a more community-driven alternative after governance tensions in the Godot project. It's a full 2D/3D game engine targeting the same audience as Godot — indie developers who want an open-source Unity alternative with no royalties.
- Inherits the full Godot 4.x codebase: years of battle-tested rendering, physics, GDScript, GDExtension API, and cross-platform export pipelines — none of that had to be built from scratch.
- Nix build support with a one-liner `nix run .` is genuinely useful for reproducible CI and contributor onboarding; most C++ game engines make you fight the build system for an afternoon.
- LTS commitment is a real differentiator for small studios that need to ship and maintain a project on a known version rather than track upstream churn.
- MCP integration for AI tooling in the editor is an interesting direction, and being a smaller project means they can move on things like this faster than Godot's larger consensus process would allow.
- The differentiation from Godot is still mostly vibes. The README is essentially Godot's README with the name swapped. After nearly two years, the actual technical delta — engine changes, new features, backported fixes — isn't visible from the outside.
- 5,900 stars with 312 forks is a poor ratio for a game engine fork. It signals the stars are mostly solidarity votes from the 2024 controversy, not active users building games with it.
- The ecosystem gap is brutal: Godot has 90k+ stars, thousands of plugins, hundreds of tutorials, Stack Overflow answers, and YouTube courses. Redot inherits none of that mindshare, and a developer who hits a wall will find almost no community help specific to Redot.
- A fork born from governance drama rather than a concrete technical vision has a shaky long-term outlook — contributors who showed up to protest Godot's CoC decisions are not the same as contributors who show up to fix renderer bugs or maintain the physics backend.