Back Server setup guides
Soulmask server hosting14 min

Soulmask Dedicated Server Setup and Shifting Sands DLC Two-Map Cluster Configuration

Deploy a Soulmask dedicated server: SteamCMD 3017310, UDP 7777/27015 forwarding, key GameXishu.json parameters, Shifting Sands desert DLC cross-map clusters, and open-source LGSM management.

The Soulmask Dedicated Server supports autonomous tribes while players are offline and large multiplayer tribal wars. Since version 1.0 and the introduction of the ancient Egyptian desert DLC Shifting Sands, the game supports multi-instance cross-map Clusters. Tribe members can carry masks and technology between the main continent and the desert world through sea portals. This article covers server installation, key settings, and cluster setup standards.


1. Hardware and system resource assessment

Specification Single-map group server (4~8 players) Two-map cluster (main continent + desert DLC)
CPU 8 cores / 3.2GHz+ High-clock-speed processor with 12~16 cores
Memory (RAM) 16 GB physical RAM At least 32 GB physical RAM (each map instance uses 10~14GB independently)
Storage 50 GB NVMe SSD 120 GB NVMe SSD
Upload bandwidth 15 Mbps dedicated 30 Mbps ~ 50 Mbps dedicated

2. Install the dedicated server with SteamCMD

The dedicated server AppID is 3017310:

Shell
steamcmd +login anonymous +app_update 3017310 validate +quit

After the download, the Windows server executable is located at: WS/Binaries/Win64/WSServer-Win64-Shipping.exe


3. Network port planning

Each map instance needs a separate set of communication ports:

Port name Instance 1 (main continent forest) Instance 2 (Shifting Sands DLC) Protocol Port forwarding required?
Game communication (GamePort) 7777 7877 UDP Required
Queries (QueryPort) 27015 27016 UDP Required
Remote RCON administration 25575 25576 TCP Open as needed

4. Startup scripts and two-map Shifting Sands DLC cluster

1. Main continent script (start_main.bat)

Batch
@echo off
start WSServer-Win64-Shipping.exe Level01_Main -server -log -UTF8Output -Port=7777 -QueryPort=27015 -MaxPlayers=20 -ServerName="LanGame Tribe Main" -Password="pwd" -AdminPsw="adminpwd" -ClusterID="SoulmaskCluster1" -ClusterDir="C:\SoulmaskCluster"

2. Shifting Sands DLC script (start_desert.bat)

Batch
@echo off
start WSServer-Win64-Shipping.exe DLC_Level01_Main -server -log -UTF8Output -Port=7877 -QueryPort=27016 -MaxPlayers=20 -ServerName="LanGame Tribe Desert" -Password="pwd" -AdminPsw="adminpwd" -ClusterID="SoulmaskCluster1" -ClusterDir="C:\SoulmaskCluster"

Key arguments:

  • Map identifiers: Level01_Main for the main continent; DLC_Level01_Main for the desert DLC.
  • Cluster arguments: Both instances must have exactly the same -ClusterID and point to the same local shared directory with -ClusterDir for lossless player data transfer through sea portals.

5. Key GameXishu.json multipliers and sandbox settings

On first startup, the server creates game coefficient configuration at: WS/Saved/Config/WindowsServer/GameXishu.json

Key tuning settings:

JSON
{
  "PlayerExpRate": 1.5,
  "TribeMemberMaxNum": 30,
  "BaseMaxNum": 5,
  "DeathDropType": 1,
  "HarvestYieldRate": 1.5,
  "TameSpeedRate": 2.0
}
  • TribeMemberMaxNum: Maximum recruited tribe members; balance according to server memory.
  • DeathDropType: 0 drops everything, 1 drops backpack supplies only, 2 drops nothing.
  • HarvestYieldRate: Harvest yield multiplier.
  • TameSpeedRate: Speed multiplier for tribesman taming and consciousness transfer.

6. Choose an approach: manual configuration or LanGame Server Manager (LGSM)

Manual Soulmask cluster maintenance involves two sets of startup arguments, 4 separate listening ports, and complex JSON rules.

We recommend the official open-source dedicated server management platform to automate routine administration:

LGSM features:

  1. One-click multi-map cluster orchestration: Starts the main continent and desert DLC in parallel, assigns non-conflicting ports, and connects cross-map data directories automatically.
  2. GameXishu.json forms: Converts deeply nested coefficients into clearly grouped visual panels with real-time validation and saving.
  3. Tribal data snapshots: Creates lossless snapshots of all cluster characters and buildings before sieges or major version updates.
  4. Server watchdog: Monitors both processes in real time and restores a single map without data loss after an unexpected crash.