> For the complete documentation index, see [llms.txt](https://wiki.retrobat.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.retrobat.org/systems-and-emulators/supported-game-systems/others/the-force-engine.md).

# The Force Engine

<div align="left"><figure><img src="https://990680527-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FexdzL60ZuqPLldz2AYta%2Fuploads%2FDgUCr5u0tXat2oT8yRyo%2Fimage.png?alt=media&amp;token=222ea7f1-a66b-4f19-92fa-9f126e4a65ce" alt="" width="375"><figcaption></figcaption></figure></div>

## Overview

**Star Wars: Dark Forces** (LucasArts, 1995) is a first-person shooter in the Star Wars universe.

RetroBat uses **The Force Engine**, a modern engine that recreates the original game: high resolution, widescreen, OpenGL rendering, mods.

The game files are not provided: use the ones from your own copy (DOS CD, Steam, GOG).

{% embed url="<https://theforceengine.github.io/>" %}

## At a glance

<table><thead><tr><th width="237.75"></th><th></th></tr></thead><tbody><tr><td><strong>Games folder</strong></td><td><code>roms\theforceengine</code></td></tr><tr><td><strong>Extensions</strong></td><td>.game</td></tr><tr><td><strong>Default emulator</strong></td><td>theforceengine</td></tr><tr><td><strong>BIOS</strong></td><td>None (game files to provide)</td></tr><tr><td><strong>Controller setup</strong></td><td>No: The Force Engine controls</td></tr><tr><td><strong>Save states</strong></td><td>No: in-game saves</td></tr><tr><td><strong>RetroAchievements</strong></td><td>No</td></tr><tr><td><strong>Netplay</strong></td><td>No</td></tr><tr><td><strong>Light guns</strong></td><td>—</td></tr><tr><td><strong>Wheels</strong></td><td>—</td></tr><tr><td><strong>Optional BIOS</strong></td><td>—</td></tr></tbody></table>

## BIOS

No BIOS is needed. Copy the Dark Forces files (including `DARK.GOB`) to `roms\theforceengine`.

## Which game format?

A `.game` file placed in the folder of the game files starts Dark Forces. If it holds the name of a mod on its first line, the mod is started (see [**Guides**](#start-a-mod)).

## Controls

RetroBat does not configure the controller: The Force Engine recognizes it and its controls are changed in its options.

**CONTROLS > DISABLE AUTOAIM** and **DISABLE CROSSHAIR** can be set in RetroBat.

### Hotkeys

<table><thead><tr><th width="251.5">Hotkey</th><th>Action</th></tr></thead><tbody><tr><td>HOTKEY + START</td><td>Quit</td></tr></tbody></table>

## Folders

<table><thead><tr><th width="212.75">Content</th><th>Folder</th></tr></thead><tbody><tr><td>Game</td><td><code>roms\theforceengine</code></td></tr><tr><td>Mods</td><td><code>roms\theforceengine\Mods</code></td></tr><tr><td>Saves and configuration</td><td><code>emulators\theforceengine</code> (<code>settings.ini</code> makes the install portable)</td></tr></tbody></table>

## Guides

### File layout

Copy the original DOS game (or the Steam / GOG version) to `roms\theforceengine`. Example with the DOS version:

<div align="left"><figure><img src="https://990680527-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FexdzL60ZuqPLldz2AYta%2Fuploads%2FuInyVYXj1qQZJIxaVFdO%2Fimage.png?alt=media&amp;token=766b5a69-5c0a-4177-ac4a-7f2b1bc2b1bc" alt=""><figcaption></figcaption></figure></div>

Create a text file in the same folder as the game executable, then change its extension to `.game`.

### Start a mod

Put the mod in `roms\theforceengine\Mods`:

Create a text file with an easy to recognize name (it is shown in the game list), write the full name of the mod (with its extension) on the first line, then change the extension to `.game`:

<div align="left"><figure><img src="https://990680527-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FexdzL60ZuqPLldz2AYta%2Fuploads%2FhPYSqFgzJwp3azrPArgq%2Fimage.png?alt=media&amp;token=30825f78-0d0c-49e6-af93-2fb060ed249d" alt=""><figcaption></figcaption></figure></div>

<div align="left"><figure><img src="https://990680527-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FexdzL60ZuqPLldz2AYta%2Fuploads%2FDq9ihrd1sPAw8UY8r5N2%2Fimage.png?alt=media&amp;token=54aa5634-027d-4eba-9083-53e6b183d8cb" alt=""><figcaption></figcaption></figure></div>

### Options

* **INTERNAL RESOLUTION** from 200p to 2160p (default: screen resolution), **VIDEO > WIDESCREEN**.
* **EMULATION > DISABLE CUTSCENES**, **USER INTERFACE > SHOW SUBTITLES**.

## Known issues

| Issue                                   | Solution                                                      |
| --------------------------------------- | ------------------------------------------------------------- |
| The Force Engine does not find the game | The `.game` file must be in the folder that holds `DARK.GOB`. |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://wiki.retrobat.org/systems-and-emulators/supported-game-systems/others/the-force-engine.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
