Every game runs on an engine: the renderer, physics, audio, scripting and tools that turn code and assets into something playable. Studios have built their own engines to push their games forward, and those engines have shaped whole genres. The early first-person shooter grew out of id Tech, grand strategy runs on Clausewitz, and open-world action games run on Anvil. If you know how engines work, you understand how games are made.
MYCPLUS has covered game development since 2004, and this section is built around in-depth game engine profiles. They cover the in-house engines of the biggest studios, the open-source C++ engines you can download and build today, and the classic and discontinued engines that came before them. Each profile covers how the engine works, the version history, a checked list of the games built on it, and where it stands in 2026, including what to use when an engine is no longer available.
Alongside the profiles you’ll find guides to choosing an engine and a language, graphics programming with DirectX, and complete C++ game projects with tested source code. Whether you’re picking a toolset for your first game, studying engine source code or researching the technology behind a game you love, start here.
Why MYCPLUS: One of the web’s largest collections of game engine profiles, maintained since 2004. Every profile checks its game list against named sources, corrects the myths copied elsewhere, and states each engine’s status in 2026. For the language behind most of these engines, see the C++ Programming tutorials.
Real Virtuality powered Operation Flashpoint, Arma and VBS for over a decade. Here’s how it worked, each generation, what replaced it, and the 2026 open-source release.
Shark 3D was a Munich-made real-time 3D engine best known for Dreamfall and for live editing on consoles. Here’s how it worked, what was made with it, and what replaced it.
OpenClonk is the community’s open-source continuation of the German Clonk series, a 2D game and engine scripted in C4Script. Here’s how it works, a tested script, and its status.
Limon is a one-developer, open-source C++ engine for first-person games, with an editor, physics and Python scripting. Here’s what it does, its new render pipeline and its status.
Armory is a free, open-source 3D game engine that runs inside Blender. Here’s how its Haxe engine works, a tested trait example, its features, and where it stands in 2026.
Gamebryo powered Oblivion, Fallout 3 and Civilization IV. Here’s its history from NetImmerse to Gamebase, how its NIF files work, the games built on it, and its status today.
Stratagus is the free, open-source RTS engine behind Wargus. Here’s its history from FreeCraft, how its Lua game data works, a tested external-AI example, and its status today.
The C4 Engine is Eric Lengyel’s commercial C++ game engine. Here’s its history through the Tombstone years, how it works, its OpenGEX format with a tested example, and where it stands now.
Stockfish is the strongest free chess engine. Here’s its history from Glaurung, how its search and NNUE evaluation work, a tested Python example, and what’s new in Stockfish 19.
Godot is the free, open-source engine behind Slay the Spire 2. Here’s what’s new in Godot 4.7, how scenes, nodes and GDScript work, a tested example and how it compares.
DX Studio was a Windows tool for interactive 3D games and simulations, with editors, JavaScript and DirectX 9. Here’s how it worked, what it cost, and what to use instead.
ClanLib is a long-running open-source C++ toolkit for 2D games. Here’s what ClanLib 4.2 includes, how it changed from version 3, a working example and the alternatives.
