Some semi-random thoughts on terrain generation

[xoft]

Waaaah! The new noise is no different in speed from the old noise. Whaaaa?!

[xoft]

Ahh, stupid me, I changed the Noise3D generator, but tested the BiomalNoise3D.
Now that I've changed the BiomalNoise3D generator as well, I'm happy to report that the chunk generator speed was doubled.

[NiLSPACE]

Something might went wrong with the Ocean biome, because this is all ocean:

[xoft]

Yeah, the heights are off, perhaps because the new noise has a slightly different shape. We'll have to redo all the biomes. That's why I wanted to switch to the new noise before finishing the parameters for the biomal noise.

[xoft]

The good thing is, the generator speed has improved. I had 6 - 7 chunks per second with CubicNoise, now I have 16 - 17 chunks per second with the InterpolNoise. I think there is still a large improvement possible regarding the tree generator, but I'll leave that for later. Now I'm trying to finish the biome parameters so that the shape generator is worth the change.

[xoft]

Hah, this just generated for me, I think our terrain generator's getting better and better

[xoft]

The new generators are up for review:
https://github.com/mc-server/MCServer/pull/1604

[NiLSPACE]

This is the first time I've seen a floating spawner:

[NiLSPACE]

So I started doing the spawners in MineShafts and Dungeons, but how are we planning on doing the Nether fortresses? Have the Spawner pre-programmed in the prefab, or should the cNetherFortGen class handle it somehow?

[xoft]

I guess we should make it possible to export the spawner(s) (and chests, and other block entities) in the prefab itself. What should the format be? I'm thinking something along the lines of a single string:

"<x>\t<y>\t<z>\t<BlockEntityType>\t<BlockEntityContentsJSON>\n" \
"<x>\t<y>\t<z>\t<BlockEntityType>\t<BlockEntityContentsJSON>\n" \
"<x>\t<y>\t<z>\t<BlockEntityType>\t<BlockEntityContentsJSON>\n" \

This way we can store multiple block entities for each prefab, store whatever is needed for the block entity contents, and if needed, extend the format by using another tab at the end (supposing that the JSON won't have a tab in it, which we can enforce).