Soulmask version 1.0 launched on April 10, 2026, delivering a dedicated server overhaul that adds a second map, new game modes, and a granular configuration system. For the first time, hosting your own world is approachable for ordinary administrators—provided they master the backup discipline that the game’s new complexity demands.
The update is a turning point for the survival genre: server quality now directly determines whether a community thrives or fragments. This guide walks you through what changed, what it means for your setup, and the concrete steps to keep your world intact.
A Server Stack Rebuilt for Version 1.0
Soulmask’s 1.0 server is no longer a simple binary toggle between PvE and PvP. You now get multiple game modes—including the combat-focused Warrior Mode—and a second map, Shifting Sands, that can be linked to the original Cloud Mist Forest. That means your dedicated server can become a platform for varied playstyles rather than a one-size-fits-all lobby.
The other headline change is the configuration depth. Instead of superficial tweaks, you can adjust XP progression separately for awareness, character, mask, gathering, crafting, and combat. You set decay rates, invasion pressure, tribe limits, and resource drain. In practice, two servers running the same map can feel like entirely different games.
The Hardware Reality: What Your Machine Actually Needs
Soulmask’s server isn’t exotic, but it isn’t light either. The server process alone gobbles about 12GB of RAM, so 16GB is the practical floor—and even that leaves thin headroom for Windows services and disk caching. A 64-bit, quad-core processor is strongly recommended, especially if you expect more than a handful of concurrent players.
Disk space is another trap. The base install needs 30GB free; add the second map and room for saves, backups, and logs, and you’ll want significantly more. On the networking side, the server must have its gameplay port, query port (27015 UDP is critical for browser visibility), and admin ports open and forwarded. A direct-connect fallback is a wise safety net.
Installation: The Step Most Admins Botch
Soulmask uses SteamCMD, familiar to anyone who has hosted Rust or ARK. The Windows app ID is 3017310 (Linux: 3017300). Create a dedicated folder, extract SteamCMD, build an update script, and fetch the files. Then—and this is the crucial part—start the server once to generate the configuration files before you touch anything.
Many important files, including the all-important GameXishu.json, don’t exist until that first launch. Stop the server cleanly, then begin tuning. If you skip this, you’ll waste hours debugging a setup that was never broken. Test the base install before layering on customizations.
Launch Parameters That Set the Contract
Your launch line defines the server’s identity: name, max players, passwords, game mode, and save/backup intervals. The -initbackup flag is underused but invaluable—it creates a clean backup before the world loads, giving you a restore point if the new session corrupts.
Equally important is how you shut down. Closing the server window directly is a fast-track to data loss. Always use Ctrl+C, telnet on the admin port, or the in-game GM panel. Save integrity trumps convenience every time.
Tuning Your World with GameXishu.json
The real customization lives in GameXishu.json, which appears only after the server runs once. This file controls progression, resource yields, survival pressure, combat balance, decay, invasions, and cluster behavior. The granular XP multipliers, for instance, let you boost early-game troubleshooting (awareness and gathering) without trivializing endgame combat.
Follow a disciplined approach: identify a pain point, change one category, observe player behavior, and keep a dated copy of every config version. Random tweaking leads to unbalanced worlds; versioned configs let you roll back painlessly.
Clustering: Running Two Maps as One Persistent World
Soulmask 1.0’s cross-map clustering is a standout feature. Connecting Cloud Mist Forest and Shifting Sands lets players move between them while retaining character progression. But cluster hosting isn’t just “run two copies”—it requires unique ports, matching passwords, consistent game modes, and enabled cross-server flags on both ends.
Crucially, character data (levels, masks, skills) transfers, but structures and local inventories do not. Before converting an existing world into a cluster, back up your world.db. Without it, a misconfiguration can destroy months of community progress.
Backup Discipline: The Only Thing Standing Between You and a Ruined World
world.db is your everything. Back it up before major config edits, before every game update, and before cluster conversion. The automatic backup interval helps, but it’s reactive; a manual copy made right before a change is your real insurance.
Good backup habits are inseparable from clean shutdowns. An abrupt termination can corrupt the save just as an auto-backup fires. Treat your server like a service: save often, close gracefully, and keep at least one offline backup copy.
What to Do Now
- Set up your hardware with at least 16GB RAM, a quad-core CPU, and 40GB+ free disk space.
- Use SteamCMD to download the server files (Windows ID 3017310, Linux ID 3017300).
- Start the server once to generate config files, then stop it cleanly.
- Configure your launch line with server name, ports, passwords, and
-initbackup. - Edit GameXishu.json incrementally, focusing on one tuning category at a time.
- Set up a backup regimen that includes manual copies before any change.
- If clustering, back up world.db and ensure cross-server settings match.
- Adopt graceful shutdowns (Ctrl+C, telnet, or GM panel) as a non-negotiable habit.
Outlook: Keeping Your Server Alive Beyond Day One
The long-term health of your server depends on patch stability, documentation improvements, and how well the community shares hard-won knowledge. Watch for developer updates that might alter config file structures or cluster behavior, and always test patches on a backup before deploying to your live world. Hosting provider panels are maturing, but understanding the raw JSON still matters.
Soulmask 1.0 gives you the tools to build a world worth returning to. The rest is up to you—and your backup folder.