Moving a Path of Titans community server from a home PC or another host to LOW.MS does not have to mean starting from scratch. If you have been running a PoT community server yourself, all your tuned config, registered players, and every dinosaur your community has raised are sitting in a handful of folders on your current machine. Copy those folders across to your LOW.MS server in the right places and everything comes back online exactly as it was — same rules, same characters, same progression. This guide walks through where those files live on a PoT server, how to get them onto your new LOW.MS box using the File Manager or SFTP, and the small handful of settings you need to re-check once the upload is done.
Where Path of Titans Saves Live on Your Server
On any PoT community server — Windows or Linux — everything that matters sits under a single folder: PathOfTitans/Saved/. Inside that folder there are two areas you care about.
The first is Config/. On a Linux server this is PathOfTitans/Saved/Config/LinuxServer/, on Windows it is PathOfTitans/Saved/Config/WindowsServer/. That folder holds Game.ini (rules, rates, home cave limits, quest settings), GameUserSettings.ini (server name, password, mod list, slot count), and Engine.ini. These are plain text files and they carry every tweak you have made since you first started the server.
The second is DatabaseCache/. This is where the local database stores player data. Accounts sit under DatabaseCache/Account/ as JSON files named by Alderon ID (for example 123456789.json), and each dinosaur character is saved as a separate JSON file under DatabaseCache/Character/. If you zip up DatabaseCache/ you have a complete backup of every player and every dinosaur on the server.
If your old host was using the Alderon remote database instead of a local one, your player data is not in DatabaseCache/ — it is held by Alderon, keyed to your server token. In that case you only need to carry across your config files.
Before You Do Anything
Stop the old server before you copy anything. PoT writes to the database files while the server is live, and a copy taken mid-write can come across with half-finished character data. Shut the old server down, wait a few seconds, then start the copy.
On the LOW.MS side, provision your Path of Titans service at control.low.ms and let the first install finish. That gives you a clean PathOfTitans/Saved/ layout to drop your files into, and it confirms the server boots on a stock config before you overwrite anything. Once it is running cleanly, stop the service from the panel — do not upload files to a running server.
One last thing worth doing: take a Cloud Backup of the freshly installed server from Service Settings before you change anything. If the upload goes sideways, Cloud Restore puts you back to a known-good state in a couple of minutes.
Uploading via File Manager
For most people, the panel's File Manager is the fastest way. Open your service at control.low.ms, click File Manager, and browse to PathOfTitans/Saved/.
Upload your Config/LinuxServer/ folder (or WindowsServer/ if that is what you had — both work) and replace the versions already there. Then upload your DatabaseCache/ folder the same way. File Manager will ask before overwriting existing files; say yes.
The File Manager handles zip files natively, so if you compressed Saved.zip on your old box you can upload the single archive and extract it on the server. That is usually quicker than dragging thousands of individual character JSONs across a browser upload.
Uploading via SFTP
For larger worlds — anything with more than a few hundred characters in the database — SFTP is the saner choice. LOW.MS exposes SFTP on port 8822. Open your service page, grab the SFTP credentials from Service Settings, and connect with FileZilla, WinSCP, or the sftp CLI:
sftp -P 8822 your-username@your-server-hostname
Once connected, navigate to PathOfTitans/Saved/ and upload your Config/ and DatabaseCache/ folders into place. SFTP handles interrupted transfers cleanly — if the connection drops halfway through a 40,000-file DatabaseCache/ upload, you can resume without starting over.
Pointing the Server at Your Config
With the files in place, open PathOfTitans/Saved/Config/LinuxServer/GameUserSettings.ini in the File Manager's editor and sanity-check a few lines. The server name, password, and max player count should match what you expect. If you had a mod list on the old box, the mod IDs under [/Script/PathOfTitans.GameUserSettings] should be there too — PoT pulls mods from mod.io at startup, so the IDs are what matters, not any files.
Your authentication token does not live in the config files. It is passed to the server as a command-line argument or via the AG_AUTH_TOKEN environment variable, and LOW.MS stores it as a server variable you can set from Service Settings. Re-enter the token you generated at alderongames.com/oauth/hosting-token. You can reuse the same token — one token per hosting account is fine.
Starting Up
Start the server from the panel and watch the Web Console for the first minute. You want to see PoT load your map, mount the database, and report a successful auth handshake with Alderon. Once "Server is ready" appears, join the server with your own client and check that your character is there, your quests are in the state you left them, and any mods you had configured are loaded.
If something looks off — missing characters, wrong map, server listed as "unauthorised" — stop the server, Cloud Restore to the clean snapshot you took, and double-check the folder paths on your upload.
A Few Things to Know
Path of Titans pulls mods from mod.io at boot, so as long as the mod IDs in GameUserSettings.ini are correct, your LOW.MS server will download them on the first start — you do not need to upload the mod files yourself. Expect the first boot to take a little longer than usual while they come down.
Your Alderon auth token is tied to your hosting account, not to a specific machine, so the token from your old server is valid on LOW.MS. You just need to re-enter it once in Service Settings because the panel does not know about your old install.
Finally, map selection is driven by GameUserSettings.ini too — the SelectedMap entry decides whether you boot Panjura, Gondwa, or a modded map. If you were running a community map, make sure its mod ID is in the mod list as well, otherwise the server will fall back to default and your existing characters may be pinned to a map that is not loaded.
Take a fresh Cloud Backup from Service Settings once the server has been live for an hour or so — that becomes your new baseline.