I kept getting this error on startup, after creating and configuring an instance on my local machine, and moving it over to the container. Took me a bit to reason out what was going on.
The issue was that the world name of the save I had setup was not the same as the name of the save folder, since it was a world I had initially setup in singleplayer and moved to the server. The game pasted a timestamp into the world name, including an invalid : character, which got stripped out of the folder name. I.E. the world name was "Red Ship v2 2024-08-04 11:12" while the folder name was "Red Ship v2 2024-08-04 11:12". Since the container startup script attempts to fix the save file path, by searching for an extracting a world name, it was configuring the save path to be "Red Ship v2 2024-08-04 11:12", which the game then couldn't find. After manually changing the world name and folder name, everything loaded up great.
Not sure if this is worth a fix, to account for invalid characters in the path name, within the startup script, but I figured it's at least worth posting the issue and the solution, should anyone else encounter it.
I kept getting this error on startup, after creating and configuring an instance on my local machine, and moving it over to the container. Took me a bit to reason out what was going on.
The issue was that the world name of the save I had setup was not the same as the name of the save folder, since it was a world I had initially setup in singleplayer and moved to the server. The game pasted a timestamp into the world name, including an invalid
:character, which got stripped out of the folder name. I.E. the world name was"Red Ship v2 2024-08-04 11:12"while the folder name was"Red Ship v2 2024-08-04 11:12". Since the container startup script attempts to fix the save file path, by searching for an extracting a world name, it was configuring the save path to be"Red Ship v2 2024-08-04 11:12", which the game then couldn't find. After manually changing the world name and folder name, everything loaded up great.Not sure if this is worth a fix, to account for invalid characters in the path name, within the startup script, but I figured it's at least worth posting the issue and the solution, should anyone else encounter it.