Descent3 is the open-source, GPL-3.0-licensed engine for Descent 3, the game from Outrage Entertainment, published for players and developers who already own the original game files and want to build, run, and maintain the engine from source.

What it is

This repository is the open source engine behind Descent 3, the codebase originally developed by Outrage Entertainment and released here under GPL-3.0. It is written in C++ and sits in the registry under Miscellaneous / Gaming, tagged with the topics cplusplus and game-engine. The tree also carries the "1.5" patch written by Kevin Bentley and Jeff Slutter several years ago, which the Descent community has since brought to a stable condition for this release. At the time of listing the project has 3,019 stars, 293 forks, and 45 open issues.

The problem it solves is one of ownership and maintainability. The engine was previously something players received only as a shipped, closed binary: it could not be read, rebuilt, or patched by the people using it. This release puts the engine source in public hands so the community can compile it, carry the 1.5 patch forward, and resolve build and runtime problems in the open. It is deliberately an engine release rather than a game release; as the README states plainly, "In order to use this, you must provide your own game files." The content remains the user's responsibility, and USAGE.md describes how it is supplied.

Key capabilities

• A complete C++ game engine codebase, catalogued in the registry under the cplusplus and game-engine topics.
• Distribution under GPL-3.0, with the licence linked directly from the README.
• Inclusion of the "1.5" patch by Kevin Bentley and Jeff Slutter, stabilised by the Descent community before release.
• A bring-your-own-content model: the engine does not ship game data, and USAGE.md covers installation with the files the user provides.
• A documented build path in BUILD.md for compiling the game from source.
• Issue reporting through the project's GitHub tracker for both build and runtime problems.
• Patch submission on GitHub, with an active community presence on the Descent Developer Network Discord server.

Who uses it and how

• Players who already own the Descent 3 game files and want to run the community-maintained source tree alongside their own data, following the installation notes in USAGE.md.
• Developers who compile their own copies from source using the steps in BUILD.md; the repository has been forked 293 times, which is consistent with a population of people maintaining private builds.
• Contributors who submit patches on GitHub and coordinate with other developers through the Descent Developer Network Discord.
• Maintainers and reporters who use the GitHub tracker to raise and triage the open build and runtime issues, of which 45 were open at the time of listing.

Getting started

No published package, container image, or hosted build is named in the available material; the documented route is to take the source from GitHub, read USAGE.md for installation, and follow the build instructions in BUILD.md. The user must supply their own Descent 3 game files before the engine is usable.

How it compares

It stands alone in this registry: the available facts name no comparable engine, whether open source or paid, so no product-by-product contrast is offered here. The only comparison the material supports is with the earlier proprietary distribution of the same engine, which this GPL-3.0 release replaces and which anyone can now rebuild and patch.

When to use it — and when not to

Choose it if you own the game files and are comfortable compiling a C++ project, because that is the only route the documentation describes. Do not choose it if you want a ready-to-play download or a packaged binary, since none is mentioned and the engine ships without content. The README is short and defers almost everything to USAGE.md and BUILD.md, so expect to read those two files closely before you have a working build.