Advertisement

Generate a Squad Server.cfg

Squad keeps its configuration in several separate files side by side in one folder, and every file is responsible for one thing.

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 "My Squad"
MaxPlayers 80
NumReservedSlots 2
ServerPassword 
IsLicensedServer 0
ShouldAdvertise 1
AllowTeamChanges 1
PreventTeamChangeIfUnbalanced 1
IsStandby 0

Advertisement

The Server.cfg format

Identity and gameplay limits go in Server.cfg, written as simple command-and-value lines. Admins, RCON and the map rotation are kept in separate files of their own, and the server reads each one on its own terms — nothing is merged, so a setting in the wrong file is ignored.

Advertisement

The mistake that wastes an evening

The mistake people make most is writing admin definitions or the map rotation into Server.cfg. Each belongs in its own file, and since there is no warning, you end up with a server that looks properly configured and has no admins.

Rather not run the server yourself?

These tools are free and funded by the two hosting services we run. If you want a server that is already set up, here they are.

Advertisement