Building a Single Server Patch
Introduction In this tutorial, we will build a single server patch together so you can get to grips with how Game Patch Creator works at
You can choose to have your configuration file for your patcher stored on a webserver or have it as a settings file local to the patcher executable.
Having your configuration file for your patcher on your webserver is the recommended method to use. This enables you to update your patch configuration at any time by simply updating the file on the server.
To modify your configuration file, you can simply open your project up in GPC, make the modifications and then Export your Configuration file then upload it and overwrite the existing one on your server.
If you choose this method, you must launch your patcher with the commandline item /D
Example:
patch.exe /Dhttps://mysite.com/patch_config/patchconfig
If you do not choose the downloadable option then when you build your patch, GPC will build out your settings file and it will be named gpcsgs. This must stay with your patch executable at all times.
If you wish to use another location for your local settings file, you can specify this with the commandline item /P
Example:
patch.exe /Pdata\configs\gpcsgs
Introduction In this tutorial, we will build a single server patch together so you can get to grips with how Game Patch Creator works at
You can instruct the patch builder yourself, completely evading the use of the GPC editor to build patches. You would have to send all the
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
In order to prepare your server for patching, there are a few pointers we can give you here. If you host your game files with
Every time your user runs your patcher, it will log every detail it possibility can down in a log file, should the patcher crash or
When we programmed and designed Game Patch Creator we understood the importance of generating Debug logs. So we generate exclusive, in-depth debug logs for both