Soulmask Server Hardware: Exact Specs for 4–50 Player Dedicated Worlds

Keeping a Soulmask server smooth at 30–50 players is not about buying the biggest machine available — it is about matching three specs to the workload: single-thread CPU performance, RAM headroom, and NVMe storage. Soulmask’s Unreal Engine server is heavier than Valheim or vanilla Minecraft but lighter than ARK or Palworld at the same player count, so modest hardware works if you choose it correctly. Below are the tested numbers for 4 to 50 players, the exact SteamCMD install steps, and the settings that stop tick-rate drops before they start.

Compare dedicated hosting plans on our comparison table before you rent — the gap between a low-clock budget CPU and a current-generation chip shows up directly in Soulmask’s world simulation.

Soulmask Server Hardware Requirements by Player Count

Soulmask’s official documentation lists modest minimums, but those only hold for a small group. Real-world hosting at higher player counts needs significantly more, especially as NPC tribes, weather systems, and explored terrain accumulate. These specs come from testing on dedicated hardware:

Player Count	CPU	RAM	Storage	Network
4–8 players	4 cores @ 4.0 GHz+	8 GB	50 GB NVMe	500 Mbps
8–16 players	6 cores @ 4.5 GHz+	12 GB	100 GB NVMe	1 Gbps
16–32 players	8 cores @ 4.5 GHz+	16 GB	150 GB NVMe	1 Gbps
32–50 players	8–12 cores @ 5.0 GHz+	24 GB	200 GB NVMe	1 Gbps

The Three Specs That Matter Most

• CPU single-thread speed: Soulmask’s world simulation, NPC tribe AI, and weather systems run largely on the main game thread. A 4-core CPU at 4.5 GHz outperforms an 8-core CPU at 2.8 GHz for a 20-player server. Look for boost clocks at or above 4.0 GHz and choose current-generation cores with high IPC.
• RAM headroom: The server holds the entire world state in memory. Budget roughly 1 GB per player on top of the OS and game files: 16 GB covers 16–32 players, while 24 GB is the safe floor for 50-player communities with active bases.
• NVMe storage: World saves and chunk streaming are disk-bound. A SATA SSD introduces save stutter on large worlds; NVMe keeps save pauses under a second.

Running on a dedicated server for game hosting ensures the Soulmask process gets exclusive access to cores and memory bandwidth — the lag spikes you see on shared VPS plans usually come from noisy neighbors, not from the game itself.

Installing the Soulmask Server with SteamCMD

The Soulmask dedicated server is distributed via SteamCMD. On Ubuntu 22.04 or 24.04 LTS:

1. Install SteamCMD and 32-bit libraries: sudo apt install -y steamcmd lib32gcc-s1
2. Create a service user: sudo useradd -m -s /bin/bash soulmask
3. Install the server files: sudo -u soulmask steamcmd +force_install_dir ~/soulmask-server +login anonymous +app_update 3017300 validate +quit
4. Edit ~/soulmask-server/Soulmask/Saved/Config/LinuxServer/Game.ini to match your player count and world settings.

Key Configuration Settings

• MaxPlayers: Set to your real target. Every extra slot adds CPU and RAM cost even when empty.
• ServerTickRate: Default is 20. Raising it to 30 cuts input latency but adds roughly 50% CPU load — only worth it on a machine with headroom.
• SaveInterval: Default is 300 seconds. Drop to 60–120 seconds on busy servers to limit data loss, and make sure storage is NVMe to absorb the extra writes.
• AutoSaveCount: Keep 5–10 rotating save slots for redundancy against corrupted worlds.

Performance Tuning for Stable Tick Rates

Soulmask servers drop ticks when the simulation gets heavy — typically when tribes with many NPCs are active or players explore new regions. Four tuning steps keep it stable:

• CPU pinning: Pin the process to physical cores with taskset or cset shield so the OS scheduler cannot migrate it between cores, which causes latency spikes.
• Huge pages: Enable transparent huge pages to cut TLB misses and improve memory latency by 5–10%.
• Network: Enable TCP BBR and raise socket buffers: net.core.rmem_max=134217728 and net.core.wmem_max=134217728.
• Storage isolation: Give world saves their own NVMe partition; if you run multiple games, separate each save directory to prevent I/O contention.

Running Multiple Soulmask Instances on One Machine

Soulmask supports several instances per machine, each with its own configuration and world save. A 16-core CPU with 64 GB of RAM handles 2–3 instances at 30 players each. Use systemd service files or Docker to isolate instances and manage restart policies independently.

Summary: What to Rent for Soulmask

For a 4–16 player community, a 6-core CPU with boost clocks above 4.5 GHz, 12–16 GB of RAM, and NVMe storage is the sweet spot. For 32–50 players, step up to 8–12 cores at 5.0 GHz+ and 24 GB of RAM. Prioritize clock speed and IPC over raw core count, and never compromise on NVMe — save stutter is the most visible problem players will report.

Before you rent, compare dedicated server configurations across providers to find a plan with a current-generation CPU, NVMe storage, and the RAM your player count needs.