Docs Running a server
Running a server
What a Soldier Front Legacy server is, what it needs, and the steps from download to the list.
LegacySFServer is the server Team Vanilla runs, for anyone to run on Windows or Linux. Players sign in with their Team Vanilla account, find your server on the list (or join it by address), and play. Their rank, record and SP are Team Vanilla's and follow them everywhere; what your server adds of its own stays on your server.
What you need
- A machine that stays on: a PC at home, a VPS, a dedicated server, or a small ARM board.
- Windows, 64-bit.
- Linux on x86-64 or ARM64, glibc 2.28 or newer (Debian 10, Ubuntu 18.10, RHEL 8 and later), with libcurl and the system's certificates.
- A UDP port players can reach from the internet: 27240 unless you choose another. At home that means a port forwarded on your router. Shared web hosting usually has no UDP port a program of yours may open, so it will not do.
- A Team Vanilla account: the one you play with. The server is registered to it, and you are its Owner.
- Upload: pack downloads use your upload, and
upload_kbpskeeps them from crowding out the matches.
The steps
- Install it: unpack the server, name it in
server.cfg, run it once to make its key. - Register it: get a code on Team Vanilla's control panel and run the server with it.
- Let players in: forward the UDP port and allow it through the firewall.
- Start it normally. It is listed once Team Vanilla can reach it.
- Run it day to day: on Linux (systemd or a container) or on Windows.
Then make it yours: staff, channels, the shop and packs.
What is in the folder
| Name | What it is |
|---|---|
LegacySFServer.exe / legacysf-server | the server (Windows / Linux; ARM64 in arm64/) |
data/ | the Soldier Front game data: the server reads the maps from it (where bots walk, what a soldier can see, what a wall stops) |
server.cfg | its settings (server.cfg) |
server.key | its identity, made on the first run. Not in the download: every server makes its own. Never share it. |
channels.cfg | its channels: the original thirteen to start with |
staff.cfg | its staff, by Team Vanilla account (empty to start with) |
shop.cfg | its own shop: your packs' items, its capsules, base items' prices |
accounts/ | what this server knows about each player: their role here, bans and mutes here, the custom items they own here, their loadout here |
weapons/, maps/, chars/ | your packs' sources |
packs/ | your built packs, served to players |
recordings/ | every match, kept 7 days |
logs/ | one log a start |
tools/ | lsfpack (builds and checks packs); on Windows also sfcheck (checks maps and data) |
files.sha256 | every file here and its SHA-256 |
legacysf-server.service, Containerfile | Linux only: the systemd unit and the container image |
What a server cannot do
A community server is a machine its owner controls, so the things that matter everywhere are kept where no server can change them. A server cannot add SP or Coins, write anyone's rank or record, sell a base item below Team Vanilla's price, change a base gun's numbers, see a password, or read anyone's whispers and mail. Yours and Team Vanilla's has the whole of it.