Administration
Resellers and packages
Packages are the products you sell or hand out: a game with a slot range and resource limits. Resellers run their own customers inside your panel, with quotas, their own packages and their own branding. Both are optional: a clan running its own servers can ignore this page.
Packages
Open Packages (needs packages:read; changing them needs packages:write).
| Field | Meaning |
|---|---|
| Name, description | What customers and billing staff see |
| Game | Fixed once the package exists |
| Slots: minimum, maximum, default | Player slots a game server of this package may have (inside the game’s own range) |
| CPU limit | 100 % = one core; 0 = unlimited |
| Memory limit | 0 = unlimited |
| Disk quota | File manager, SFTP and upload quota; 0 = unlimited |
| Datacenters | Where its game servers may be placed; empty = anywhere |
| Variable defaults | Startup variables new game servers start with (not passwords: every server gets its own) |
| Start after install | Start new game servers as soon as the game is installed |
| Enabled | Disabled packages cannot be ordered; existing game servers keep running |
- Global packages (made by administrators) can be sold by every reseller for the games it is allowed. A reseller’s own packages are visible to that reseller only.
- A package that game servers use cannot be deleted: disable it instead.
- Changing a package does not change existing game servers. Apply it to one with Change package on the game server (administrators and the owner’s reseller), or from billing.
Creating a game server from a package
On Services → New, pick the package: it fixes the game and the slot range, and the limits come from it. The node is optional: without one the panel picks an online node that runs the game’s operating system, sits in an allowed datacenter and has enough memory left (its memory x the overcommit percentage minus the memory limits of its game servers), the one with the most room first. Customers and resellers never see nodes; they choose a datacenter at most.
Resellers
Open Resellers (administrators, resellers:read / resellers:write).
- Add a reseller: a name, then optionally
- Quotas (0 = unlimited): customer accounts, game servers, slots, memory and disk (the sum of the game servers’ limits). A change that would go over a quota is refused with quota exceeded; lowering a quota below what is in use only stops further growth.
- Allowed games and allowed nodes (empty = all).
- Branding: product name, accent color and help link. The reseller’s customers see these instead of the panel’s own.
- Create the reseller’s account(s) on Users: role Reseller, choose the reseller.
A reseller account then:
- creates and manages its own customers (users and sub-users) and their game servers;
- creates its own packages and sells the global ones for its allowed games;
- sees its quotas and what is used on its dashboard;
- reads the audit log of its own customers;
- creates billing API keys for its own WHMCS (see Billing and WHMCS).
It never sees nodes, datacenters, panel settings, other resellers or their customers: anything outside its tenancy answers not found. A reseller with accounts cannot be deleted; delete or move its accounts first.