SCUM Server Hosting

What is a SCUM server and why rent one?

A SCUM server is a dedicated process that runs the map, player characters, vehicles, bases and economy of Gamepires’ survival game around the clock. SCUM has no in-game “host” mode, so anyone who wants a persistent community either joins the official servers or runs their own copy of the SCUM Dedicated Server.

The advantage of your own server is that you set the rules: loot density, puppet (zombie) count, day and night length, the PvP/PvE balance, vehicle limits, starter gear and economy prices are all changed through ServerSettings.ini and related config files. Clans, roleplay (RP) communities and friends-only PvE worlds open their own servers precisely for this flexibility.

SCUM simulates a large Unreal Engine open world, so it is not a lightweight game server. According to the community wiki, the server uses about 8 GB of memory with nobody connected, which makes stable hosting on a home PC or a low-memory shared environment difficult. That is why memory and single-core CPU speed are the first things to check when choosing SCUM server hosting.

Which operating system does the SCUM Dedicated Server run on?

The SCUM Dedicated Server officially runs only on 64-bit Windows: SCUMServer.exe will not start on 32-bit systems and the publisher provides no native Linux build. The community wiki notes that setup has been tested on Windows and should work on any Windows host that can install the Visual C++ and DirectX components in the _CommonRedist folder.

There are community Docker images that run the server on Linux through Wine or Proton, but they are not officially supported, can break after game updates and leave you without help from the developer. For a long-lived community server we recommend a VDS running Windows Server 2022.

Server files are downloaded with SteamCMD using an anonymous login. The wiki specifically warns you to use the correct app ID: for the SCUM server use 3792580 and do not confuse it with another SCUM server app on Steam.

steamcmd +login anonymous +app_update 3792580 validate +quit

The server files take up about 8 GB; the wiki recommends keeping at least 15 GB free for saves and updates.

How much RAM does a SCUM server need per player count?

A SCUM server consumes memory quickly as the player count grows: 12–16 GB is a realistic starting point for a 16-player community and 24–32 GB for a server approaching 64 players. The table above summarises these estimates; the exact need depends on loot density, vehicle count, number of bases and the puppet limits in your config files.

The factors that affect memory most are:

• Persistent objects on the map: player bases, chests and dropped items accumulate over time; on servers that go months without a wipe, memory use keeps rising.
• Vehicles: every physics-simulated vehicle adds CPU and memory load; capping vehicle numbers in the config noticeably improves performance.
• Puppets and animals: AI entities depend on single-core speed, and high values lengthen the server tick.
• Player spread: the more players spread across the map, the more areas the server simulates at once.

On the CPU side, a few fast cores are worth more than many slow ones. On a LIONFIN VDS the cores are dedicated to you, so busy neighbours do not affect your game’s smoothness. NVMe storage matters because SCUM constantly writes game state to its SCUM.db database; on a slow disk you feel stutters at save time. When planning memory, also leave 2–3 GB for the operating system.

Should I choose a game server package or a VDS for SCUM?

For SCUM the page lists VDS packages: you can install the server on a VDS yourself or open a support ticket and request a ready-made installation. SCUM’s high memory needs and Windows requirement make it a better fit for a virtual server with dedicated resources than for a typical shared game package.

With a VDS you keep control over:

• The Windows Server version, firewall rules and remote desktop access.
• Side services on the same machine, such as a test server, a Discord bot or a stats website.
• Upgrades: when your community grows you can move to a larger plan with more RAM and cores.
• SteamCMD updates, restart times and backup schedules, set to your own timetable.

In return, operating system updates and server maintenance are your responsibility. To compare both models, read game server package or VDS?. We do not quote fixed package capacities here; compare the current RAM, core and disk values in the package table on this page against the estimate table above.

If you are new to server administration, start with a small group for the first week, watch memory and CPU usage, and only then announce the server publicly. That way you size resources from your own server’s real data rather than from guesses.

Which ports does a SCUM server need?

By default a SCUM server uses three consecutive UDP ports: the game port, the next port as a raw UDP socket and the one after that as the Steam server browser query port. The sample configuration from the community wiki looks like this:

If you change the game port with the -port=7777 launch parameter, the other two shift accordingly. To run a second server on the same machine, use a range such as 7780–7782. The wiki also warns that the query port must not fall within 27020–27050, a range used by the Steam client.

Create inbound rules for these ports in Windows Defender Firewall. If you do not use RCON, leave the TCP port closed; if you do, restrict access to your own IP address.

Where are SCUM server settings configured?

A SCUM server’s behaviour is defined by launch parameters and the ServerSettings.ini file. The file is created on first run in the server’s SCUM/Saved/Config/WindowsServer folder, alongside files such as AdminUsers.ini, which holds the admin list. For changes to take effect, stop the server, edit the file and start it again.

Common launch parameters:

• -log: opens the console log; essential for troubleshooting.
• -port=7777: sets the game port.
• -MaxPlayers=64: sets the player limit and overrides the value in ServerSettings.ini.
• -nobattleye: disables BattlEye; the community wiki does not recommend it.

ServerSettings.ini contains hundreds of options: server name, password, message, PvP rules, loot and puppet multipliers, day length, vehicle limits and more. Setting names can change with game updates, so after every major patch it is safest to generate a fresh default copy and carry your values over by comparison. Admin commands are typed into in-game chat with a # prefix; to use them your Steam64 ID must be listed in the admin file.

Can you mod and customise a SCUM server?

