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
Here you can stipulate the filename of the patch file list to use.
When GPC scans over your game files, it generates what is known as a Patch File List. This list is a catalogue of all the game files. The patcher will run through this list, comparing what is on the user’s computer and what needs to be patched. It stores all the checksums for the files in here. It’s the file the patcher needs to access to know what files to look for on the user’s computer.
If you are not running multiple versions or multiple servers for your game patching and just using one server with incremental patching, then you stipulate the filename here. This is the filename that the scanner will generate once it has scanned over your files.
If you are using either multiple versions or multiple servers, you must use the Multiple Patch File List filename option instead.
The URL to this Single Patch File must be absolute (ie: https://mysite.com/patch_config/patchfile)
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