Upload Builds and Patches

Get your game to your players, from the dashboard or from the CLI

A build is a packaged version of your game: a ZIP file with everything a player needs to run it. You upload a build, Game Launcher Cloud processes it, and your players receive the update through your launcher.

There are two ways to upload. Pick the one that fits your build and follow that guide:

Upload from the Dashboard

Drag and drop your ZIP in the browser. Up to 5 GB.

Upload with the CLI Tool

For large builds, faster uploads and CI/CD automation.

---

Dashboard Upload vs CLI Upload

	Dashboard (Web)	CLI Tool
Maximum file size	5 GB	Large files (depending on your plan)
Setup	None, it is already in your browser	Download the CLI once
Best for	Small and medium builds, occasional updates	Large builds, frequent releases
Upload speed	Good	Faster on large files, direct to Cloudflare R2
CI/CD automation	Not available	Yes, scriptable on every release

Both methods produce exactly the same build. Nothing changes for your players.

---

Build Types

Standard Build (Baseline)

Upload the complete game build.

Use this when:

• Creating the first build.

• You are not sure which files changed.

• Your build structure changed significantly.

Existing players will still download only new or modified files.

Merge Build

Upload only the files that changed. Game Launcher Cloud merges them with the existing Baseline. Files must keep the exact same path as before.

Be aware of the path structure. Example:

Data/translations.csv

must still be uploaded as:

Data/translations.csv Do not rename or change root folders between builds or they will be detected as new files.

For example:

MyGame_v1/Data/file.dat

and

MyGame_v2/Data/file.dat

are considered different paths.

Merge Builds are mainly useful for avoiding large uploads. For example, if your game is 100 GB but you only changed a 5 KB file, you only need to upload that file.

If you are unsure which files changed, use a Standard Build instead.

---

Prepare Your Build

Whatever method you use, the ZIP has to meet these requirements:

Requirement	Details	Notes
Format	ZIP compressed file	Must be a .zip file
Size	Up to 5 GB from the Dashboard Larger files with the CLI
File structure	Files must be in the ZIP root (do not compress a single folder)	Select all your files and compress

Important: do not include unnecessary files like source code, logs, .git folders or development tools. They make every download bigger for your players.

Compress your game as a ZIP

Make sure to select all the files and compress, so they stay in the root of the ZIP

CORRECT: Select all the files and compress as a ZIP

Recommended Structure

MyGame.zip
├── MyGame.exe              (Windows)
├── assets/
│   ├── textures/
│   ├── sounds/
│   └── models/
├── data/
│   ├── config.json
│   └── settings.ini
└── README.txt

Windows

MyGame_Windows.zip
├── MyGame.exe           ← Main executable
├── MyGame_Data/         ← Unity/Unreal data
├── MonoBleedingEdge/    ← Unity runtime
├── UnityCrashHandler64.exe
└── UnityPlayer.dll

macOS

MyGame_macOS.zip
├── MyGame.app/          ← macOS application bundle
│   └── Contents/
│       ├── MacOS/
│       ├── Resources/
│       └── Info.plist
└── README.txt

Linux

MyGame_Linux.zip
├── MyGame.x86_64        ← Linux executable
├── MyGame_Data/
├── UnityPlayer.so
└── run.sh               ← Optional launch script

---

Build Notes

Build notes are optional, and players read them in the launcher before downloading. Good notes tell them what changed:

**Version 1.2.0**

New Features:

- Added multiplayer co-op mode
- New character customization options
- 5 new maps in rotation

Bug Fixes:

- Fixed crash when loading large maps
- Improved FPS on low-end systems
- Fixed audio sync issues

⚖Balance Changes:

- Reduced weapon damage by 10%
- Increased player movement speed

Tip: markdown formatting works here, so use it. "update" is not a build note.

---

Next Steps

Dashboard Upload

Step by step guide, up to 5 GB

CLI Upload

Step by step guide for large builds

How Patching Works

Delta patches, Smart Bundles and file verification

Environments

Test in Staging before going to Production