Help
Foxcore help for creating a game server, the join host, packs, ports, console, files, backups, and the Pro subscription.
Getting started
Create picks a pack, region, and size. It stays closed until a ready node has free ports — there is no fake start.
A VPS keeps the same instance_id and allocations as a game server. Guests are floki with libvirt, and that isolator cannot define a domain yet. Public create does not offer VPS. Machines share this contract later.
A pack is a versioned image, default ports, and a start command. It is not an egg.
Players join with the join host (IP:port). Many servers share one IPv4. Foxcore does not mint a dedicated address per person.
A hostname does not replace IP:port. Foxcore does not publish DNS. The panel on Cloudflare is not the game path.
On a server
Change pack on the same instance. instance_id and ports stay; the next job is switch_title.
Power controls live on the instance header. Each change queues a job and returns accepted — the panel does not wait on the node. While a power or switch-title job is open, the header refreshes until it settles.
Console attaches when a ready node shows observed running. Frames fan in through the control plane; an empty pane is not a log replay.
The volume lives on the node. When the session is ready, browse, download, upload, mkdir, and delete via files RPC — not a host editor or a fake world folder.
Backup and restore are D1 jobs on the instance. Restore prefers on-disk inventory from backup.List.