Worldgenerator resets after each server restart (Multiverse)
NoArmsNoCookies opened this issue ยท 11 comments
Hi,
i created a new world using Multiverse and TerrainControl. Problem is: Whenever the server is restarted the worldgenerator seems to be reset to default, causing terrain glitches.
The only thing that helps is to manually unload and reload the world after each server restart (which means at least every morning x_X).
The logs seems to be ok, and Multiverse says it's loading TerrainControl.
I already asked the guys from Multiverse but they couldn't find any hint to what is going on.
I have the same problem. I set TerrainControll as default terrain generator in bukkit.yml.
This problem occurs in combination with Wormhole X-treme, and depends on the number of concurrently loaded plugins.
Issue here: http://dev.bukkit.org/server-mods/wormhole_x-treme/tickets/76-wxt-and-multiverse-custom-world-gen-issue/
I created the world with the following command:
/mv create world_131 NORMAL -s NoArmsNoCookies -g TerrainControl -t NORMAL -a true
Serverlog:
http://pastebin.com/tL68ttYq
This happens after a manual /unload and /load
http://pastebin.com/dpccjXGq
My worlds.yml (from Multiverse)
http://pastebin.com/QVtevKLe
What Multiverse version you use ?
Also, first server log happen after server restart with added TC world, right ?
In other words - server will generate wrong terrain after that log ?
Ah how this glitches looks ?
I'm using MV2 2.4-b527 with TerrainControl 2.2.4
Yeah, the first server log is after a normal restart and the server generates new chunks with a different generator, or perhaps a different seed or TerrainControl settings.
The glitches are simply sharp biome edges at new areas.
Using //regen (worldedit) on a correctly generated area after a server restart changes the terrain to something different (e.g. a river where should be a forstest). When performing //regen on the same area after unload und load the area is restored correctly.
Hmm did you know about your MV`s build ?
This is builded in April O.o
Try MV dev builds please ..
Looks like mv or bukkit did not end world init .. string "TerrainControl: world initialized with seed is 1111041366" must be always after world loaded.
Updated to latest devbuild Multiverse-Core 2.5-b591, but didn't change anything.
I will try a completly different world-management tool.