Star Wars Jedi Knight: Jedi Academy / Jedi Outcast

Two different Jedi journeys

Jedi Academy puts you in the role of a student learning the Force, with a customizable character and lightsaber and a choice of missions. Jedi Outcast follows Kyle Katarn, combining weapons, Force powers and lightsaber combat in a separate campaign. Their related technology does not make them one combined story or one interchangeable data set.

For a player choosing between them, Academy’s character and saber choices are part of the original game’s appeal; Outcast’s established protagonist and campaign are its own starting point. OpenJK maintains their engines rather than creating a new sequel.

Jedi Academy · publisher description · Jedi Outcast · publisher description · OpenJK · project documentation

Academy and Outcast have different support levels

The project labels Jedi Academy single-player and multiplayer stable. Jedi Outcast single-player works but needs attention, and Outcast multiplayer is not supported here. This is the most important distinction before choosing a download or planning a session with friends.

OpenJK aims to improve stability, performance and platform support while maintaining compatibility with existing games and mods. It explicitly avoids major feature additions and core gameplay rebalancing. Choose it as an engine-maintenance project, not as a new combat overhaul.

OpenJK · project documentation

Install into the appropriate game directory

The main player guide starts with an owned Jedi Academy installation and places the downloaded OpenJK files inside GameData. The executable differs by platform. Linux can use the Windows game-data installation, while the Mac App Store edition has a separate documented app-bundle layout.

Outcast uses its own data and the separate OpenJO build. Do not follow the Academy folder instructions with Outcast assets and expect the engine to identify them as the same game. Check the chosen build’s guidance before moving either installation.

OpenJK · project documentation

Keep user files when changing the application

For the documented macOS setup, saves, configuration and logs live in Application Support/OpenJK rather than inside the installed application. Preserve that user directory when replacing a build. If you add mods, keep their intended game and engine requirements in view: OpenJK’s compatibility goal does not erase the distinction between Academy, Outcast and their respective multiplayer implementations.

OpenJK · project documentation