SCUM has no general mod system tied to Steam Workshop; server customisation mainly happens through config files, economy and loot settings, and admin tools. So a “modded SCUM server” usually means one enriched with altered loot tables, custom trader prices, starter kits and community bots.

Common customisations:

• Economy: trader buy and sell prices and stock; the main tool for balancing the economy on RP servers.
• Loot and spawns: item spawn rates, puppet density, animal count and vehicle spawn limits.
• Community tools: external bots that read server logs and push kill feeds, player stats or shop systems to Discord. These usually run as a separate process on the same VDS.

Never upload executables of unknown origin to your server; a bot running with administrator rights can access the whole machine. Leave enough memory headroom for bots and helper services, since SCUM already uses most of the RAM. If you prefer to keep Discord bots separate, there is also Discord bot hosting.

How do you improve SCUM server performance?

The biggest performance gains on a SCUM server come from limiting the number of AI entities, vehicles and persistent objects that build up on the map. Reviewing these settings before buying bigger hardware gets you a much smoother game from the same machine.

Steps that work in practice:

1. Scheduled restarts: memory use climbs when SCUM runs for a long time. Restarting once or twice a day, with advance warnings in chat, is the most effective measure.
2. Puppet and animal limits: lowering the number of simultaneous AI reduces server-side lag in crowded areas.
3. Vehicle limits: keep total and per-type vehicle counts reasonable and let abandoned vehicles despawn after a set time.
4. Base and item cleanup: clear bases of long-inactive players according to your rules and keep the despawn time for dropped items short.
5. Up-to-date Windows and drivers: apply OS updates outside play hours and do not run other heavy processes in the background.

Watch the SCUMServer.exe memory curve in Task Manager for a few days. If it keeps approaching the ceiling between restarts, tuning is not enough and it is time for a VDS plan with more RAM. A single core pinned at 100% indicates too much AI and vehicle load.

What settings differ between PvE, PvP and RP SCUM servers?

The type of a SCUM server is determined by how the damage, loot and time settings in ServerSettings.ini are combined; the same software can run a calm PvE world or a harsh PvP arena. Deciding the type up front helps you set player expectations and plan resources correctly.

• PvE servers: player-versus-player and base damage are disabled or limited; loot and puppet settings define survival difficulty. Memory use grows over time because more bases and vehicles accumulate per player.
• PvP servers: raid hours, base protection timers and death penalties matter most. Competition is high, so DDoS and cheat protection become critical.
• RP servers: economy prices, starter kits, naming rules and admin events matter. External bots and Discord integration are common.

Whatever type you choose, state the rules clearly in the server description and welcome message; SCUM players check those first in the server browser. Your wipe schedule also depends on type: PvP servers reset map and characters more often, while PvE and RP communities prefer long-lived worlds. Archiving a copy of SCUM.db before a wipe lets you roll back if disputes arise later.

How is a SCUM server protected against DDoS and cheaters?

There are two layers of protection for a SCUM server: network-level attack filtering and BattlEye anti-cheat in the game. Competitive PvP servers and large RP communities can be targeted by traffic attacks from rival groups, so both layers should stay on.

On the LIONFIN network, traffic is filtered at the network level by the RouteFence firewall; during DDoS attacks malicious packets are filtered out before they reach your server, and the infrastructure is monitored 24/7 by NOC and SOC teams (see our data center). This does not replace hardening inside your own server:

1. Open only the game and query ports; protect the remote desktop port with an IP restriction.
2. Use a strong Windows administrator password and create a separate user for remote desktop.
3. Do not disable BattlEye; -nobattleye belongs only on closed test servers.
4. Add only trusted Steam64 IDs to AdminUsers.ini.
5. Schedule Windows updates for low-population hours.

Because the servers are located in Türkiye, they suit communities with players in Türkiye and the surrounding region.

How do you back up and migrate a SCUM server?

A SCUM server’s game state lives in an SQLite database named SCUM.db in the save folder; regular backups mean copying this file together with the config folder. Player characters, bases, vehicles and bank accounts are all in that database, so a single corruption can wipe the whole community’s progress.

A safe backup routine:

1. Take backups while the server is stopped or during a scheduled restart; copying a live database can produce an inconsistent file.
2. Archive the SCUM/Saved/SaveFiles and SCUM/Saved/Config/WindowsServer folders together.
3. Keep date-stamped backups and store at least one copy off the server.
4. Always take a manual backup before major updates.

To move to another server, install the same game version with SteamCMD and copy these two folders to the new location. A VDS-level snapshot also gives you a quick rollback, but it does not replace a file-level backup.

What are the most common SCUM server errors?

The most common SCUM server problems are the server not appearing in the browser, version mismatches after an update and crashes caused by running out of memory. Most can be solved by reading the logs (the console opened by the -log parameter and SCUM/Saved/Logs).

• Server not visible in the browser: the query port (game port +2) is closed or falls within 27020–27050; in the meantime, connect directly by IP:port.
• Players get a “version mismatch”: the game was updated but the server was not. Stop the server and run app_update 3792580 validate in SteamCMD.
• Server will not start: the Visual C++ packages in _CommonRedist are missing or the OS is 32-bit.
• Lag and crashes that grow over time: memory is running out; lower vehicle and puppet limits, add a daily scheduled restart and add RAM if needed.
• BattlEye kicks: the player’s client is corrupted or the BattlEye service is outdated; ask the player to verify their game files.

If the problem persists, open a ticket from the Support section of the LIONFIN customer panel and attach the log file; if you need help ordering, contact us by email.