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 instruct the patch builder yourself, completely evading the use of the GPC editor to build patches. You would have to send all the appropriate command line syntax in order to properly build a successful patch. This is only available for Pro and Ultra licenses.
Here is the list of available command line switches for the builder. None of these are optional, you will need to specify them all, in any order.
You can hide the build process by using the /W switch with either a 0 (zero) or 1 (one).
Example: /W1 (show build window)
You should send the input folder to scan over for your patch files. It should contain no space between the flag and the path. If your path contains spaces in any of the folder names, you will need to wrap it in ” ” speech marks.
Example without spaces
/GC:\mygame\
Example with spaces
“/GC:\my game\”
You should send the path to the output folder where the renamed patch files will go once scanned over. These are the files to be uploaded. As above, you should use speech marks if the syntax contains spaces anywhere.
If this folder does not exist, you don’t need to create it. The builder will automatically try and create this output folder for you.
You should specify the path to the patch log and version output folder. This will export the patch file list and version file to. If this folder doesn’t exist, the builder will automatically try and create it.
Example: /Pc:\output\
You should specify the project name here, the same as your project name inside your GPC project. You can find this name when you open your project in GPC, it will be above the menu (underneath the project logo). If it contains spaces, you must wrap in ” ” speech marks.
Example: /Nmypatcher
You should specify the output patch file list name here. You should use the one specified inside your GPC project. If it’s a single version patcher, use your single patch file list name, if it’s multiple versions, you should use the multiple patch file list name.
You should specify the custom extension output here. By default, gppc is used. This extension must match the custom extension used inside your GPC project.
Example: /Egppc
You should specify here the absolute URL to your salt file online.
Example: /Lhttps://mydomain.com/gamefiles/salt
You should specify the version number as a string here. This is the version number for this build.
Example: /V1.1.2 (would build version 1.1.2)
If you experience any issues with using command line for the builder, you should consult the build patch log. Each build generates a patch log output which will show you the entire build process from start to finish. If you experience any difficulties, you can read through this log to see what went wrong and where.
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
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
Building your project is very easy with GPC. Upon your first build, you will need to select ‘Build All’. This will scan over your game