// the take
Halley is a C++17 game engine built by the Wargroove developers, structured around a true ECS (components as data, systems as families of components operating over them) with pluggable rendering backends (DX11, OpenGL, experimental Metal). It's aimed at C++ developers who want engine-level control over a shipped, console-proven codebase rather than a drag-and-drop editor experience.
It has shipped a real commercial game across Windows, Switch, Xbox One and PS4, which is a much stronger signal than most hobby engines claiming console support. The ECS is a genuine data/system split, not a bolted-on afterthought, and the module boundaries (engine/plugins/tools) map cleanly onto swappable backends like DX11 vs OpenGL vs SDL. The project values fast iteration (hot-reloading, code-first workflow) over editor-generated boilerplate, which fits long-lived codebases better than engines that serialize everything through editor-owned formats.
The samples project was taken down and never replaced, so there's no working example to build from outside the engine's own test/stress projects — a real barrier for anyone evaluating it today. Console platform support (Switch, Xbox One, PS4) requires NDA'd SDKs the public repo can't include, so 'cross-platform' claims are partially unverifiable from outside. The dependency list (specific pinned versions of SDL, Freetype, yaml-cpp) plus CMake-only build with no prebuilt binaries means a nontrivial setup tax before you see anything on screen. Documentation lives entirely on an external wiki rather than in-repo, and the 'runner' tool for dynamic reloading is flagged 'highly experimental,' so a headline feature isn't actually stable.
We read the README, the directory tree and a key source file in October 2026. Nobody pays to be listed. How we judge →