-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
Minor
-
None
-
Affects Version/s: None
-
None
-
Environment:
Running on Linux, I don't have access to other platforms to test
-
This server is running CraftBukkit version git-Spigot-a19903d-e1ebdd9 (MC: 1.16.4) (Implementing API version 1.16.4-R0.1-SNAPSHOT)
-
Yes
On the server I run I have several different worlds of which only one is loaded at a time, I store all the worlds in a "worlds" subdirectory of the minecraft server folder to keep things organized and use a script to stop the server, update the level-name line in server.properties, and start the server again.
I'm investigating migrating to Spigot from the vanilla server but I ran into this problem: when Spigot migrates the world to separate folders the migrator and the server use different locations: the migrator uses worlds/NAME_nether and the server then attempts to load worlds/worlds/NAME_nether. I imagine that the migrator is correct and the server should be fixed but idk.
Steps to reproduce (assumes knowledge of UNIX/linux command line):
- Download a fresh server.jar from Mojang
- Build a new spigot.jar from BuildTools.jar
- Accept the EULA: `echo "eula=true" > eula.txt`
- Start the server: `java -jar server.jar nogui`
- Go into creative and go into the Nether and place some blocks
- Go back into the overworld and stop the server
- Run `mkdir worlds && mv world worlds/`
- Edit server.properties to set level-name=worlds/world
- Run `java -jar spigot.jar nogui` to migrate the world
- Log back into the server and go back to the nether
- It's not the same nether! The game has generated a new nether
- (I assume the same applies to the End, but I didn't check)
After inspecting the tree structure of the worlds/ folder, I found that the original nether dimension was migrated to worlds/world_nether while the game created a new nether dimension in worlds/worlds/world_nether.