Windows packaging, versions & quality variants
Create a Windows packaging entry point, centralize version updates in packaging, and provide High / Medium / Low first-run quality variants.
Ordinary code compilation no longer increments the version; a packaging run shares one UTC-based V<phase>-yyMMdd-HHmmss version across quality variants. Milestone dates advance the phase; successful compilation stamps the version. Required Perforce checkouts use project workspace settings and fail early on errors. Saved player preferences override bundled quality defaults, and the version remains visible across lobby pages. A common command/script workflow handles configuration, output and failure recovery.