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
From this panel you can choose to write your own custom appended file extension to your patch files to be uploaded to your webserver.
The default is gppc.
You maybe distributing your game to a handful of players or millions of players worldwide. Lots of users have antivirus products installed, firewalls, external firewalls and much more. Sometimes, if a process (or patcher) tries to download some files like executable (exe) or dynamic link libraries (dll) a third-party app might break the download or attempt to stop it.
To get around this, we append a custom extension to the end of each of your game files. This is all done automatically, so you don’t have to do anything yourself.
Some webservers also don’t like exe or dll files being downloaded or even read, so we have to append all files to be patched with a custom extension which breaks this mould.
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