SCUM Easy Admin
DonateDE
Home › Server settings › Server configurator

SCUM Server Settings Generator

Build the ServerSettings.ini for your SCUM server step by step, have an existing configuration checked for errors and download the finished package. The configurator runs entirely in your browser – nothing is uploaded.

Where do you want to start?

Pick a template as your starting point. You can change every single value afterwards.

Or have your existing configuration checked

Drop your ServerSettings.ini here – or the whole config folder at once. A ZIP works too. Checking happens in your browser, nothing is uploaded.

Two ways: one file or the whole folder

Just the ServerSettings.ini

Perfectly enough. You get the score, every nonsensical value, contradictions between settings and the notes on obsolete lines.

The whole config folder

Drag all files in at once – or the folder itself. We then also check raid windows, announcements and the economy and tell you what every file in your folder actually is. Above all we find faults that only arise from the interplay: raid windows that never apply, say, because the ServerSettings.ini selects a different protection type. Taken on its own each file is then correct – only the combination is wrong, and that is exactly what nobody sees who looks at one file at a time.

or drop files and folders here

🔒The whole folder stays on your machine too: nothing is uploaded, everything is read in the browser only. Steam IDs from your admin and ban lists are shown shortened, and if a file holds an access token we warn you before you pass it on.

⚠A tip after updates: SCUM adds missing keys by itself but never clears out removed ones. The check finds such ballast and tells you which edition abolished it.

Why this works without uploading

When you pick a file, your browser does not pass it to the website but only to the script running in this window – through its built-in reading function. No network connection is made, so the file never leaves your machine. This page fetches exactly two things from the server: the descriptions of the settings and the templates for the full package. Both are plain downloads that carry no data from you. What you configure is remembered locally by your browser so the work survives a reload; “Reset everything” clears it again.

What would you like to configure?

Pick the topics you want to go through. Everything else keeps the value from your template – the finished file always contains all 437 entries regardless.

Done

The package contains every config file in the right structure plus a short guide. Stop the server before installing it.

Free – and meant to stay that way

This section and the tool behind it are free, with no ads and no account. If it was worth something to you, you can leave something voluntarily. You get nothing extra in return: no subscription, no premium tier, nothing gets unlocked. Everything stays the same for everyone.

Leave something, voluntarily

Where is the ServerSettings.ini located?

On a server you run yourself it sits in the server directory under SCUM\Saved\Config\WindowsServer\ServerSettings.ini. On a rented server — GPortal, Nitrado, PingPerfect and the rest all work the same way — you reach the very same file through the web interface, usually under “config files” or “settings”.

Either way the route is the same: download the file, drop it into the check above, upload the changed version afterwards. Stop the server before you do — a running SCUM server writes its settings back on shutdown and would overwrite your file again. For everything else in that folder, see the beginner guide to SCUM server files.

In single player the very same file exists, just somewhere else: under %LocalAppData%\SCUM\Saved\Config\WindowsNoEditor\ instead of WindowsServer. The configurator builds it for you all the same — how to put it in place is covered under changing SCUM single player settings.

What are the best SCUM server settings?

There is no single best configuration; it depends on what your server is meant to be. The configurator gives you four starting points: the default values exactly as SCUM ships the server, a relaxed PvE setup with more time and less punishment, a classic PvP setup close to default, and a hardcore variant where every mistake costs you. From there you change whatever does not suit you, one value at a time.

Every entry in the file has its own page here, with an explanation, a sensible range and what happens if you crank it too high. If you first want to understand what the file actually does, start at SCUM server settings explained.

How do I increase loot and puppets?

Those are the two most common wishes, and both come down to a handful of values. Loot quantity is governed by SpawnerProbabilityMultiplier and SpawnerExpirationTimeMultiplier — one decides how much appears at all, the other how long it stays around.

For puppets the key value is MaxAllowedPuppets, together with PuppetHealthMultiplier for how tough they are. Both cost server performance once you push them far; the article on why a SCUM server stutters explains where that limit comes from.

Can I check my existing server config?

Yes, that is what the second route above is for. Drop in your ServerSettings.ini, or the whole config folder at once, and you get a list of nonsensical values, contradictions between settings and outdated lines. The interesting errors are the ones that only emerge from the interplay of several files — raid times in RaidTimes.json, say, that never take effect because ServerSettings.ini specifies a different protection mode.

After a SCUM update the check is especially worth running. The game adds missing keys on startup by itself, but never clears out removed ones. A config file kept over a long time only ever grows. The check tells you which line disappeared with which version.

What is in the finished package?

You get either the ServerSettings.ini on its own or the complete package as a ZIP. It contains every config file in the right structure — ServerSettings.ini, RaidTimes.json, EconomyOverride.json and Notifications.json — plus a short guide on installing it.

The finished file always contains every entry, including the ones you never touched. That is deliberate: a complete file is easier to compare when the next update adds something.

← Back to overview