Your first game server

The path from a connected node to a server players can join. No node yet — start with Connect a node.

1. Add a game to the catalog

Open Games. At the bottom of the page is the Starter set: ready-made games with the image, ports, server settings, maps and mods already configured — Minecraft Java, Counter-Strike 1.6, Counter-Strike 2 and SA-MP.

Tick the games you want.
Under Where to install, pick the nodes: All nodes (including ones connected later), Location nodes or Selected nodes.
Click Add selected.

A game that isn't in the set is added with Add a game — see Game catalog.

2. Wait for the node to install it

The table on the Games page has a row per game and a column per node. The status in a cell:

installed — the node has confirmed the game; servers can be created on it;
installing — the settings haven't reached the node yet, e.g. it's offline; it gets them when it's back;
error — the last attempt failed and the panel retries on its own. Details are on the game's page, Nodes tab.

It usually takes a few seconds. The node downloads the game's Docker image when the first server is created.

3. Create a plan (optional)

A plan is what you sell: the server's resources (memory, CPU, disk) and pinned settings such as the slot count. Plans are created under Plans. Without one a server gets the defaults: 2 GB of memory, 1 CPU core, no disk quota.

Editing a plan doesn't touch servers that already exist. To apply the change to a server, open its Settings tab and click Reapply in the Plan row. More in Plans.

4. Create the server

Open Game servers → Create a server (or press C on that page) and fill in the form:

Game and plan — a game from the catalog and, if there are any, a plan for it.
Placement — Automatically (the panel picks the node with the most free memory) or Specific node. Nodes where the server can't go right now are shown with the reason: offline, draining, game not installed.
Server settings — name, map, password and the game's other settings. An empty field means the default. Settings the plan pins are locked. Secrets such as the RCON password are generated for each server.
Starter set — maps and mods installed right after creation (if you have built such sets under Maps and mods).
Your own domain — the address players see instead of the node's IP. It can be set later too.

The server appears at once. On first start the node downloads the game image — the server page says "Downloading the game image" meanwhile, which can take a few minutes. Then the container starts.

5. Check that it works

On the server's page:

Overview — the Address for connecting players (IP or domain and port) and the In game block: online, player count, map. The block is there when the game has server polling set up (the starter games do).
Console — the server's output while it starts; you can send commands here too.
Tasks — what the panel did with the server and how it ended.

All the tabs are covered in Managing a server.

The server runs but players can't connect — it's almost always the firewall: see Game server ports.

6. Hand the server to a customer

A customer sees only their own servers in the panel and doesn't create them — you or your billing system hand them out. To give a server away:

Create the customer an account with the Customer role (see Users and roles) if they don't have one.
On the server's Settings tab, in the Owner row, click Change and pick the customer's account.

The owner starts and stops the server, uses the console, files, backups, maps and mods, and changes the settings marked "owner". They can open part of this to friends and helpers on the Access tab.

Selling through a billing system (the WHMCS module or your own one over the HTTP API) — it creates servers and hands them to customers itself.