Publishing Your Game: Updating & Versioning

Updating your game is just as important as the initial release.
A clean versioning system ensures players always know what build they’re on, prevents multiplayer mismatches, and keeps your project organized as it grows.

This page explains how to manage updates, version numbers, release notes, and how to avoid breaking multiplayer when pushing new builds.

1. Why Versioning Matters

Good versioning prevents:

• Players joining rooms with incompatible builds

• Confusion about which build is newest

• App Lab or SideQuest rejection

• Multiplayer desync

• Bug reports with missing context

A clear version number = a clean development pipeline.

2. Version Number Format

Use Semantic Versioning:

MAJOR. MINOR. PATCH

MAJOR

Big updates that change core systems
(e.g., new movement system, new map format)

MINOR

New features
(e.g., new cosmetics, new map, new mode)

PATCH

Bug fixes
(e.g., fixing room codes, fixing collisions)

Examples

1.0.0 → First release 1.1.0 → New map added 1.1.1 → Bug fix for map collisions 2.0.0 → Major overhaul of movement system

3. Where to Display the Version Number

You should display the version number in:

• Main menu

• Pause menu (optional)

• SideQuest / itch.io listing

• App Lab listing

• Release notes

• PlayFab Title Data (optional)

This helps players and testers report bugs accurately.

4. Updating Your Quest Build

When updating your APK:

A. Increase the Bundle Version Code

This is required for installation.

Example:

v1.0.0 → Bundle Code 1 v1.1.0 → Bundle Code 2 v1.1.1 → Bundle Code 3

B. Update the Version Number

In Player Settings → Version.

C. Rebuild the APK

Export a new APK with the updated version.

D. Upload to SideQuest or App Lab

Replace the old file with the new one.

E. Add Release Notes

Explain what changed.

5. Updating Your PCVR Build

For PCVR:

1. Update the version number

2. Rebuild the Windows build

3. ZIP the folder

4. Upload to itch.io or SideQuest PCVR

5. Add release notes

PCVR updates are simpler because there’s no bundle code.

6. Preventing Multiplayer Breakage

To avoid players joining incompatible rooms:

A. Store the version in Room Properties

Example:

roomVersion = "1.1.0"

B. Store the version in Player Properties

Example:

playerVersion = "1.1.0"

C. Validate on room join

If versions don’t match:

• Kick the player

• Show a message:
  “Please update your game to join this room.”

D. Update PlayFab Title Data

Store the latest version number in Title Data so the game can check it on startup.

7. Release Notes Format

A clean release note looks like this:

v1.2.0 Update: - Added new map: Volcano - Improved climbing physics - Updated cosmetics system - Fixed room code bug - Optimized lighting in Forest

Keep it short, clear, and readable.

8. Handling Hotfixes

Hotfixes are small emergency patches.

Use PATCH versioning:

1.2.0 → 1.2.1

Hotfix examples:

• Fixing a crash

• Fixing a broken spawn

• Fixing a missing collider

• Fixing a multiplayer disconnect bug

Hotfixes should be fast and focused

9. Long‑Term Versioning Strategy

As your game grows:

• Keep a changelog

• Keep old builds archived

• Use consistent version numbers

• Update PlayFab Title Data

• Keep store listings updated

• Avoid breaking changes unless necessary

A clean version history makes your game look professional.