finds.dev← search

// the find

Jenova-Framework/J.E.N.O.V.A

★ 683 · C · MIT · updated Aug 2026

Projekt J.E.N.O.V.A is a comprehensive series of components for Godot Engine expanding its capabilities with cutting-edge technologies.

J.E.N.O.V.A is a set of Godot 4.2+ tools for writing game or app logic in C++ 20/23 and running it the way GDScript or C# scripts run, with an interpreter, hot reload, and editor integration. It suits Godot developers who want native C++ and are on Windows x64 or Linux x64 and willing to set up a compiler toolchain. This repo is the umbrella project: the runtime lives in a submodule, and several of the listed components are closed source.

The Runtime and SDK are MIT-licensed and split into their own repository, so the interpreter and script-instance code can be read and reused without the commercial parts. Compiler support is broad on paper: MSVC, clang-cl, MinGW, LLVM Clang and GCC, with multi-threaded compilation and source caching, which matters once a project has more than a handful of C++ scripts. Debug information and auto-debugging setup for Visual Studio and VS Code mean scripts can be stepped through in the editor, which most C++-in-engine attempts skip. The Carbon design, which takes reflection from a compile-time analyzer instead of macros, is the most technically interesting idea here and the right direction for binding C++ types into an engine.

The visible tree is thin: a license, a README, a Windows installer script in C, and a submodule pointer to Jenova-Runtime, so the code most people would read is one hop away. Only Runtime, SDK and Blade are MIT. RTX, Fibers and the Emulator are proprietary, Carbon and the IDE are under PJPL1, and the open part is narrower than the banner suggests. Support stops at Godot 4.2+, Windows 7 to 11 x64 and Linux x64, with Mac and web still planned. The README leans on claims such as 'Next-Gen Hot-Reloading', '100+ utility functions' and 'Compatible with All Engine Forks', and it links no tests, benchmarks or compatibility matrix, so treat them as the author's assertions until someone checks them.

View on GitHub → Homepage ↗

// want more like this?

We dig through GitHub every week and send a few repos picked for what you actually care about — each with an honest take like this one.

Get finds in your inbox → Search again →