Hosting

You can host PATCH artifacts (builds and patches) on your favorite hosting service. It works with every service that can serve files over HTTP or HTTPS and that can expose a direct file URL. This because PATCH dynamically builds URLs based on your builds/patches metadata.

Some samples:

• http://myCoolHostingService.com/patch/myfile.txt => valid
• https://myCoolHostingService.com/folder/myfile.txt => valid
• http://myCoolHostingService.com/?file=jR2xl1D => invalid

Hosting on GitHub

WARNING: some users are experiencing problems while hosting their files on GitHub. Some of these problems are: corrupted files or wrong-sized files, the Launcher and the PreGame just keep on restarting themselves in a loop, etc. This happens when Git LFS is involved (so: when your repository contains files bigger than a certain threshold). If that's your case, choose a different host.

You can use a repository on GitHub to host builds and patches for free. It does not require payments or fees and it has not bandwidth limits. It's perfect to start hacking into PATCH with no costs!

Let's make an example!

Let's assume that my files are hosted at https://github.com/manhunterita/PATCH, on master branch. In this repo I have the classic PATCH folder structure, as explained previously in this doc:

https://github.com/manhunterita/PATCH/Builds/ https://github.com/manhunterita/PATCH/Patches/ https://github.com/manhunterita/PATCH/Updater/

In the Launcher's settings I can simply set as Remote URL the raw GitHub address: https://raw.githubusercontent.com/manhunterita/PATCH/master/. Normally you can obtain your URL by following this schema: https://raw.githubusercontent.com/Username/RepositoryName/BranchName/.

Here we go: you've set your Launcher for downloading from your GitHub repositories.

Hosting with other vendors

For your convenience, here is a list of the major vendors (some of them are marked with referral, this means that by using that host you will support PATCH indirectly):

• Vultr [referral]
• Digital Ocean [referral]
• Hetzner
• Linode
• AWS
• Azure
• Google Cloud
• OVH

Hosting on AWS S3

If you are hosting your files on AWS S3, remember to check the bucket's Amazon S3 Block Public Access settings and to grant Public Read Access to your files. Otherwise, your Launcher couldn't access your files.

Hosting on Azure Blob Storage

If you are hosting your files on Azure Blob Storage and you are using the ChunkedDownloader contained in the Pro version, you may experience some difficulties in downloading files. If that's the case, make sure to use the latest API schema (by default, it doesn't use the latest). To do that, in https://portal.azure.com/ click on Cloud Shell and run this script (first change the account-name and the key to match your own credentials):

$ctx = New-AzureStorageContext -StorageAccountName <account-name> -StorageAccountKey <key>

Update-AzureStorageServiceProperty -ServiceType Blob -DefaultServiceVersion 2021-04-10 -Context $ctx

This enables ranged and partial downloads, required for ChunkedDownloader.