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
The Remote Version location should be the file or database which holds your latest version information. For incremental patching, every time you release a new update, you should update this number. You can use a simple text file on your webserver or use your own PHP file to retrieve the number and output it to the patcher.
File
You should specify the absolute URL to a file on your webserver which holds the latest version number. This will trigger the patcher to tell it there’s a new version available if the users local version number is lower.
Web-Script
You should specify the absolute URL to a script online (typically PHP/ASP) that outputs the latest version number. This will trigger the patcher to tell it there’s a new version available if the users local version number is lower.
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