Game engines

Specs, license, and export targets. Open a card for the write-up and any matching source.

A browser-based 2D editor. Event sheets build the game. Publishing a commercial project needs a paid plan.

JavaScript. Proprietary. 2D.

A visual-novel engine. Dialogue, sprites, and choices are the tools. The engine is MIT.

Python. MIT. 2D.

A Lua 2D framework. You write the game loop yourself. There is no scene editor.

Lua. Zlib. 2D.

A 2D and 3D editor aimed at mobile and web. Gameplay is TypeScript. Read the engine repository license before you treat a build as MIT.

TypeScript. Source-available. 2D/3D.

An MIT C# framework in the XNA shape. You own the game loop, content pipeline, and tools.

C#. MIT. 2D/3D.

A Java game framework. Desktop, Android, and web share one codebase. There is no editor in the box.

Java. Apache-2.0. 2D/3D.

A small C library for 2D and 3D. One header, immediate-mode drawing, no editor.

C. Zlib. 2D/3D.

A data-driven 2D engine. Config files describe objects, and C or C++ is the game code.

C++. Zlib. 2D.

An MIT 3D engine with an editor and C#. Formerly Xenko.

C#. MIT. 3D.

A Rust game engine with an editor. 3D is the main path. 2D is supported.

Rust. MIT. 2D/3D.

A BSD 3D engine used from Python or C++. Scene graph and assets, not a full visual editor.

Python, C++. BSD. 3D.

An Apache-2.0 3D engine from the Open 3D Foundation. The install and the toolset are large.

C++. Apache-2.0. 3D.