Minecraft Forums

Well, I found and fixed the latest iteration of the spawn chunks problem. The problem arose from biome IDs in the CC configs which didn't match ones in the biome mod configs. The biome mod configs have to take priority, but I didn't correct them early enough in generation. The problem didn't come up in my testing because I don't alter default configs much (I have too much to test and don't really have time for that.) So the chunk walls should go away with the next CC version. I have some other changes to make, but at this point I think it's all routine - no more multiday debugging sessions.

Also, EB is working better, although still not perfectly. Pink has bested me on rivers in rugged terrain:

I have some biome terrain redesign to do, it seems. Hmph.

(Oh, and - procedural generation, folks! Every last block.)

Showing off:

Did somebody mention waterfalls?

Or wide sandy beaches?

(that last pic is with some biome-patching code I'm working on now - not in current snapshots)

Procedural generation, every single block.

Quote from MohawkyMagoo»

I have some questions about how CC and RTG interact, just to clarify things, so I'm sure that im understanding how it all works properly.

CC controls the continent sizes, ocean sizes, the biome climate groupings etc? RTG does not?

RTG controls river generation?

RTG controls the World type - Realistic ?

CC controls biome selection of which biomes will appear in that world? Or is that RTG?

But, all biome selection through CC is dependent on the biome configs in the individual mod configs such as Highlands. EBXL and BOP?

CC controls beaches and river width? or is that RTG?

The interactions *are* complicated.
(All this assumes you're using CC layout, of course)
Oceans, continents, and climate zones are 100% CC.

RTG controls river generation. CC can make a "river biome" but it doesn't become a river in RTG. That will stop in the next CC version (it will suppress all the CC river-biomes-that-don't-make-rivers if in an RTG world).

The user picks the world type. If Realistic, RTG makes the terrain. In any non-Realistic world, RTG does nothing.

Biome selection is supposed to be by CC (but see below). RTG has been doing biome selection in the RTG layout, and some of those choices are still affecting vanilla and CC worlds. That's being fixed.

CC's biome selection *is* limited by the biome mods. CC can't put in a biome that doesn't exist, and it tries to respect settings in the biome mods.

Rivers are all RTG. Beaches are - cooperative. Roughly, CC asks for a beach of a certain size at a certain place and RTG does one as best as it can, but RTG has to smooth out the terrain and that moves the beach and generally makes it smaller.

This is all complicated by the fact that before 0.5, RTG *was* doing biome selection, layout, etc., and that's still available as a config. We are very seriously considering separating that biome layout system into a separate mod to make exactly these questions less confusing. Call that mod "Biome Regions".

The concept we're shooting for is that you select the biomes you have and the layout they're in with other mods - the biome mods, CC, or "Biome Regions". RTG will then generate that world with realistic-style terrain if you pick the world type "Realistic". If you don't pick a "realistic" world that same layout will come out with vanilla terrain.

Oh these mountains:

This is from a mixed Highlands/BoP setup, pretty much the defaults. The mountain itself is Highlands Alps. The pic is from a Highlands Pinelands. The mountain is so high you can't see it properly from normal ground. Fortunately there was a Highlands Highlands biome (yeah I know) right next to it:

That ain't WorldPainted, folks. That's random procedural generation, every single block.

The Highlands outlook also overlooks a BoP forest - Seasonal, I think. That's a darn good view itself, if not as jawdropping as the mountain. You can see how far up I am.

The Witchery crash (and several other bugs involving the same line 50, which is a check line) should be fixed with the next version. We are currently restricting the RTG generation to the Overworld but the RTG generation was being served to other dimensions. It will be restricted to the Overworld with that patch. I probably shouldn't have released that intentional crash but I figured if RTG was tried in another dimension there would be a crash anyway and this would make it clear what was going on (and it did.)

Down the line we hope to make it available in other dimensions, but there's lots of work before that's possible.

I'm playing around with the Highlands biome definitions and I am really astounded at what can be gotten out of the RTG system. A few samples:

A copse of Rainforest next to Rock Mountains viewed from a Meadow.

A view over a lake to Woodlands next to Rainforest

Cliffs with a Valley between them overlooking a bog (is that King Kong I hear in the distance?)

Seriously, wow. The most amazing part is - you know all the complaints about biome X always looking the same everywhere? Well, they don't have to. You can make Plains be high in some parts of the world and low elsewhere; be flat as a pancake some places and gently rolling elsewhere. You can have Taiga have towering mountains in some places and just hills elsewhere. Birch Forest Hills could be towering in some places and low and smooth elsewhere. Pretty boggling. These things will bring some performance hits, but not all that much as I see it.

In principle dimensional mod biomes can be placed in the Overworld but in many cases they don't work because of how they're programmed. CC has the "Overworld Wyvern Dimension" mod and that probably works as well as any mod can; it gets placed but somehow the mod clears the biome list from time to time and causes a crash. CC could also put Twilight Forest biomes in the overworld but many of their features will only work if they're in the TF dimension.