Squad Server.cfg generator

Squad spreads its configuration across several files in the same folder, and each one owns a specific job.

Visual Settings

source Format
Identity

Server name in the browser.

Gameplay

Lets players switch teams.

Blocks switches that would unbalance the teams.

Holds the server in standby. Note that admins and the map rotation live in their own separate files, not here — putting them in this one silently does nothing.

Players & Access

Slot limit. The map layer, not the player count, is what sets your memory requirement.

Slots held for whitelisted players.

Join password.

Network

Whether the server runs with an official licence, which affects how it is listed.

Publishes the server to the backend. Squad registers with Epic services rather than answering queries directly, so this is what makes it visible.

Server.cfg

ServerName "Spawnly Squad"
MaxPlayers 80
NumReservedSlots 2
ServerPassword 
IsLicensedServer 0
ShouldAdvertise 1
AllowTeamChanges 1
PreventTeamChangeIfUnbalanced 1
IsStandby 0

How Server.cfg syntax works

Server.cfg holds the server identity and gameplay limits in a simple command-and-value form. Administrators, RCON and map rotation each live in their own separate files, and the server does not merge them — a setting in the wrong file is ignored.

The mistake that costs people hours

The most common mistake is putting admin definitions or the map rotation into Server.cfg. They belong in their own files, and because nothing warns you, the result is a server with no admins that otherwise looks correctly configured.

Support & Help