Soulmask Server Hosting

What is a Soulmask dedicated server, and why do you need a separate one?

The Soulmask dedicated server is the software released for CampFire Studio's survival game Soulmask that runs the world independently of players. In the game you manage not only your own character but also the AI members you recruit into your tribe; they work, fight and craft, and are simulated continuously on the server. That's why Soulmask uses more resources than many survival games with the same player count.

When you host on your own PC, the same machine carries both the game's graphics and this simulation, and the world stops when you leave. A separate dedicated server keeps the world online 24/7, lets friends progress at different times and keeps your tribe's production chains running without interruption.

The server software is a separate tool on Steam and can be downloaded with SteamCMD using an anonymous login. Community guides use separate app IDs for Windows and Linux; make sure you pick the right one before installing.

How much RAM does a Soulmask server need?

Memory is the most critical item when planning a Soulmask server; community guides recommend at least 16 GB per server and mention 24–32 GB for busy servers. The author of one guide documenting the Linux install observed the server using over 12 GB of memory during startup alone. The table above is an estimate based on these observations; actual use varies with the world's age, the number of tribe members and the size of bases.

• Tribe members: the AI members each player manages are simulated server-side; load grows as tribes grow, even if player count doesn't.
• Bases and structures: large bases, many crafting stations and storage increase memory use and save time.
• Explored area: the more players spread across the map, the more area is kept active at once.
• OS overhead: Windows Server uses more memory than Linux.

In Soulmask a memory shortage usually shows up as a startup that stops halfway, a server missing from the list, or a crash. On Linux, swap space can prevent crashes on sudden memory spikes as a stopgap, but swap writes to disk and slows the game server, so it isn't a real fix. If budget is tight, invest in memory before CPU; on the CPU side, dedicated high-clock cores reduce stutter during heavy combat.

Should you choose a ready-made package or a VDS for Soulmask?

This page shows VDS packages for Soulmask: you can install the server yourself or request a ready-made setup through a support ticket. Soulmask's high memory needs make it one of the games most likely to struggle on shared resources; on a VDS memory and cores are reserved for you, so the server runs predictably regardless of neighbouring loads.

On a VDS you have two OS options. Linux uses less memory for the OS and needs no licence, a real advantage given how much memory Soulmask wants. Windows Server is more familiar for those who prefer a graphical interface; connect over Remote Desktop and edit the launch file.

For a detailed comparison see game server package or VDS. When choosing from the live package table, look at memory first. NVMe storage, KVM virtualisation and network-level DDoS filtering are standard on every LIONFIN VDS, and you can add resources as your tribe grows.

Which parameters do you start a Soulmask server with?

A Soulmask server's core settings are passed as launch parameters; StartServer.bat on Windows and StartServer.sh on Linux contain them. Parameters commonly used in community guides:

A sample Linux launch line might look like this:

./StartServer.sh -SteamServerName="MyServer" -MaxPlayers=20 -PSW="join" -adminpsw="admin" -pve -Port=8777 -QueryPort=27015 -EchoPort=18888

One Linux guide notes that -MaxPlayers is capped at 50. Restart the server after changing parameters.

How do you choose PvE or PvP on a Soulmask server?

The -pve parameter in the launch line decides the mode: with it the server opens in PvE, without it in PvP. This choice fundamentally changes your server's character, so it is the first thing to settle with your community.

PvE servers suit groups of friends and communities who want co-op. Players can't harm each other; the focus is building a tribe, developing production chains and fighting the game's AI enemies. Rules are simpler and admins need to step in less.

PvP servers are for players who want tribe rivalry, raids and territory control. Admin workload rises: you need written rules on raid times, alliance limits and base placement. Competitive servers are also targeted by denial-of-service attacks more often, so network-level protection and regular backups become critical.

Switching later technically only changes the parameter, but think about how players will react: moving to PvP puts bases built for PvE at risk, so announce it in advance and give players time to prepare. Some communities offer both by running two instances on one VDS with different ports; given Soulmask's memory needs that only makes sense on a server with plenty of memory, as each instance needs the values in the table on its own.

How do you secure the EchoPort and admin access?

The port set with -EchoPort opens a telnet-based console for managing the server locally; players don't need it and it must not be exposed. Community guides recommend keeping this console reachable only from the server itself; Linux guides send save and shutdown commands through this port when stopping the service.

• Close the EchoPort: don't allow outside access to it in the firewall. Telnet is unencrypted, and exposing it to the internet risks control of the server.
• Strong admin password: pick a long, unique -adminpsw that differs from the join password -PSW.
• RCON: community guides also mention an optional RCON port; if you use it, open it only to your own IP.
• Where passwords live: passwords sit in plain text in the launch file; restrict access to the server folder.

Using SSH keys instead of passwords and limiting password attempts with Fail2ban narrows the admin surface further.

How is a Soulmask server protected against DDoS attacks?

