Jump to content

World Generation Tinkering


Recommended Posts

This is my first topic and first time here so yeah .-.

But... this is about me editing how world generation works in the Rocketry upgrade. My results are pretty weird, but you may enjoy! Also, if you make a play through, if you would like to send it, send it!

Okay, let's start with the world gens.

- (Rocketry Upgrade) Using Helicona.yaml -

----------------------------------------------------------

Spoiler

Test 1 - Deleting the frozen part

I deleted the Frozen zone from the Zone Files part. This resulted in well, no frozen biome. the result is a bit weird but cool.


worldsize: # This will be used soon!
  X: 384
  Y: 384
ZoneFiles:
  - name: subworlds/Space
  - name: subworlds/StartWorld
  # where the Frozen subworld should be.
  - name: subworlds/Default
  - name: subworlds/Surface
    weight: 0.3
  - name: subworlds/Bottom

Result:

image.thumb.png.964a117eb7880090533ee22d6c8afec1.pngThe starting biome is all over, and even took over the surface!

Download yaml
Test.yaml

Spoiler

Test 2 (The yaml file is named Test1...) - Deleting the Bottom


worldsize: # This will be used soon!
  X: 384
  Y: 384
ZoneFiles:
  - name: subworlds/Space
  - name: subworlds/StartWorld
  # where the Frozen subworld should be.
  - name: subworlds/Default
  - name: subworlds/Surface
    weight: 0.3
  # also where the bottom subworld can be.


image.thumb.png.701660444a55bdd554815ff53fa7d9ea.png

As you expected.. the bottom is gone, with water and tiles being surrounded with neutronium. (Sorry for the sandstone highlight!)

Download yaml
Test1.yaml

Spoiler

Test 3 - Deleting the surface...

Now moving on to the surface. If you haven't noticed, the surface seems to have a 'weight' part. This may control how big it is, but this isn't about that. CONTINUE TEST!


worldsize:
  X: 384
  Y: 384
ZoneFiles:
  - name: subworlds/Space
  - name: subworlds/StartWorld
  - name: subworlds/Default

image.thumb.png.0a4cba53bfecf401bda2be2de8f9c139.png

The gravitas is gone, and the surface has seem to take shapes of half-hexagons. This may be due to biome sizes.
Download yaml
Test2.yaml

Spoiler

Test 4 - Deleting space itself



worldsize:
  X: 384
  Y: 384
ZoneFiles:
  - name: subworlds/StartWorld
  - name: subworlds/Default
  
  # All that exists is now just a starting world, (printing pod) and a default biome. The duplicants must be really confused.

image.thumb.png.91c4bdb0d22e93b561f846f5aa2a3f08.png'

It may not be very visible, but space no longer exists. The half-hexagon top is also gone, being replaced with a flat sandstone top. All that exist is just the starting biome. Boo hoo.
 

Download yaml

Test3.yaml

Spoiler

Test 5 - Deleting the default biome - Final



worldsize:
  X: 384
  Y: 384
ZoneFiles:
  - name: subworlds/StartWorld
  
  # All that exists is now just a starting world, (printing pod), and a broken biome barrier.

image.thumb.png.5c6c24eeb82d48b0c190c3c5a152972b.png

There seems to be a broken biome barrier explaining the immense flood of abyssalite. All that remains is what I just explained and a weird starting biome. Deleting the last Zone is not possible, as it creates  an error in generating, and causes a crash.

 

Feel free to test more and touch other parameters (appropriately),even without mod tools (and just Notepad++) one can do a lot to the world generation. Personally I of course like it simple to keep it playable, more POIs, no Neutronium anywhere (neither world borders nor in the magma biome) and perhaps a bigger world once my PC can handle it without issue. I can't help but wonder if deleting space prevents meteors yet still allows space travel~

Archived

This topic is now archived and is closed to further replies.

Please be aware that the content of this thread may be outdated and no longer applicable.

×
  • Create New...