Problem Description: ASKA instance can be started. But whenever I restart the instance, the progress is lost and a new ‘save id’ is created
Tried it via Docker and non docker, both share the problem
Steps to reproduce:
Step 1 Launch the instance
Step 2 write down the save ID from ‘server properties.txt’
Step 3 restart the instance
Step 4 new save ID within ‘server properties.txt’
Step 5 verify in connected game → progression list
Actions taken to resolve so far:
tried to change the location of the ‘server properties.txt’ but I seem to be unable to do that
tried with docker, without docker, changed the line via shell, also via file explorer from Amp - nothing changes my problem
"Nah, after creating a save, right click on server properties.txt to import it into the AMP UI, then AMP will know the save ID and can launch it the next restart
Tried various ways:
Put the id into what you’ve described and also tried it directly via ssh and via file manager as well (into the server properties.txt file)
I suspect what your issue is that the save actually hasn’t been generated by the time you restart the server, so the server has nothing to load and therefore generates a new ID
Change the autosave interval to something shorter, so that the server can actually generate the save file, then if the Save ID is populated correctly in the UI, that save will be loaded on restarts
step 1) put into the config via GUI:
step 2) press import button on ‘server properties.txt’
step 3) check before restart: wrong ID in file
the imported ID seems to be wrong already? it doesn’t match my ID, but I can see the directory under server → savegame → savegame_a44df_280625111314 and various files.
So I guess the savegame (and other folders as well) are to be found in the file structure
second attemp on another server
step 1) put into the config via GUI:
step 2) press import button on ‘server properties.txt’ (0 success)
step 3) manual insertion of correct ID into file
step 4) start server
step 5) check server properties.txt → wrong Id
Edit: I have played 10h in one save … And 2 in another so there are small files but files in the save game folders
I don’t have a client to connect to the server, so the save is never generated for me. So a new id is created on restart the because the set save doesn’t exist. But if it did exist, it should be loaded fine
Is the save you are trying to load generated by this server, or did you add it from a different server?
If the latter, the issue could be file perms. Use AMP’s File Manager or SFTP to add the save.
The “server” directory in the datastore is actually a symlink to the server’s actual save location in the wine prefix (yes, ASKA is one of those dumb servers that saves to AppData)
I have just created a fresh instance, started it with “keep server world alive”, stopped it.
checked within the savegame folder for the naming, put it into the config, checked the “server properties.txt” file, compared it and it looked good.
Restarted a couple of times and it’s still in there.
Tried to do the same on my old instance where my 10h gamesession was, but to no avail.
Strange enough this is the ID I’ve put in the GUI:
a44df_270625182905
This is the ID after restart:
a44df_2706251829055
One digit too long it seems (and also doesn’t really work), but this longer version stays now even after updates. Why suddenly? I don’t know, but I cannot connect from my client currently and check if by some miracle that’s my old save game (no new savegame folder was being created though).
Well it’s really a pity that my save game is probably lost, but for the life of me I cannot get it to run (it was created on the same instance I am trying to use it). The only difference I am aware of is that in my old instance(s) there were multiple saves due to all the testing. maybe there is something wrong with that - I don’t know.
I guess we can call it a day as my new instance seems to be behaving fine (but the trust into the save capabilities of Aska is a bit low I have to admit)
