How does the Patch Commander work?
The way Patch Commander works is simple. It creates a subdirectory of your Jedi Knight directory called JKPatch and a subdirectory of that called active. All your patches are stored in the JKPatch directory, and moved to the active directory when you activate them. When you run Jedi Knight, Patch Commander executes jk.exe -path JKPatch\active\ which tells JK to look for GOB files in the JKPatch\active directory and use them as patches. • I can’t get patches to work with Patch Commander! How come? This is a hard question to answer. The most common reason is that Jedi Knight was moved to a new drive or directory after it was installed, and Patch Commander can’t figure out where it is. Patch Commander uses the Microsoft DirectPlay registry information to find out where Jedi Knight is installed. This information is placed in the registry by the Jedi Knight installer. The latest version of Patch Commander has a Debug Information option under the Help menu which will provide lots of informat
