With the Pro and Ultra versions of Game Patch Creator, you have the ability to send command line switches to your patcher executables.

Command line switches are very useful because they enable you to send parameters and switches to override existing settings or perform special actions without having to modify your existing patch settings. Here we will take a look at the available switches to you and what they do.

Please note, command line switches will override your default settings. So if you specify as an example:

This instructs the patcher to force a patch install of version 1.1.2 automatically.

Please also note, if any of your syntax includes spaces you must wrap the commandline in ” ” speech marks!

Available Commandline Switches

Here is the list of available command line switches for both the builder and patcher.

Force Integrity Check – /i1

Use /i1 to force an integrity check of the currently installed version. This will check all the files in the existing installation and compare against the currently available remote version.

If you wish to force a file integrity check against a remote version that isn’t the latest, then you will need to specify the additional command /v followed by the version number.

(Latest Version) Usage: /i1(Previous/Different Version) Usage: /i1 /v1.1.2

Version Specification – /V<versionnumber>

This is an optional command to use with other commands such as forced install or integrity check. You should specify /v followed by the full version number without a space.

Force Version Install – /F1

By default the patcher will automatically check the currently installed version number against the latest version available, however you can force the patcher to install a previous version by using the /F1 switch. This should be used in conjunction with the Version Specification switch, to tell the patcher which version to force an install of.

Please note, you must have multiple versions activated inside your patcher configuration in order for this to work.

Different Config Path – /P<filename>

By default the path to your config file (unless using online configuration) will be in the same directory as the patch executable and will be named gpcsgs. You can specify a different path to your config file here, should you wish to move it somewhere else.

Note, you can use additional commands inside your path such as ./ (to go back up a level) or Data\Another Folder\Another Folder to specify a deeper folder.

Downloadable Config – /D<url>

Inside the GPC Editor you can specify if your patcher configuration file should be stored online and downloaded every launch. However, if you have an offline config file but want to issue a new online config to be used you can do this with the /D switch, followed by the URL, no spaces. This is also handy for having multiple different configuration files for different purposes.

Force Silent Patch Switch – /S<0/1>

You can choose a force of a silent patch with /S1 and force a non-silent patch of /S0 (zero), /S0 is only really to be used if your patcher is silent by default and you want the window to show.

/S1 is useful if your patcher needs to run in silent mode (no window drawn) and patcher to run.

Enable Debug Logging – /Y1

By default, debug logging for your user’s is not enabled. This is to enable a faster performance from the patcher. However, if your user is running into issues, you should instruct them to run the patch executable with the /Y1 switch and it will then generate a debug log. More Instructions here.