Docs Running a server
Updating a server
Moving a server to a new build, what to keep, and what to back up.
A build's game and server are one version. When a new build comes out:
- Stop the server (Ctrl+C, or
systemctl stop legacysf-server). - Replace the server's program and
tools/with the new build's. Keep everything else. - Start it again. It checks its
server.cfg, data and packs as it starts.
A server older than Team Vanilla accepts is taken off the list, and its log says so. A player whose game is older or newer than your server is told which of the two is out of date.
In a container, build the image again from the new folder; the volume keeps everything the server wrote.
What to back up
| Back up | Why |
|---|---|
server.cfg, channels.cfg, games.cfg, staff.cfg, shop.cfg | your settings |
accounts/ | what your server knows about each player: their roles, bans and custom items here |
weapons/, maps/, chars/ | your packs' sources (the built packs can be built again) |
server.key | the server's identity: keep a copy safe and to yourself, never in a backup that leaves your hands |
A lost server.key means a new code from the control panel. A key you think was copied should be revoked there at once.