Aska Save Location & How to Upload Your World

Moving an Aska world from your PC to a LOW.MS dedicated server is straightforward once you know where the save folders are kept and how the server picks which world to load. This guide walks you through finding your local save, getting it onto the server, and making sure the server actually uses it.

Where Aska Saves Live on Your PC

Aska is a Unity game from Sand Sailor Studio, so your saves sit in the usual LocalLow folder:

%USERPROFILE%\AppData\LocalLow\Sand Sailor Studio\Aska\data

You can paste that straight into the File Explorer address bar, or press Win + R and run %userprofile%\AppData\LocalLow\Sand Sailor Studio\Aska\data.

Inside data you will see one or more folders named like savegame_ac8e3_220425234054. The first chunk after savegame_ is the Save ID, and the trailing digits are the creation timestamp. If you have several saves and are not sure which is which, open the meta file inside a save folder with a text editor. It contains the world name and basic info.

Take the entire savegame_... folder for the world you want to move and right-click it, then choose Compress to > ZIP file. Keeping it as a single zip makes the upload quicker and avoids half-transferred files.

Before You Do Anything

Two quick bits of housekeeping before you touch the server:

1. In control.low.ms, stop the Aska server from the service page. Uploading saves while the server is running can corrupt data.
2. Take a Cloud Backup of the current server state. If something goes wrong you can roll back with Cloud Restore instead of starting from scratch.

With the server stopped and a backup in hand, you can upload safely.

Uploading via File Manager

For most players the built-in File Manager is the fastest path:

1. Open your Aska service in control.low.ms and open File Manager.
2. Navigate into the server save directory. On LOW.MS Windows nodes this typically sits under a folder named similar to AppData_LocalLow_Sand Sailor Studio_Aska_data_server_.
3. Use the Upload button to send your zipped save folder up.
4. Right-click the uploaded zip and choose Extract so the savegame_... folder sits alongside any existing saves.
5. Delete the zip once extraction is done to keep things tidy.

Uploading via SFTP

If the save is large, or you prefer a dedicated client like FileZilla or WinSCP, use SFTP:

• Host: the IP shown on your service page
• Port: 8822
• Username / password: your panel credentials (or a separate SFTP user if you have set one up)

Connect, browse to the same AppData_LocalLow_Sand Sailor Studio_Aska_data_server_ directory, and drag the unzipped savegame_... folder across. SFTP can resume interrupted transfers, which is useful for bigger worlds.

Pointing the Server at Your World

Aska stores the active world's Save ID in server_properties.txt. That ID must match the part of your folder name between savegame_ and the timestamp. For a folder called savegame_ac8e3_220425234054, the Save ID is ac8e3.

1. In File Manager, open server_properties.txt in the server root.
2. Find the Save ID line and set it to the ID from your uploaded folder.
3. Save the file.

The IDs in the folder name, the meta file inside the save, and server_properties.txt should all match. If Aska cannot find a matching save on startup, it will usually generate a fresh world instead, which is the most common cause of a "my save didn't load" report.

Starting Up

Back on your service page in control.low.ms:

1. Start the server.
2. Open Web Console and watch the log.
3. You should see Aska load the uploaded save rather than generate a new one. The world name and seed in the log should match what you expect.

Join the server from your Aska client to confirm your buildings, villagers and progress are intact.

A Few Things to Know

• Aska updates occasionally change save formats. If you have just run a Steam Update on the server, make sure your local client is on the same version before uploading a save from it.
• Keep your zipped local save around for a few days as a manual backup in addition to Cloud Backup.
• If the server keeps generating a fresh world on every start, double-check the Save ID in server_properties.txt and that the savegame_... folder is in the correct server data directory rather than a nested subfolder.
• Some hosts mention a pp_savefile_id.txt override file used by Aska to force a specific save. LOW.MS does not require you to create this by hand; editing server_properties.txt is enough in normal setups.

If anything looks off after the upload, use Cloud Restore to roll back to the backup you took at the start, then try again.