A SCUM server's config folder holds a good dozen files. Four of them change how your server plays. The rest is administration, client leftovers or ballast. This page places every single one.
| Field | Role | Checked | What does this setting do? |
|---|---|---|---|
ServerSettings.ini | The server reads it | fully checked | The big file with all 437 server settings – from the player limit to the damage of individual weapons. |
RaidTimes.json | The server reads it | fully checked | When bases may be attacked. Only effective with the matching protection type in the ServerSettings.ini. |
Notifications.json | The server reads it | fully checked | Recurring announcements to all players – above all the warning before a restart. |
EconomyOverride.json | The server reads it | partly checked | The economy: price movement, restocking, trader funds and individual goods. |
GameUserSettings.ini | From the client, merely sits in the folder | not checked | Comes from the game client and also sits in the server's folder. It plays no role in running the server – resolution, mouse and graphics only concern the machine being played on. |
Input.ini | Game client only | not checked | The client's key bindings, some 30 kilobytes of them. No effect on the server. You never need to touch it. |
AdminUsers.ini | List of Steam IDs | format checked | Who has admin rights. One Steam ID per line, followed by rights in square brackets. |
ServerSettingsAdminUsers.ini | List of Steam IDs | format checked | Who may change server settings from within the game – a narrower circle than the admin list. |
WhitelistedUsers.ini | List of Steam IDs | format checked | Who may still join when the server is full. |
ExclusiveUsers.ini | List of Steam IDs | format checked | If anyone is listed here, only those players may join. An empty file means everyone may. |
BannedUsers.ini | List of Steam IDs | format checked | Who is banned. |
SilencedUsers.ini | List of Steam IDs | format checked | Who may not write in chat. |
On a self-hosted server you find it at SCUM/Saved/Config/WindowsServer/. On a rented server the panel usually calls the area “config files” – behind it sits exactly this folder.
Important for everything that follows: the server writes its settings back when it shuts down. Edit while it is running and you lose your changes. Stop first, then edit, then start.
ServerSettings.ini is the big one: 437 settings, from the player limit through loot to the damage of individual weapons. The other three are small but constantly got wrong because they are barely documented: RaidTimes.json for raid windows, Notifications.json for announcements and EconomyOverride.json for the economy.
Each of these four has its own page here and a check in the configurator.
Who may do what: admins, server admins, whitelist, exclusive list, banned players, silenced players. All six are plain text files with one Steam ID (17 digits) per line.
Only AdminUsers.ini also knows rights in square brackets – [GodMode] and [SetGodMode]. Without a bracket suffix, someone gets full admin rights.
ExclusiveUsers.ini is the dangerous one: put a single ID in it and nobody else can join your server. Leave it empty unless you explicitly want that.
Input.ini holds the game client's key bindings – no effect whatsoever on the server. GameUserSettings.ini is mostly graphics and sound settings of the same client.
On top of that come files from neither the game nor your provider: backups with .bak in the name and configurations of third-party tools. SCUM does not read those. They do no harm, but they clutter the folder.
People asking for help in Discord tend to push the whole folder along. Two things do not belong there.
Steam IDs. They are personal data and can be traced to a profile. Nobody needs them to answer a configuration question.
Access tokens. Configurations of third-party tools – Discord bots, for instance – often hold a token. Whoever has it can act in your bot's name. Such files never belong in a public message.
Our check points out both: we show Steam IDs shortened only, and files holding an access credential get a warning.
Drag it into the configurator – on its own or with the whole folder. Checking happens in your browser, nothing is uploaded.
To the configurator →