Karsk Games CDN

Build channels

Channel	Status	Description	Path
Release	No build	The stable public build.	/nomansland/release/
Beta	No build	Next release candidate.	/nomansland/beta/
PlaytestKey	No build	Closed playtest builds.	/nomansland/playtest/
DevelopmentTeam	No build	Internal builds off the branch.	/nomansland/dev/

Layout

/nomansland/<channel>/manifest.json    what the launcher reads
/nomansland/<channel>/...              build files, paths as in the manifest
/launcher/latest.json                  current launcher version
/launcher/KarskLauncher-<v>-win64.zip  launcher packages
/images/                               hero art and shared artwork

How the launcher uses this

The launcher fetches the manifest for the selected channel, compares its build number against what is installed, and downloads only the files whose SHA-256 differs. Three things about that are worth knowing before you publish anything here.

Build numbers decide updates, not versions. The comparison is integer only. A build number must increase on every publish, including a hotfix that keeps the same version string.
Paths resolve against the manifest's own folder. Manifests hold relative paths, never absolute URLs, which is what lets an entire channel be relocated by moving one directory.
Manifests are never cached, build files are cached forever. Build files are content-addressed by their hashes, so a URL's bytes never change meaning. A stale manifest, by contrast, makes the launcher read an old build number and ignore everything you uploaded.