You have been playing Soulmask locally, or running your own server on a home PC, and now you want to move that world onto a LOW.MS dedicated box so your friends can join without you acting as host. Good news: the save is just a SQLite database and a small JSON config, and moving it across is a straightforward copy-paste job once you know which files to grab and where they go on the server.
This guide covers both ends of the trip: locating the save on your PC, and pushing it up to your LOW.MS server via the panel at control.low.ms.
Where Soulmask Saves Live on Your PC
If you have been playing the game locally (not hosting a server of your own), your world sits under your user's AppData folder. The quickest way to get there is Win+R, paste %LOCALAPPDATA%\WS\ and press Enter.
From there you should land in a folder keyed by your Steam ID, then 2646460\AutoGames\<Game Invite Code>\. The two files that matter are:
world.db- the actual world save (SQLite)GameXishu.json- your gameplay settings
If you were running your own Soulmask dedicated server on another machine, the layout is different. Look under the server install at WS\Saved\Worlds\Dedicated\Level01_Main\world.db and WS\Saved\GameplaySettings\GameXishu.json.
Copy both files somewhere safe on your desktop before you touch anything on the server side.
Before You Do Anything
Log into control.low.ms and open your Soulmask service. Two things to do in order:
- Stop the server. Hit Stop from the service page and wait until the status clears to Offline. Uploading a
world.dbwhile the server is running will either fail or corrupt what you push. - Take a Cloud Backup. Run a manual Cloud Backup of the existing server world. If the upload goes sideways - wrong file, wrong folder, mismatched version - you can roll back via Cloud Restore in one click and you have lost nothing.
Do not skip the backup. It takes a minute and it is the only safety net that matters here.
Uploading via File Manager
For two small files the File Manager in the panel is the fastest path.
- Open File Manager from your service sidebar.
- Browse to
WS/Saved/Worlds/Dedicated/Level01_Main/. If the folder chain does not exist yet, create the missing folders - the server generates them on first boot, so a brand-new service may not have them until you start it once. - Upload your
world.db, overwriting the existing file if prompted. - Back up one level to
WS/Saved/GameplaySettings/and upload yourGameXishu.json.
If the file you copied off a server was named GameXishu_2.json, rename it to GameXishu.json before uploading.
Uploading via SFTP
If your world.db is large, or you want to batch multiple files, use SFTP. Grab the hostname, username and password from the FTP/SFTP panel on your service page. The port is 8822.
Any client works - FileZilla, WinSCP, Cyberduck. Connect, navigate to the same paths above (WS/Saved/Worlds/Dedicated/Level01_Main/ for world.db, WS/Saved/GameplaySettings/ for GameXishu.json), and drop the files in. Use binary transfer mode; world.db is not a text file.
Pointing the Server at Your World
Soulmask dedicated servers load the world folder that matches their configured save name. By default that is Dedicated, which maps to Level01_Main - the path we used above. If your server has been customised with a different save name in Service Settings, check what it is set to and use that folder instead of Dedicated.
For most LOW.MS Soulmask servers the default save name is correct out of the box and you will not need to change anything.
Starting Up
Back on the service page in control.low.ms, start the server. Open the Web Console and watch the boot log - you should see the world load and player count initialise. First boot on a migrated save can take a little longer than normal while the server indexes the database.
Once the console settles and the status shows Online, connect in-game and verify your base, inventory and character are intact. If anything looks wrong, stop the server and use Cloud Restore to roll back to the backup you took earlier.
A Few Things to Know
- Version mismatches bite. The save must have been created on the same Soulmask version the server is running. If your local client auto-updated to a newer build than the server, run Steam Update on the service first.
- Character data is in
world.db. You do not need to copy anything else to bring your character across. The.jsononly holds gameplay settings (difficulty, rates, etc.) and is optional if you are happy with the server's existing settings. - Single-player to dedicated is one-way in practice. Your local save will keep working locally, but once people play on the server copy, that becomes the canonical world. Do not try to sync changes back later.
- Keep Cloud Backup on. Automatic backups run on a schedule and are separate from the manual one you took. Leave them enabled.