Cities not always generating
Areolata7 opened this issue ยท 2 comments
Using 1.16.3 with forge 34.1.42 and LostCities - 1.16-4.0.5-alpha
Trying to create a world with a single biome (BOP Alps or Tundra or other treeless frozen biome) and very rare cities with no generated trees. I copied the "rare" city profile but altered:
"avoidGeneratedTrees": true"
"cityChance": 0.0005"
And tweaked floor numbers and explosions
Basically I want a tougher world where you have to find a city and must try to get saplings via breaking the few available leaves in the rubble.
A couple of times I generated maps there was a city generated but in the others I have traveled 10,000 blocks in at least one direction and never found one. I also resorted to using creative to fly around and never found a city. I see no "locatebiome" or similar command I can use to confirm a city generated anywhere in the world. This would save me a lot of time wandering around looking for something that isn't there. Is there any such command I can use when I first start the world to confirm that lost cities is actually working? Only commands I see are "debug", "map" (doesn't seem to do anything), and "saveprofile".
Please advise
That cityChance is pretty low. It's to be expected that they are rare. There is no way to locate cities however. You have to find them
Thank you for the reply. When I leave it at the default "rare" setting there are way too many cities. I typically find 3 or 4 within viewing distance of spawn. They are often lumped together in groups like that so you may have a long distance between them and then find another group of several cities together. I want single cities spaced far apart but not so far that you spend 1 hr in creative flight or 12 survival days and never find one. I like the idea of having to survive a night or two before finding a city but not longer than that. So what do you suggest for a rare chance that would avoid multiple city clumps?
.