Terrain Control

Terrain Control

235k Downloads

BO2 placement - Rarity:1 is still too much

Opened this issue · 9 comments

commented

Hi everyone,

After about two weeks of experimentation, I am now going to create my first map with TerrainControl, in a more serious and precise way. I am heavily modifying the default biomes: I am at the stage of adding custom Objects (made those with BetterBOB). Suppose I have a ruin, and I want to place them in a plain. My setting in WorldConfig.ini is objectSpawnRatio:1 and in the Ruins Object I gave it a Rarity of 1. Still. it's too much. I'd like it to be a lot rarer.

How can I obtain it?

Thanks in advace.

commented

In the BO3s Rarity can now be very small: 0.000001 if you want.

I haven't found a solution to your other problem. 😦

commented

Two ways:
Wait next version, in dev now.

Add small isle biomes for that object

commented

Thank you very much for your quick reply! Using isles is clever! I'll do that until next version.
Anyway I'd like to understand the current capabilities:

objectSpawnRatio tunes the number of attempts per chunk, while individual rarity inside objects represents the chance of spawning it for every attempt. So setting those to 1 and 1 should mean a 1% chance for every attempt, and just 1 attempt per chunk. So I should see about 1 object every 100 chunks. I'm trying to imagine it in my plains: about only one object for a 10x10 chunks grid, It means just one object every ~160x160 blocks. Pretty rare! Why does it seem to me that their presence is far higher then that? Not even close! I frequently can see three or even four of those in a single viewport. That's surely not 1 in ~160x160 blocks.

Another question: some instances of my custom objects are sometime being spawned partially or with missing blocks. I am tweaking the most obvious variables (fillUnderObject, Dig, Collision%) but nothing seems to have a clear effect. I tried collision% from 0 to 100. Some object always spawn broken. What is causing it?

commented

This problem is really bothering me a lot. I spent the last three days changing individual values in BO2s and googling and reading guides. But I still don't have the slightest idea of what is causing it! Some BO2s (both mine or from MassiCraft pack) spawn completely broken. What's worst is that they seem to cause some kind of trouble, in fact when I walk over the "missing blocks" i get stuck there, as if something actually was there but invisible (the behaviour is not of a regular block though, my walking over it kinda stutters there). I will post screenshots if necessary. But please, if someone knows what's the problem, I really need help with this.

Thanks in advance.

commented

Oh, that bug. Sometimes the server forgets to tell the client about some of the blocks in the BO2. Log out and log back in.

commented

I can't believe this is just a bug and that it's unfixable. Just sitting there untouched. In a world with lots of BO2s this is going to be a nightmare for the players!

And it happens very often! I am creating a world biome by biome, so I am doing something like: generating - logging in - flying over the world looking at things - logging out - make changes - repeat. And you know what? I can't remember a single time in which there weren't broken BO2s.

commented

I never said that it's unfixable, but it seems to be a hard one to fix. But:

It only affects newly generated terrain. It usually happens when the server has to generate a lot of terrain at once. If you have a survival server players cannot walk that fast. And if you have a creative server, you can pregenerate terrain with a plugin like WorldBorder, which is a good idea anyways.

commented

I really hope it gets fixed. TerrainControl is an AMAZING piece of software. Really. It has astonishing capabilities. I am loving it! But this bug is a dire one. Mainly because it can have a direct negative impact on player's gameplay.

Also. I need to thank you for your support! ;)

I am trying WorldGenerationControl, a Bukkit Plugin. It's a little slow to generate everything but, once done it could fix this. I'll let you know!

commented

This is minecraft or bukkit bug :(
Occurs sometimes when chunk massively changed when populate.