Debugging Launcher and Patcher
Getting the logs
Launcher and Patcher logs are usually the first thing you should be looking into. Here’s the list of where Launcher and Patcher logs can be found.
|GNU/Linux||launcher||launcher-log.txt next to launcher binary|
|Mac OSX||Launcher.app||~/Library/Application Support/PatchKit/Apps/launcher-log.txt|
Watch out, since both launcher and patcher logs will get overwritten as soon as you start your game again. If you want to keep them (to send them to firstname.lastname@example.org for example), you have to make copies.
Command line arguments
Patcher should be ran with following command line arguments:
patcher.exe --installdir "dir" --secret "secret" --readable
You can try and launch it with your custom installdir and secret. Remember to always pass readable, because otherwise patcher will expect an encoded secret instead of a string.
Patcher behavior can be overriden by setting up those environment variables.
|PK_PATCHER_FORCE_SECRET||Set it to application secret to forcefully change what game should be downloaded.|
|PK_PATCHER_FORCE_VERSION||Change the latest game version to given one. This is internal version id starting from 1.|