rutgerkok
commented
9 years ago What I found interesting is that a desert turned into a snow biome. This means that the server recognizes the biome (otherwise it would be listed as the ocean biome, and wouldn't have snow). Are you running multiple TerrainControl-enabled worlds on the server? If yes, are there biomes with overlapping ids?
Assuming the answer is yes on the previous two questions: two biomes on the server can't share the same id but have different properties, even if they are in different worlds. If this is the case, your best option is probably to make sure that two biomes with the same id are actually quite similar.
If, on the other hand, you're running only one TerrainControl world on a server, then I have no idea what is happening. Maybe you can find some workarounds to get the Forge version of TerrainControl working on Cauldron? You mentioned that it makes certain plugins that control generation impossible since Multi-Verse can't talk mods. I also encountered an issue where I cannot force generate another world name within Cauldron itself., but maybe that can be worked around, for example if you use TerrainControl for your main world.
However, I have little confidence that I can solve this error. Have you got TerrainControl to work on Cauldron previously? If you look through the bug tracker, you can see that I haven't been able to solve most Cauldron-related issues. Cauldron uses a ton of hacks to get both Bukkit plugins and Forge mods working, and TerrainControl uses a ton of hacks to get around the limited Bukkit API, and the two don't work well together.
Dockter
Hello,
I have been using TerrainControl for some time under the bukkit server, however about 6 months ago we migrated to Cauldron. We are running Cauldron for 1.7.10 forge build 1448 (we have our own repo).
We noticed on the worlds we migrated from our bukkit server that when users TODAY go to areas on the map that were not previously generated the server generates chunks that don't match up. After a very long search into this issue it appears that when TerrainControl loads its biome data in that it isn't actually making it into the Cauldron server.
When we try to create a new world using Multi-Verse, /mv create newWorld normal -g TerrainControl the world is created, the populators on the chunks run as I would expect them to except its missing all of the custom biomes.
Our servers log files looks like this when it is generated:
http://pastie.org/pastes/10373415/text?key=z90lq0if1t5bj6gtuldrqw
I have asked several developers within the Sponge community, Blood, Zidane, Gabizou etc their thoughts on the issue. Blood's thought was to generate the world using the forge version TC which I tried AND does work however it makes certain plugins that control generation impossible since Multi-Verse can't talk mods. I also encountered an issue where I cannot force generate another world name within Cauldron itself.
Zidane's thought to solve the issue was to generate the entire map using the Forge version, move the world into the appropriate subfolder under world in Cauldron then allow Multi-Verse to import it. Whereas that may work the world I am generating is based off of a map.png file. Generated completely it is around 70gb in size not counting Dynmap's images.
With either suggestion it was discovered that once generated if we moved the worlds back to having the Bukkit version of TC control the worlds after generation that the biomes would suddenly disappear. Area's that were previously generated as deserts would suddenly have snow in them.
My question is are you aware of an issue where TerrainControl appears to load the biome data at the server but it never makes it into the generator itself?
Our server has been online since 2011. Our developer repos are located at https://www.github.com/AlmuraDev/ I am willing to make a donation to your cause if you could assist us in solving this issue. I realize that this is supporting a previous version but I thought I would start with you folks first.