Multiverse/Multiverse-Core — Issue #370: Empty world folders in server root when using world-container bukkit setting.
Author: credomane
Created: 2012-01-03 18:33:59+00:00
State: open

I've been debating on if this is a bukkit issue or multiverse-core issue. So I thought I'd bring it up and see if someone knew for certain. Functionality wise everything works. This just creates an annoyance for me because it is defeating the purpose of using the world-container option in the first place. :)

I have it set in my bukkit.yml to store all worlds inside the folder named "worlds".

All of the world are stored and work properly from inside that folder. However, I've noticed that whenever mv tells bukkit to load shall I say a non-standard world an empty folder gets created in the server directory.

Lets say I have these 5 worlds. server.properties says the level name is "cobblebox".
So that makes the standard worlds cobblebox, cobblebox_nether and cobblebox_the_end.
I then have these two non-standard worlds that mv loads. cb_old and cb_ancient.

Every time the server starts or I issue a reload cb_old and cb_ancient folders are created in the root directory of minecraft with absolutely nothing inside of them. The same happens if I import, create, remove or delete a new world. Yep, deleting a world will completely remove everything from ./worlds/ but an empty folder will be created as ./.

I'm tempted to blame this all on bukkit. :P