search

MCTCP / TerrainControl

Minecraft Terrain Generator for SpigotMC and Forge
https://www.spigotmc.org/threads/terraincontrol.37980/
MIT License
231 stars 161 forks source link

"Unable to find spawn biome" message without changing any config file. #344

Open luizrcs opened 9 years ago

luizrcs commented 9 years ago

Hello, I just installed TerrainControl v2.7.1 in my test-server and didn't change any of the config files that were generated. When I start my server, however, I get the "Unable to find spawn biome" message, then it keeps frozen for a few seconds and finally generates an ocean world. I'm using Spigot git-Spigot-6d16e64-b105298 (MC: 1.8.7) with API version 1.8.7-R0.1-SNAPSHOT. If anyone could help I would really appreciate. Thanks.

luizrcs commented 9 years ago

Anyone?

rutgerkok commented 9 years ago

Maybe just bad luck with the world seed? For me the seed 12 always spawns me on land (keep in mind you need to delete the level.dat file for a new seed to take effect.)

PG85 commented 8 years ago

I can't find the specific code anymore but I once saw in the Forge source code that MC tries randomly to find a spawn point in small number of chunks it loads when world generation starts. it looks for a grass block. If it cannot find a grass block in these chunks it says "unable to find spawn biome" and starts loading more chunks and looking for a suitable spot there. I remember this because it struck me as odd. For MCW this behaviour was causing problems so for the first chunk that is requested from the ChunkProvider when world generation starts I replace blocks with grass to fool MC into thinking the spawn location is valid. I later replace the grass blocks with their original blocks, also making sure that a solid block remains for ppl to spawn on.

So in any case, you can ignore the "unable to find spawn biome" message. The ocean world is a known bug that seems to happen only with certain world seeds.