Skip to content

Configuration and Admins

SCUM commonly stores generated settings beneath its saved configuration directory. Use the Game Panel file search and edit the server copy, not a local client configuration.

Change one group at a time and keep the original values. Settings may control:

  • Server name, description, password, and slots
  • Loot and item spawning
  • Puppet and encounter behavior
  • Vehicles
  • Damage and stamina
  • Time, weather, and day speed
  • Base building and raid protection
  • Economy and trader behavior

The game may rewrite obsolete values after an update. Compare generated defaults after major patches.

Use the player’s 17-digit SteamID64 in the server’s admin-user list or admin setting. Put one identifier per entry in the format expected by the generated file.

Restart, join, and test a harmless admin command before relying on access. Never grant admin by player display name.

SCUM uses separate lists/settings for exclusive or reserved access and bans. Keep a note explaining each ban and the responsible administrator. Remove duplicates and blank entries if list parsing fails.

  1. Stop the server.
  2. Back up the configuration and save.
  3. Edit and save the file.
  4. Start and check for parsing warnings.
  5. Join and verify the changed setting.