over 2 years
ago -
Irongate Smiffe
-
Direct link
Hi!
Sorry sorry sorry for messing things up.
What happens is the dedicated server tries to load your world default from worlds_local folder, instead of the old worlds folder. Which ends up not finding your old world of course. So it creates a new world.db and world.fwl file and stores those in worlds_local.
This is just files you can remove from worlds_local after verifying your old world.db and world.fwl file is still in your worlds folder.
What you can do to make the dedicated server work again is either to manually move world.db and world.fwl from worlds to worlds_local folder. then start your dedicated server again.
OR
Go to worlds folder and see so your world.db and world.fwl file is still there.
Then to worlds_local, delete the newly created world.
Then join the public-beta-test and this should fix itself.
Both client and server needs to be in public-beta-test for this to work since the client versions needs to match.
Sorry sorry sorry for messing things up.
What happens is the dedicated server tries to load your world default from worlds_local folder, instead of the old worlds folder. Which ends up not finding your old world of course. So it creates a new world.db and world.fwl file and stores those in worlds_local.
This is just files you can remove from worlds_local after verifying your old world.db and world.fwl file is still in your worlds folder.
What you can do to make the dedicated server work again is either to manually move world.db and world.fwl from worlds to worlds_local folder. then start your dedicated server again.
OR
Go to worlds folder and see so your world.db and world.fwl file is still there.
Then to worlds_local, delete the newly created world.
Then join the public-beta-test and this should fix itself.
Both client and server needs to be in public-beta-test for this to work since the client versions needs to match.