The Force Engine is a from-scratch reimplementation of the Jedi Engine
Modern "Jedi Engine" replacement supporting Dark Forces, mods, and in the future Outlaws.
At a glance
- What is it?
- The Force Engine aims to reverse engineer and rebuild the Jedi Engine so that Dark Forces and, later, Outlaws run natively on modern systems, with a level editor, a floating point software renderer and a GPU renderer, while staying compatible with the original data files. It is not a remaster, and a purchased copy of the original game is required.
- Who is it for?
- Adopt The Force Engine if you want to play Dark Forces or its many community mods on a modern system, at a modern resolution, with the original data rather than a remastered asset set. Do not adopt it expecting a standalone game, because the original game data is required and is not provided, and it remains GPL-2.0 with a Dark Forces scope only.
- Can I use it commercially?
- Yes, with conditions. GPL-2.0 is a copyleft licence: if you distribute software that includes it, you must release that software's source code under the same licence. Running it internally without distributing it does not trigger that obligation.
- Is it still maintained?
- Yes. The repository last received commits 11 days ago.
- What is it written in?
- Mainly C++, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on October 23, 2026, and from our analysis. They are not legal advice.
Editorial analysis
Reverse engineering an engine, not a game
The Force Engine is a project with the goal to reverse engineer and rebuild the Jedi Engine for modern systems and the games that used that engine, like STAR WARS: Dark Forces and Outlaws. The project will include modern, built-in tools, such as a level editor, and it will make it easy to play those games on modern systems as well as the many community mods designed to work with the original games.
So the deliverable is an engine, and the game data is the input. The distinction matters for everything else on this page, and the readme states it without hedging. A purchased copy of the original game is required and is not provided by The Force Engine, and the documentation has some information on how to legally purchase Dark Forces.
The readme also says what it is not. TFE is not a remaster, it is essentially a source port designed to run the original game natively on modern systems with quality of life improvements and optional enhancements. Dark Forces and Outlaws are owned by Disney and are still active, commercial products, and the IP is owned solely by Disney.
That framing is the whole legal position in one paragraph, and it is why the project can exist and why the downloads do not include the game.
The implementation is C++, the licence is GPL-2.0, the last push was on 2026-10-12, and the recent releases are v1.22.420 from 2025-09-10, v1.22.410 from 2025-09-09 and 1.22.400 from the same day.
What is done, and what is not
The Current State and Current Release sections say the same thing in two places, and the message is clear.
Full support for Dark Forces has been completed. You can play through the entire game, with all AI, weapons, items and functionality working as expected, and the current release includes iMUSE, the music system, so the soundtrack works too. You can also play Dark Forces mods.
Outlaws is not playable yet, and it is planned for version 2.0. The focus so far has been on the framework, the Dark Forces support and the Jedi Engine reverse engineering.
There is a line about lineage that is worth reading carefully. The project shares a legacy with DarkXL, but it is a complete rewrite, rebuilt from the ground up with a much greater focus on accuracy, and it is much more focused than the XL Engine, focused on being a Jedi Engine replacement and port only.
That is a real design decision with consequences. The XL Engine and its forks are feature-rich and sprawling, and they are the reason many modern community mods exist. A project that rebuilds the engine from scratch for accuracy will not have the same feature set on day one, but it will behave like the original, which is what the modding scene needs when a mod relies on engine behaviour that a fork changed.
The readme also sets expectations about quality. As with any project of this nature, there may be bugs and system specific issues, and bugs that cannot be reproduced in the DOS version should be reported on the forums or on GitHub.
Three renderers, and OpenGL is the only backend that exists
The rendering options are the most visible part of the project, and the readme describes them in order of how close you get to the original.
At 320 by 200 you get the original software renderer. TFE also includes a floating-point software renderer which supports widescreen, including ultrawide, and much higher resolutions. And there is a GPU renderer with perspective correct pitch, for much higher resolutions with improved performance.
So the engine can look like the DOS original, or it can run the original art at 4K, and the software path is the fallback rather than an afterthought. That matters for the classic renderer specifically, because the readme notes that the software renderer is also the way to get the original look with no need to adjust cycles in DOSBox.
The minimum requirements are OpenGL 3.3, and Windows 7 64 bit, a modern Linux distribution or macOS. The readme is candid about the limitation. For now, only OpenGL is supported, which may limit the use of some older Intel integrated GPUs that would otherwise be capable.
And the plan is to change that. There are near term plans to add Direct3D 10 and 11, Vulkan, and maybe Metal render backends, which should enable more GPUs to run the engine efficiently. There are also plans to lower the requirements for the classic software renderer, but the minimum for GPU rendering is here to stay.
That split is a sensible one. The GPU floor stays where it is because the renderer needs it, and the software floor can move down because it is a CPU path.
Mods, limits and input
Three features are about making the engine usable rather than about rendering.
The mod loader is simple by design. You place your mods in the Mods directory as zip files or directories, and that is the whole mechanism. For a project whose stated purpose includes the many community mods designed to work with the original games, a loader that does not need a manifest or a tool is the right call, because the mods predate the loader and the loader has to fit them.
Extended Limits are the second. TFE by default supports much higher limits than the original game's Jedi Engine was capable of, which removes most of the HOM, Hall of Mirrors, issues in advanced mods. That is a real compatibility feature rather than a feature, because the original engine had a sector count ceiling and the workaround for it in mods was a set of tricks that the removal makes unnecessary.
Input is the third. There is full input binding, mouse sensitivity adjustment and controller support, with the caveat that menus currently require a pointing input device like a mouse or touchscreen. That is a limitation of the UI rather than of the engine, and it is the sort of thing that shows up immediately on a console-oriented setup.
Save games, sound and the switch back to the original feel
The remaining features are about quality of life, and the project is careful to let you turn them off.
The save system is new, and it works seamlessly with the existing checkpoint and lives system. You can ignore it entirely, use it just as an exit save so you do not have to play long user levels in one sitting, or use full save and load with quicksaves like Doom or Duke Nukem 3D. Those three modes are genuinely different use cases, and supporting all three is a more useful design than picking one.
Sound is emulated, with Sound Font, sf2, and OPL3 emulation support, which covers the two sound technologies the original games used.
Then there is the long list of optional improvements: full mouselook, an aiming reticle, improved Boba Fett AI, autorun, and more. And the readme tells you how to turn them off. You can play in 320 by 200, set the mouse mode to menus only or horizontal, and enable the classic software renderer, and it will look and play just like DOS but at a higher frame rate and with no need to adjust cycles in DOSBox.
That last sentence is the one the project wants to be judged on. The enhancements exist, but the original experience has to remain reachable, because for a game with two decades of community mods, being able to go back is part of the feature set.
Linux, Flatpak and the Steam Deck
The platform story is handled carefully, and it is more nuanced than a list of downloads.
Linux is supported but may require additional setup, and you may need to compile TFE from source in order to run it directly on your favourite Linux distribution. For most Linux users it is recommended to install and run TFE via Flatpak from Flathub on those systems where Flatpak is available. The readme suggests searching your distribution's software centre or app portal, and notes that if you are already using GNOME Software or KDE's Discover, installing TFE might be one click away.
A Snap package is planned for the future, to alleviate the need to manually compile the project on systems employing Snap, and if you do not want to compile the code it might be better to use Windows for now or use Proton on the Steam Deck.
On the Steam Deck the recommendation is to run The Force Engine in desktop mode and install it via KDE's Discover from Flathub.
The Windows story is the simplest. The release package includes the Windows binary and all of the data, except for the original game, needed to run it, and if you want to compile it yourself there is a Visual Studio solution provided.
The runtime data, savegames, configuration and mods, are by default stored under ${HOME}/.local/share/TheForceEngi... in the path given in the readme, which follows the XDG convention.
The repository layout and what the roadmap holds
The top level listing is small and it is a C++ project with both build systems in the tree.
There is CMakeLists.txt for the CMake build, TheForceEngine.sln for the Visual Studio solution, and CreateGitVersionH.cmake, which is the usual trick for generating a version header from the git state at build time so a build from a working tree identifies itself.
The engine itself is in TheForceEngine/, and beside the code there are three documents that do a lot of the explaining. ProjectStructure.md describes how the project is organised, Roadmap.md holds the plan including the Outlaws work that will land in version 2.0, and the README is the one you have just read.
The surrounding directories are the community ones. There is a .github/ directory for the workflows, a .gitignore, a LICENSE file for the GPL-2.0 terms, and a Logo.png in the assets of the site rather than in the repository listing here.
The project also runs a forum on the-force-engine.freeforums.net and a Discord, and the readme is explicit about where bugs go: post them on the forums or on GitHub, and only if they cannot be reproduced in the DOS version, because a bug that also happens in the original is not a bug in the engine.
Editorial conclusion
Adopt The Force Engine if you want to play Dark Forces or its many community mods on a modern system, at a modern resolution, with the original data rather than a remastered asset set. Do not adopt it expecting a standalone game, because the original game data is required and is not provided, and it remains GPL-2.0 with a Dark Forces scope only. Verify first that your GPU supports OpenGL 3.3, since Direct3D, Vulkan and Metal backends are only planned, and that the release you install matches the game version whose data files you own.
Frequently asked questions
What is The Force Engine?
It is a C++ project that reverse engineers and rebuilds the Jedi Engine so that Dark Forces and, in future, Outlaws run natively on modern systems. It includes built-in tools such as a level editor and supports the many community mods designed for the original games.
Do I need to own the original Dark Forces game?
Yes. A purchased copy of the original game is required and is not provided by The Force Engine, and the documentation has information on how to legally purchase it. TFE is not a remaster, it is a source port that runs the original game with quality of life improvements and optional enhancements.
What are the system requirements?
OpenGL 3.3, and Windows 7 64 bit, a modern Linux distribution or macOS. Only OpenGL is supported for now, which may limit some older Intel integrated GPUs, and Direct3D 10 and 11, Vulkan and maybe Metal are planned.
How do mods work with The Force Engine?
You place them in the Mods directory as zip files or directories, with no manifest or special tool required. The engine also has extended limits by default, which removes most of the Hall of Mirrors issues that advanced mods had to work around.
Can I play the original games with the original look on The Force Engine?
Yes. Playing at 320 by 200 gives you the original software renderer, and the optional features such as mouselook can be disabled. The readme says that with those settings it will look and play just like DOS, at a higher frame rate and with no need to adjust cycles in DOSBox.
How do I install The Force Engine on Linux?
You may need to compile it from source to run it directly on your distribution, but for most users the recommended route is the Flatpak from Flathub, which can also be installed through GNOME Software or KDE Discover. A Snap package is planned for the future.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/theforceengine-theforceengine)Was this useful?