You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Servers always create new worlds in the current directory according to the running jar. In MSM's case this is the server directory. The problem is we really want worlds to be in the worldstorage directory. We cannot change the behaviour of the server, but we can fool it.
Before starting a server MSM creates symbolic links in the server directory pointing to worlds in the worldstorage directory. If the world that the server is going to use exists in world storage, the link is made in the server directory, the server sees that link as the world and all is fine. If the world does not yet exist, there is no link and so the new world folder gets created in the wrong place.
The solution: By inspecting the server.properties file we can glean the name of the world a server is expecting to use, and before it starts create an empty folder in world storage with the same name. The link will then get created, and the server will still create the world files—in the correct place—via the dynamic link.
The text was updated successfully, but these errors were encountered:
So if i understand this correctly the default world "world" should end up automatically in the wordstorage directory on server-creation?
Because if that's the case there is a bug, since it is NOT doing that for me....
Servers always create new worlds in the current directory according to the running jar. In MSM's case this is the server directory. The problem is we really want worlds to be in the
worldstorage
directory. We cannot change the behaviour of the server, but we can fool it.Before starting a server MSM creates symbolic links in the server directory pointing to worlds in the
worldstorage
directory. If the world that the server is going to use exists in world storage, the link is made in the server directory, the server sees that link as the world and all is fine. If the world does not yet exist, there is no link and so the new world folder gets created in the wrong place.The solution: By inspecting the
server.properties
file we can glean the name of the world a server is expecting to use, and before it starts create an empty folder in world storage with the same name. The link will then get created, and the server will still create the world files—in the correct place—via the dynamic link.The text was updated successfully, but these errors were encountered: