Weird worldgen Direwolf20 1.6

  • Please make sure you are posting in the correct place. Server ads go here and modpack bugs go here
  • The FTB Forum is now read-only, and is here as an archive. To participate in our community discussions, please join our Discord! https://ftb.team/discord

Saberwulfy

New Member
Jul 29, 2019
105
0
0
My world in Dirwolf20 1.6 have some elevation problems and sliced biomes, ive flyed for 2 hours and never found a mystcraft temple, minecraft village.
Is it the usual or a isolated case?
 
Have you updated or changed the BoP configs (assuming you are using BoP generation). Changing Biomes o Plenty configs usually has the sliced biomes effect. as for mystcraft stuff, the 'temples' or libraries only occur within mystcraft ages as far as I know. And the villagers are random but I have had them in most of the villages I have run across. Probably just luck of the draw for that.
 
  • Like
Reactions: Tristam Izumi
I never change any configs, ive flyed 178 Km and never found a village, i think my world gen have some problems.
My generatorName is default, seed -2301488416465593898.
 
Last edited:
Sometimes villages are hard to find.

Make sure you had generate structures enabled when you made the world, and the BoP config has villages enabled in some of the biomes you have enabled.

Once you have villagers you can breed the types you want if they didn't turn up on world gen.
 
Ive found, the minimap dont rendered but ive used the "Minutor" for review and found, i am posting my png map for u look the worldgen problem.
Oculatio.png
 
Which worldgen did you use to create the world?
 
She said her generatorName was default.
Ahh right, missed that. Odd then. Maybe some mods were added/changed that adds new biomes which messed up the biomes list somehow?

As long as its default world gen and no config changes were made to BoP, it shouldn't be using BoP at all. Should it?

There have been several warnings about things like this happening when updating any of the packs still in beta, but usually it involves BoP, Highlands and ATG etc. Don't really understand why it would cause problems in a default vanilla world.
 
Ahh right, missed that. Odd then. Maybe some mods were added/changed that adds new biomes which messed up the biomes list somehow?

As long as its default world gen and no config changes were made to BoP, it shouldn't be using BoP at all. Should it?

There have been several warnings about things like this happening when updating any of the packs still in beta, but usually it involves BoP, Highlands and ATG etc. Don't really understand why it would cause problems in a default vanilla world.
It honestly could be just a download error. My advice would be to redownload the pack and try with the same seed. If it's still like that, I don't know what.