Simplify single-server launch flow
This commit is contained in:
@@ -26,12 +26,14 @@ the agent owns local execution and its durable operation journal.
|
||||
progress and errors. Wait for verification before launching. Hosts report
|
||||
connection and readiness separately; deployment also checks the particular
|
||||
game files, image, capacity and ports required for the launch.
|
||||
6. Launch a server or collection. The latest game files and default runtime
|
||||
are selected automatically. An advanced runtime override is
|
||||
available for images an admin has already prepared on the destination host.
|
||||
If the latest files change after previewing, refresh the preview
|
||||
before launching.
|
||||
Apply saves the requested lobby IDs. Provisioning selects a host and atomically
|
||||
6. Open **Create server**, choose a game and map, and review the automatic
|
||||
readiness checks. Launch collections separately from **Fleet → Collections**.
|
||||
The latest game files and default runtime are selected automatically.
|
||||
**Advanced settings** in the single-server dialog includes a runtime override
|
||||
for images an admin has already prepared on the destination host, along with
|
||||
optional network overrides. If the latest files change after the checks run,
|
||||
let the dialog recheck the setup before launching; **Retry checks** also rechecks it.
|
||||
Launching saves the requested lobby IDs. Provisioning selects a host and atomically
|
||||
reserves UDP/TCP ports when capacity is available.
|
||||
An available Plutonium key from the game pool is reserved for each launch.
|
||||
Its assignment survives stops and rebuilds and ends after confirmed removal.
|
||||
|
||||
Reference in New Issue
Block a user