Get started

Free trial Try any game free for 3 days. No card needed. Start a free trial Start a free trial

Game servers

All games

Guides / Squad / Mods and fixes

Squad server crashes or won't start after an update

After an Offworld update, restart so Update on start can download it. Then check mods built for the old version, new config keys, and the crash logs.

Updated , checked on Squad 10.6.1

When Offworld releases an update, the server does not change by itself. It is updated when it next starts, if Update on start is on. Restart first. If it still fails, the usual causes are a mod made for the old version, or a setting the update added to your config files.

1. Restart so the update downloads

  1. Open Startup. Check Update on start (1) is 1. It checks Steam for a game update every time the server starts. Players cannot join a server behind the current version, so leave it on.
  2. Check Beta branch is empty, unless Offworld gave you a private branch.
  3. Restart the server and watch the Console until it has finished starting.
The Startup page, with Update on start marked
  1. Update on start

Some Offworld releases update both the game and the server at once. The 10.6.1 hotfix was one. A player on the new version cannot play on an old server.

2. Find out if a mod is the cause

A mod made for the old version may not work after an update.

To check:

  1. Stop the server. In Files, move the numbered folders out of SquadGame/Plugins/Mods, for example into a folder you make called Mods-off.
  2. Start the server. If it starts, a mod is the cause.
  3. Move the mods back one at a time, restarting each time, until it fails.
  4. Check the mod’s Workshop page for an update. Offworld’s advice for a mod that will not load is to remove it, delete its download, and download it again.

See install Squad mods to put an updated mod back.

3. New settings are not added to your files

Offworld does not overwrite your config files in an update. A new setting is not added to a file you already have. Offworld’s wiki says to add it by hand. The game uses its own default until you do.

  1. Read the update’s release notes on the Steam news page for Squad.
  2. If a new key is named there, add it in Files, in SquadGame/ServerConfig. Use the file’s own style: Key=Value, one per line.
  3. Config Editor lists only the settings the file already holds, plus a few the panel knows the defaults of, marked Game default.

4. Read the crash files

The game can save a crash report. Add this to SquadGame/Saved/Config/LinuxServer/Engine.ini:

[CrashReportClient]
bAgreeToCrashUpload=true

Make a folder SquadGame/Saved/Crashes. After the next crash, a crashinfo-SquadGame... folder appears there. The log is SquadGame/Saved/Logs/SquadGame.log. The setting lets the game send crash reports to Offworld. Leave it out if you do not want that. This is from Offworld’s wiki, Server Administration page, “Getting Crash Dumps”.

If it does not work

  • It still will not start with every mod out. Open SquadGame.log and read the last lines. Ask support, and give them the crash folder.
  • It starts, but nobody can find it. See Squad server not in the list.
  • A layer will not load. Check the layer name for a typo, and that it is not in ExcludedLayers.cfg or ExcludedLevels.cfg.

More about the game: Squad servers.

Sources: store.steampowered.com: 393380, squad.fandom.com: Server Configuration, squad.fandom.com: Unable to load a Layer, squad.fandom.com: Unable to Find Server, squad.fandom.com: Uploading a mod to a dedicated server, squad.fandom.com: Server Administration

Squad serversAll Squad guides