Game servers
The console, files, schedules and backups of a game server. Game servers cannot be ordered yet.
Built, not open to the public yet
This feature is built and has been tested against simulated hosts and a test database. It has not yet been proven on real hardware, and nothing here can be ordered today.
Not there yet
- Game servers cannot be ordered yet. Minecraft (Paper) comes first, then FiveM.
- Real-host testing of the console, file access and network isolation is still to come.
This page describes the game server pages as built. Game servers are not on sale: the first game will be Minecraft (Paper), then FiveM. See game servers. No prices exist for them yet.
One page per game server
A game server has a page with its connection details, resources, startup variables and four tabs: Console, Files, Schedules and Backups. Some games ask you to accept the game's licence before the server can start. Files, schedules and backups open once the server has finished setting up.
Console
The console shows the game's output, starting from its recent history, and lets you type commands. If the node restarted its management service, input can be unavailable until you restart the server; the console says so.
Files
- Browse, read, edit, create folders, rename and delete files in the server's data directory from the panel. Large or binary files go by SFTP, with a login the panel gives you.
- Lists show the first 5000 items; use SFTP for the rest.
- Your role needs the file permission. Owners, admins and members have it; viewers and billing contacts do not.
- File access in production is switched off until an extra isolation layer between servers is built and proven. Until then the panel answers that files are unavailable.
Schedules
A schedule runs tasks on a timetable in the time zone you choose: a power action such as a restart, a console command of your own text, or a backup. The platform runs it, and checks your permission again each time it runs. Not every plan includes schedules; the page says so when it does not.
Backups
- A backup copies the server's data directory, encrypted under your organisation's key. It can be taken on a schedule or by hand.
- If the game confirmed writes were paused, the backup is consistent; otherwise it is crash-consistent and the page says so.
- Restoring needs the server stopped and replaces everything written since the backup. A damaged backup is refused and nothing changes.
- Files a template names as secret (for example a remote-console password) are left out of the archive. Which files that covers depends on the game.
Retention is by count: a scheduled backup removes the oldest unlocked scheduled one.
Not built
- Your own ignore list for backups, and download of a backup on demand.
- Off-site copies of game backups, and age-based retention.
- Schedules triggered by game events, and a "run now" button.