Multiverse/Multiverse-Core — Issue #409: Autoload settings sometimes don't work properly
Author: Huns
Created: 2012-01-17 00:04:08+00:00
State: open

These commands work, and using them results in their values in worlds.yml being changed:

/mvm set memory false world_nether
/mvm set memory false world_the_end

These commands work (do not produce errors), but their values in worlds.yml don't get changed:

/mvm set autoload false world_nether
/mvm set autoload false world_the_end

If I set autoload to false for world, world_nether, and world_the_end in the config file, the only one that doesn't get loaded is world_nether. I would think that explicitly setting the flag to false would stop any of them from getting loaded until someone actually uses them.

The reason this is important is that some people have enough custom levels that loading up the spawn areas for all of them will cause their server to run out of RAM. (The "memory false" thing doesn't apply until AFTER the spawn has been loaded, so when the server starts, and before MV has been able to prune the unused spawn areas, it will run out of RAM and crash.)