Ultimate Odycer · public preparation guide

Prepare your first local world

A bounded checklist for a B2B studio evaluating the self-hosted Zig server service.

1. Know the responsibility boundary

The service is intended to cover

The authoritative Zig server package and the licensed CCU capacity.
Versioned integration documentation and covered server updates.
Limited support within the written offer; priority support is quoted separately.
Optional premium templates and custom tools only when explicitly contracted.

The client studio remains responsible for

Hosting, cloud account, operating system, monitoring, backups and incident response.
Game client, content, community, player support and downstream monetisation.
Production secrets, DNS, certificates, database operations and access control.
Its own legal assessment and obligations in every territory where it operates.

2. Prepare the minimum environment

A dedicated Windows or Linux host controlled by the studio.
PostgreSQL 15 or newer; PostgreSQL is mandatory for durable production operation.
A unique high-entropy JWT secret stored outside source control.
A valid TLS certificate and private key for production authentication and gameplay.
TCP ports 7777 for gameplay and 2106 for login, exposed only when the service is ready.
The WebAdmin API on 8082, PostgreSQL and any cache kept private or loopback-only.

3. Define acceptance evidence before installation

Write down the target CCU, operating system, database version and recovery objectives.
Identify the exact client or engine integration and the required versioned API/SDK contract.
Require successful database migration, TLS verification, authenticated login and gameplay handshake evidence.
Exercise backup and restore in an isolated environment before opening access to players.
Record every remaining proxy, fixture or unvalidated integration as [Scaffolding / Proxy].

CCU is a licensing capacity dimension, not a universal performance guarantee. Results still depend on the studio's hardware, world logic, database design and network conditions.

4. Commercial and compatibility rules

The current public path is a non-binding interest declaration. It creates no order and accepts no payment.
Managed hosting is not included. A separate cloud-partner option may be studied later.
Custom tools are quoted against a versioned API/SDK boundary and do not force a Zig server update.
The custom-tool quote states the compatibility window; the current commercial target is at least 12 months.
Compliance features can produce controls and evidence, but they are not a blanket legal guarantee.

Résumé français

Le produit envisagé est un service B2B autour du serveur Zig autoritatif, auto-hébergé par le studio client. Aucun binaire public, achat ou hébergement géré n'est disponible à ce stade. Le client conserve la responsabilité de son infrastructure, de son jeu, de ses joueurs, de ses sauvegardes et de son analyse juridique.