The AOPS2 Patch settings dialog allows you to configure your patching system inside the launcher. Some options may not be available for all Editions.<\/p>\n
Specify the Window Title<\/a> to display for the patcher.<\/p>\n Specify the size of the patch window in pixels (Width x Height)<\/em>.<\/p>\n Allows for a silent patch process. If you are using your own custom page in the launcher for the patching, you must enable this. You must also send the \/S1 commandline in the action where you run the AOPS2 patcher.<\/p>\n Instruct the patching system to Exit the game launcher when the patching process starts. For obvious reasons, you should not uncheck this if you are embedding the patching system directly in your launcher page.<\/p>\n This must be the full, absolute URL to the online folder where your latest patch files are stored (example: https:\/\/myserver.com\/patch\/files\/). This folder must be accessible for the patching system so you may need to set permissions correctly.<\/p>\n This must be the full, absolute URL to the online patch list file. This file must be accessible publicly. You can test this by typing this URL into your web browser and seeing if the patch list shows (or downloads). (example: https:\/\/myserver.com\/patch\/patchfilelist)<\/p>\n This must be the full, absolute URL to the online salt file. This contains your hash<\/a> salt. You must not<\/strong> use #<\/strong> or |<\/strong> characters inside your patch salt<\/a>. (Example: https:\/\/myserver.com\/patch\/salt)<\/p>\n You must specify the custom extension you wish to use for your patch files. This can be absolutely anything you want, although we recommend keeping it to something that has never been used before (or GLC is fine).<\/p>\n By using a custom extension, most of this can be avoided, resulting in a flawless patch system.<\/div><\/div>\n Here you must specify the compression ratio to use for your latest game patch files. This uses LZMA2 compression. The range is 0 – 9 with 0 being no compression and 9 being the highest form of compression.<\/p>\n You MUST make sure the files are not in use by the operating system or another application. This too, can throw errors as the file must not be in use in order to be compressed.<\/div><\/div>\n You can toggle whether the splash screen is enabled or not.<\/p>\n You can toggle this to ON to tell the patcher to download your splash screen from your webserver (formats supported: JPG, PNG, BMP). You must specify the full, absolute URL to this (example: https:\/\/myserver.com\/files\/splash.jpg)<\/p>\n Even if you are running a silent patcher, you can still choose to display your splash screen to the user.<\/p>\n You must specify in frames, how long to display the splash for. 60 = 1 second, 120 = 2 seconds. Seconds are in increments of 60. For 1 minute, use 3600.<\/p>\n You can choose to assign a Base Installer to your patch setup, should certain conditions be met. A base installer is a good option if the user runs the launcher for example, and it appears your game isn’t installed or something is missing. You can then choose to download your base installer and then run it, so the initial installer can be run for your game.<\/p>\n For example, below, you can choose to instruct the patcher to check the registry to see if a particular entry exists. If it doesn’t, it will download the base installer.<\/p>\n Toggle this to ON, if you require the base installer option.<\/p>\n The full, absolute URL to the base installer on your webserver (example: https:\/\/myserver.com\/files\/installer.exe)<\/p>\n The Root Registry Key for a base install check<\/p>\n The current key for the base install check<\/p>\n The string entry to look for in the registry key for the base install check<\/p>\n Toggle this to ON if you are using 64-bit registry keys, or the user is using 64-bit. Most of the time, you should turn this to on, unless you know your users are only running 32-bit machines (very unlikely)<\/em>.<\/p>\n Require base installer if one of the pre-execs fails.<\/p>\n <\/p>\n Restart the patcher after the base installer has downloaded and finished running. This allows your patching system to run immediately after they have installed the base installer.<\/p>\nWindow Size<\/h6>\n
Silent Patch (Developer Only)<\/strong><\/h6>\n
Exit Launcher<\/h6>\n
General Setup<\/h5>\n
Online Directory<\/h6>\n
Online Patch File<\/h6>\n
Online Salt<\/h6>\n
Custom Extension<\/h6>\n
Compression (Developer Only)<\/strong><\/h6>\n
Splash Screen<\/h5>\n
Splash Enabled<\/h6>\n
Download Splash<\/h6>\n
Show in Silent Patch<\/h6>\n
Splash Timer<\/h6>\n
Base Installer<\/h5>\n
Require Base<\/h6>\n
Base URL<\/h6>\n
Reg Root<\/h6>\n
Reg Current<\/h6>\n
Reg String<\/h6>\n
64-Bit Key<\/h6>\n
Require Pre-Exec<\/h6>\n
Base Pre-Exec<\/h6>\n
Restart Patcher<\/h6>\n
Version Base<\/h6>\n