DarkJedi

DarkJedi is a fork of OpenJK (see below) focused on providing necessary code changes for the Dark Forces mod for Jedi Academy. Changes include enabling the unused advanced combat system from Jedi Academy, reenabling the inventory system, and programming the Dark Forces weapons: the Fusion Cutter, Mortar Gun, and Assault Cannon as new, separate weapons.

Additional aims are to:

• Provide commits to OpenJK that can mutually benefit both projects
• Add new gameplay elements, such as a Stormtrooper Disguise and unlockable outfits for Kyle Katarn

About OpenJK

OpenJK is an effort by the JACoders group to maintain and improve the game engines on which the Jedi Academy (JA) and Jedi Outcast (JO) games run on, while maintaining full backwards compatibility with the existing games. This project does not attempt to rebalance or otherwise modify core gameplay.

Our aims are to:

• Improve the stability of the engine by fixing bugs and improving performance.
• Provide a clean base from which new JO and JA code modifications can be made.
• Make available this engine to more operating systems. To date, we have ports on Linux and OS X.

Currently, the most stable portion of this project is the Jedi Academy multiplayer code, with the single player code in a reasonable state.

Rough support for Jedi Outcast single player is also available, however this should be considered heavily work in progress. This is not currently actively worked on or tested. OpenJK does not have Jedi Outcast multiplayer support.

Please use discretion when making issue requests on GitHub. The JKHub sub-forum is a better place for support queries, discussions, and feature requests.

Windows	OSX	Linux x86	Linux x64

License

OpenJK is licensed under GPLv2 as free software. You are free to use, modify and redistribute OpenJK following the terms in LICENSE.txt.

For players

To install OpenJK, you will first need Jedi Academy installed. If you don't already own the game you can buy it from online stores such as Steam, Amazon or GOG.

Installing and running OpenJK:

1. Download the latest build for your operating system.
2. Extract the contents of the file into the Jedi Academy GameData/ folder. For Steam users, this will be in <Steam Folder>/steamapps/common/Jedi Academy/GameData.
3. Run openjk.x86.exe (Windows), openjk.i386 (Linux 32-bit), openjk.x86_64 (Linux 64-bit) or the OpenJK application (OS X), depending on your operating system.

Linux Instructions

If you do not have a windows partition and need to download the game base.

1. Download and Install SteamCMD SteamCMD .
2. Set the download path using steamCMD, force_install_dir .
3. Using SteamCMD Set the platform to windows to download any windows game on steam. @sSteamCmdForcePlatformType "windows"
4. Using SteamCMD download the game, app_update 6020.
5. Download the latest build for your operating system.
6. Extract the contents of the file into the Jedi Academy GameData/ folder. For Steam users, this will be in <Steam Folder>/steamapps/common/Jedi Academy/GameData.

OS X Instructions

If you have the Mac App Store Version of Jedi Academy, follow these steps to get OpenJK runnning under OS X:

1. Install Homebrew if you don't have it.
2. Open the Terminal app, and enter the command brew install sdl2.
3. Extract the contents of the OpenJK DMG (Download the latest build) into the game directory /Applications/Star Wars Jedi Knight: Jedi Academy.app/Contents/
4. Run openJK.app or openJK SP.app
5. Savegames, Config Files and Log Files are stored in /Users/<USER>/Library/Application Support/OpenJK/

For Developers

Building OpenJK

• Compilation guide
• Debugging guide

Contributing to OpenJK

• Fork the project on GitHub
• Create a new branch and make your changes
• Send a pull request to upstream (JACoders/OpenJK)

Using OpenJK as a base for a new mod

• Fork the project on GitHub
• Change the GAMEVERSION define in codemp/game/g_local.h from "OpenJK" to your project name
• If you make a nice change, please consider back-porting to upstream via pull request as described above. This is so everyone benefits without having to reinvent the wheel for every project.

Deciphering buildbot's output

• Pick the build from the operating system builder you're interested in at the builders page.
• Click on stdio for the Steps to see the command executed and the result.
• The command is at the very top, the output starts below.

Maintainers (in alphabetical order)

• Ensiform
• Razish
• Xycaleth

Significant contributors (in alphabetical order)

• eezstreet
• exidl
• ImperatorPrime
• mrwonko
• redsaurus
• Scooper
• Sil
• smcv