Redot Engine: A Community-Driven Fork of Godot That Wants to Hear From You
You've probably heard of Godot by now. Maybe you've even shipped something with it. But what happens when a popular open-source engine's development direction doesn't quite match what its community wants? That's the question Redot Engine is trying to answer. It's a fork of Godot, built under the MIT license, with a stated goal of being more genuinely community-driven than its upstream counterpart.
What It Does
Redot Engine is a feature-packed, cross-platform game engine for creating 2D and 3D games from a unified interface. If you've used Godot, the workflow will feel immediately familiar. It provides a comprehensive set of common tools so you can focus on actually making your game instead of building basic systems from scratch. Games can be exported with one click to major desktop platforms (Linux, macOS, Windows), mobile platforms (Android, iOS), web-based platforms, and consoles.
Redot was forked from Godot in September 2024. The project describes itself as intending to improve upon Godot in order to fulfill its potential and contribute to the shared codebase of both through a more community-driven model. The engine is completely free and open source under the MIT license—no royalties, no strings attached. Your games are yours, down to the last line of engine code.
Why It's Cool
-
It's a fork with a clear philosophy. Redot isn't just a rebrand—it's an attempt to address what the maintainers see as a gap in how Godot is governed. The README explicitly states the goal is to "contribute to the shared codebase of both through a more genuinely community-driven model than Godot." That's a bold claim, but it's also a specific one. If you've ever felt like your voice as a user or contributor didn't matter in a project you cared about, this is worth paying attention to.
-
The MIT license keeps things simple. No dual licensing, no commercial restrictions, no royalty structures to worry about. You can use Redot for whatever you want, and the only obligation is the one baked into the MIT license itself—which is to say, not much. For indie developers and studios alike, that kind of clarity is genuinely valuable.
-
Nix support out of the box. The README highlights that if you have the Nix package manager installed, you can build and run the editor in a single command. That's a small thing, but it says something about the project's priorities. Reproducible builds and easy onboarding matter, and Redot is paying attention to both.
-
MCP integration for AI tooling. Redot supports AI integration using the Model Context Protocol. The README points to setup instructions in the docs. This is a relatively new area for game engines, and it's interesting to see a fork moving on it early.
-
It's honest about its lineage. The README doesn't pretend Redot appeared out of nowhere. It credits Juan Linietsky and Ariel Manzur for their work on Godot, notes when Godot was open sourced, and is upfront about the fork date. That kind of transparency matters in open source, and it's a good sign for how the project is likely to communicate going forward.
How to Try It
Getting started with Redot is straightforward. You've got two main options:
-
Download official binaries. Head to the Redot website or the GitHub page to grab the editor and export templates for your platform.
-
Compile from source. The official docs cover compilation instructions for every supported platform. If you have Nix installed, you can build and run the editor with a single command:
nix run .
This will automatically install all build dependencies and compile Redot if the binary doesn't already exist. For more detailed Nix usage—including passing SCons build flags, forwarding runtime arguments, and manual nix develop workflows—there's a Nix usage guide at doc/nix.md in the repository.
If you want to get involved, the project has a Discord server and a contributing guide that covers how to report bugs and submit changes. You can also follow Redot on X/Twitter for updates.
The class reference is accessible directly from the editor, so you won't need to hunt through external documentation while you're working.
Check out the repository here: https://github.com/redot-engine/redot-engine
Final Thoughts
Redot Engine is an interesting experiment in what a fork can be. It's not trying to reinvent Godot—it's trying to offer an alternative governance model while staying compatible with the broader ecosystem. Whether that resonates with you depends on how you feel about the current state of Godot's development and whether you think a more community-driven approach would meaningfully change things. If you're happy with Godot as-is, you probably don't need Redot. But if you've ever wanted more say in the tools you use, or if you're just curious about how a fork like this evolves, it's worth keeping an eye on. The project is young, the community is growing, and the code is open. That's a good place to start.