Uploading Game Versions

Each game can have multiple versions. Every uploaded version goes through a quarantine scan before it can be published.

Uploading

1. Go to your game's edit page (/games/{id}/edit)
2. Scroll to the Versions section
3. Click Upload New Version
4. Fill in:
   • Version Name — A label like 1.0.0, beta-3, launch
   • Changelog — Release notes (HTML supported)
   • Is Demo — Check if this is a demo version
   • File — Select your game zip file
5. Submit

TIP

For HTML5 games, ensure your zip contains an index.html (or similar entry file) at the root or in a recognizable structure.

Quarantine Pipeline

After upload, the version enters the quarantine pipeline:

Upload → Quarantine Blob Storage
  → Queue message triggers Azure Function
  → File is scanned for malware/issues
  → Result: Approved or Rejected

States

State	Meaning
Draft	Just uploaded, entering quarantine
Quarantined	Currently being scanned
Approved	Scan passed — ready to publish
Rejected	Scan failed — check the scan result for details
Published	Live — players can download/play this version
Deprecated	Superseded by a newer published version
Archived	Removed from active use

Publishing a Version

Once a version is Approved:

1. Go to the game edit page
2. Find the approved version
3. Click Publish
4. The previous published version (if any) is marked as Deprecated

Demo Versions

Upload a version with Is Demo checked to create a demo. Demos can be:

• Played in-browser from the store page (for HTML5 games)
• Downloaded from the store page

Demos are free — no purchase required.

File Requirements

• Max size: 200 MB (via API), browser upload limits may vary
• Format: ZIP archive
• HTML5 games: Must contain an HTML entry file
• Integrity: SHA-256 hash is computed after scan for verification

API Upload

For CI/CD integration, use the API with a GameVersions-scoped PAT:

curl -X POST \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -F "file=@game.zip" \
  -F "versionName=1.2.0" \
  https://ludilol.example.com/api/games/{gameId}/versions