SYSTEM
LIVE CONTROL ROOM
Overview
Matchmaking, capacity, and infrastructure at a glance.
CAPACITY
Node health
ACTIVE
Running ZW3 servers
PRIVATE SNAPSHOTS
Backups
Important database snapshots are managed separately from optional full-game backups. The policy below controls game copies only.
Loading backup policy…
Full game backups are optional and separate from important database snapshots. Existing game backup records below are not deleted by a policy change.
Immutable backup receipts
Restore reviewed backup
Legacy game restores require an enabled game-backup policy, a fresh safety receipt, and a reviewed fingerprint. Database snapshots are not restored through this game-file workflow.
Backup and restore jobs
A failed restore or timed-out job stays blocked for recovery review. No automatic retry or deletion of private snapshots occurs.
DEDICATED ZW3
ZW3 Servers
Managed instances and signed agent actions across matchmaking and manual testing.
Instances
Port, match, map, process, and health status.
SHARED ALLOCATION
Game Workspaces
Independent game copies can offer public capacity, serve restricted development matches, or run manual tests. Changes to participation apply through the shared allocation path.
Managed workspaces
Node binding, participation, current lease, and release gates.
Add workspace
Registers an isolated workspace path. Copying game files and binding an attested agent are separate setup steps.
Optional DEV test accounts
DEV test accounts
READY-BUILT FILES
Upload Source
Upload a ZIP containing ready-built files. Included paths are added or replaced; absent files are retained. Upload never compiles or deploys files.
New source archive
Maximum ZIP size: 10 GiB. Sound tools and local logs, cache and player settings are skipped, not installed.
Source archives
Download the exact uploaded archive for review or backup.
Next step
After upload, choose Continue to Updates, select the server, and click Update server. No preview or release approval is required.
GUIDED WORKSPACE UPDATE
Updates
Upload a package, choose the server to update, and click Update server.
Server update coverage
Every registered game node is listed here with its agent-attested installed build. Controlled updates remain available only for nodes bound to a managed workspace.
Choose target and package
Choose the server and uploaded package. Update server pauses new matches, installs the files and resumes the selected server. No separate preview, release approval or runtime test is required.
Update selected server
One click installs the selected package. No preview, approval or gameplay checklist is required. Public servers return to the public pool after installation.
Optional technical preview
Review changes
See added, replaced, unchanged, and retained files before anything is changed.
Deploy reviewed update
This uses the reviewed preview fingerprint and creates a private rollback journal.
Recovery, downloads, files and technical history
Rollback an update
Restore overwritten files and remove files introduced by the selected successful deployment.
Game files
Browse game files, download them or delete up to 25 selected old files. Folders are download-only. Credentials, configuration and root executables are protected.
Update history
Agent results, fingerprints, and recovery status.
Game lifecycle log
MATCHMAKING CATALOG
Playlists
Name, maps, game settings, server pool — save and done.
Playlists
Hold the side grip and drag to change the catalog order. Keyboard: Arrow Up / Down. Changes save on release; Escape cancels.
Order applies to the manager and eligible player catalogs; active matches are unchanged.
ZW3 // PLAYLISTS
Add playlist
Name, maps, game settings, server pool — save and done.
IMMUTABLE ARTIFACTS
Releases
Verified releases are registered automatically after technical checks. No separate developer or administrator approval is required. Installing an update does not require a release approval.
Release register
Installed versions and technical evidence recorded by the backend.
Deployment verification status
An agent manifest digest and file application receipt do not establish readiness or runtime test evidence. Release verification is recorded only by the trusted backend process.
Technical release history and recovery
Register an existing verified deployment
Requires a successful deployment with trusted file inventory, readiness, admission, Stats isolation, and cleanup verification. This form cannot create that evidence.
Record verified release on installation
Records a technically verified release only when it exactly matches this drained workspace's already verified deployed files and current generation. This does not deploy or copy files.
Deployment bridge
Signed update and rollback jobs are available under Deploy & Game Files. Private backup and restore jobs are available under Backups. A successful file overlay alone is not a verified release: readiness, runtime tests, admission and Stats isolation are still required.
SERVER POOL
Nodes & Ports
Manage resources, heartbeat, capacity, and UDP port allocation.
Server nodes
Draining keeps active matches running while preventing new reservations.
QUICK PLAY
Matchmaking
Monitor queues, parties, and the match lifecycle together.
Queue
Parties
Matches
PUBLIC TRANSPORT
Discovery / Master
Transport, publication, and verification are reported separately so an empty list is never presented as proof of playability.
REPORTED HERE
Manager context
VERIFICATION BOUNDARY
Runtime evidence
This manager endpoint reports backend context only. HTTP compatibility, UDP binding, a real Windows game registration, and a successful client join require their own operational checks.
Public eligibility remains enforced by release, admission, Stats, process, port, and workspace policy gates.
RELATED CAPACITY
Relay transport
Open relay health without treating it as discovery or game registration evidence.
DIRECT FIRST
Relay
Region, latency, packet loss, and relay load.
Relay nodes
ACCOUNTABLE ACTIONS
Jobs & Audit
Signed agent jobs and attributed manager actions.
Agent jobs
Audit log
TRUST & SAFETY
Reports & Bans
Read-only overview. Account actions require the existing Stats-authorized admin session.
Reports
Active bans
ZW3 // HELP
Help & guides
Step-by-step instructions for updating ZW3, testing DEV builds and preparing public matchmaking. Reading this page never changes a server.