A public Soulmask server is exposed to denial-of-service attacks because its IP appears in the Steam server list, and the risk rises noticeably on competitive PvP servers. On LIONFIN infrastructure traffic is filtered at network level by the RouteFence firewall, DDoS traffic is filtered before it reaches your server where possible, 600 Gbit/s of total upstream capacity leaves headroom for traffic spikes, and everything is monitored 24/7 by our NOC and SOC (see our data center).

• Expose only the game port (8777/UDP) and the query port (27015/UDP); keep the rest closed.
• On Linux define the firewall rules with UFW.
• Run the server as a separate non-root user; guides note this also prevents permission problems.
• Apply OS security updates regularly.

During an attack players disconnect en masse or the server drops off the list. Note the time and symptoms and open a support ticket from the customer panel.

How do you run a Soulmask server as a service on Linux?

The Linux build of the Soulmask server runs most reliably as a systemd service, so it starts automatically after a reboot and restarts after a crash. Community guides covering the Linux install recommend installing the server under a separate user and putting the launch line in the service file's ExecStart field.

1. Create a separate user such as soulmask and install the server into its home directory with SteamCMD.
2. Run the server as that user with the User= line in the service file.
3. Put the launch script and parameters in ExecStart, and enable restart after crashes with Restart=on-failure.
4. To save the world cleanly on shutdown, stop the server through the admin console as described in the guides.
5. Follow the logs with journalctl.

Soulmask startup is memory-intensive and can take a while; after a service restart it may take a few minutes before the server appears in the list. Don't keep restarting the service in the meantime, as each restart begins the startup again. Following progress in the log is the most reliable way to tell whether the server is really stuck.

How do you back up and update a Soulmask server?

World and player data on a Soulmask server live under the WS/Saved folder of the server install, so that folder is the focus of backups. Because the world save contains tribe members, bases and player progress together, a single corrupt save can affect weeks of your community's work.

1. Shut the server down cleanly, saving through the admin console.
2. Compress the WS/Saved folder into a dated archive and copy it off the server.
3. Run app_update in SteamCMD with the correct app ID (3017300 for Linux, 3017310 for Windows).
4. Start the server, connect and check that bases and tribe members are in place.

Players' Steam clients update automatically, so keeping the server current prevents connection problems; always take a manual backup before big content updates. On Linux you can automate the backup steps with a script and a cron job.

Can you move a world from single-player or a friend’s server?

Moving a Soulmask world between servers relies on copying the save folder; however, we could not confirm an official, developer-documented way to transfer a single-player save to a dedicated server. If you plan to do it, try it on a test server first.

Moving from one dedicated server to another is more predictable:

• Shut the old server down cleanly and archive the entire WS/Saved folder.
• Install the same game version on the new server; if the operating systems differ (Windows to Linux, for example), remember that config folder names change.
• Extract the archive to the same location on the new server and keep the launch parameters identical.
• Start the server and check the world; if something is off, investigate before shutting down the old server.

Use SFTP on Linux or Remote Desktop drive sharing on Windows. For large saves, a direct server-to-server transfer is much faster than routing through your own PC. Don't delete the old server until the move is complete. Plan the move for a quiet hour and announce it; since the IP will change, share the new address and server name clearly so players can find it again.

How do you improve performance on a Soulmask server?

The first condition for Soulmask performance is enough memory; once memory is sufficient, most stutter comes from heavy AI and large bases. Watch memory use for a few days: if it sits near the limit, no setting can replace missing memory and upgrading is the right step.

• Keep the player limit realistic: set -MaxPlayers to what your server can handle; every player brings their tribe along.
• Tribe and base rules: limiting oversized tribes and many small bases scattered across the map through community rules reduces simulation load.
• Scheduled restarts: memory use can climb on long-running Unreal Engine servers; a daily restart is standard on many servers.
• Dedicated resources: load swings on shared environments turn into noticeable stutter on heavy servers like Soulmask.

htop and free give a quick picture of server load. After a change, watch its effect for a few days and don't change several settings at once, so you know which one actually helped and avoid unnecessary upgrades.

What are the most common Soulmask server problems?

Most Soulmask server problems come from insufficient memory, the wrong app ID or port settings; the server logs usually show the cause.

• The server won't start or stops halfway: not enough memory. Community observations suggest startup problems on servers with less than 16 GB.
• Files don't run on Linux: they were downloaded with the Windows app ID. Use 3017300 for Linux.
• Not visible in the server list: query port 27015/UDP is closed, or the server hasn't finished starting. Startup can take a few minutes.
• Players can't connect: game port 8777/UDP is closed.
• The server opens as PvP: the -pve parameter is missing from the launch line.
• Permission errors: the server was run as different users; give ownership of the files to a single server user.
• Version mismatch: players' clients updated but the server didn't.

If you get stuck, open a support ticket from the customer panel with the logs attached.