Multiverse
Add option for /mvimport to not regenerate world folder if it is missing
This one might need a bit of explanation:
I use a plugin called MirrorWorld. On server startup, it deletes the contents of one of my world folders and copies the contents of another into it. When the world folder that gets deleted by MirrorWorld is in the worlds.yml file at startup, Multiverse 2 attempts to regenerate the world as a normal environment right after MirrorWorld deletes it, which is when it is copying the other world folder over. MirrorWorld contains no world generators, so I cannot tell Multiverse 2 to let MirrorWorld handle that, so they both attempt to alter the world folder. This causes bad things to happen.
Could there be a feature added that tells Multiverse 2 to not regenerate the world folder if it happens to be missing? i.e. while MirrorWorld is doing its thing at startup, Multiverse will pretend it's alright with the fact that MirrorWorld has the control in that situation despite not being a world generator and will keep the world loaded regardless of the fact that it does not actually contain world files.
You could always try editting the plugin.yml within the multiverse jar file and add "MirrorWorld" to the soft depends list.
This will make Multiverse load after MirrorWorld. If this is already the case then I'm not sure on what the best route to take would be.
This was mostly meant to be a feature request, but I'll give that a shot and see how it does. I have a feeling it won't do much, because MirrorWorld doesn't normally finish its world operations until after all the other plugins have finished loading.
EDIT: Gave it a shot, did not work.
