Survival Guide

SCUM

Detailed connection, admin, file, settings, mods, backup, wipe, and troubleshooting notes for SCUM dedicated servers.

Connect & First Checks

Before editing files

Use the IP and game port from the game panel. Browser listings can lag after restart, so test direct connect or Steam favorites first.
If a password is set, give players the exact password and confirm they are on the same game branch/version.
For admin work, use Steam64 IDs and the admin file exposed by the panel template.

Stop server before edits

Saved/Config/WindowsServer/ServerSettings.ini	Primary server rules. Depending on current build/template, server name, password, max players, loot, vehicles, damage, respawn, and economy values may be exposed here or through panel variables.
Saved/Config/WindowsServer/AdminUsers.ini or AdminUsers.txt	Admin Steam64 IDs. Add one ID per line or in the format required by the generated file, then restart.
Saved/SaveFiles or server save directory	World/state data. Back this up before wipes, economy changes, or large config changes.

High-use values

Server name	Public name displayed in the server browser. Keep it short and searchable.
Server password	Makes the server private. Restart after changing.
Max players / slots	Usually controlled by product slots and startup args. Do not raise above purchased slots without a plan change.
Loot/economy/rates	SCUM has many balance values. Change in small batches and keep a backup of the previous config.
Admin Steam64 IDs	Use steamid.io or Steam profile conversion, then restart after editing.

Staff access

Add your Steam64 ID to the admin users file exposed in File Manager.
Restart the server after editing admin lists.
Use in-game admin commands only after confirming admin is active. If commands fail, re-check Steam64 format and server restart status.

Install carefully

SCUM mod support and Workshop behavior can vary by game build and template. Use the panel mod manager when present.
Do not manually delete generated mod/config folders while the server is online.
If players cannot join after a mod change, verify they have the same mod set and restart after removing the last changed mod.

Protect player data

Back up save data plus ServerSettings/AdminUsers before changing loot, economy, vehicle, or wipe settings.
For a full wipe, stop the server, back up the save folder, then remove/replace the world/save files recommended by the template.
For rollback, restore both save data and matching config files from the same timestamp.

Common tickets

Server not in browser	Wait several minutes after startup, confirm it is fully online in console, then test direct IP/Steam favorites.
Admin not working	Wrong Steam64 ID, wrong file, or no restart after edit.
Players kicked/mismatch	Check password, branch/version, and any enabled mods.
Settings not applying	Server was edited while running or a panel variable overwrote the file at startup. Stop, edit, save, start.

Docs and sources