Jump to content

kunchboy

Vintarian
  • Posts

    8
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

kunchboy's Achievements

Wolf Bait

Wolf Bait (1/9)

3

Reputation

1

Community Answers

  1. Hi, I just used commands to change the worldgen settings from in-game. Make sure to backup your world before upgrading or messing with commands, especially worldgen commands. The command I used was /worldconfig landcover 0.7 After you use the command you'll have to save and rejoin, and then any new chunks you explore will generate with the new setting from the command. I used the wiki page on world config here to help. There's lots you can mess with, but it might get glitchy, so remember to make backups if you muck with it :)
  2. To anyone who comes across this and is wondering the same thing, I did some experimenting. I went onto my main world generated pre-1.21 and changed the landcover to 0.7 (previously 1). Ocean cover was set to 1, I didn't change that. Loading new chunks after changing gave mild terrain weirdness but no jagged chunk cutoffs like 1.20 if changing the landcover. So you are able to have oceans in previous worlds if you load new chunks after changing the settings with commands, and the chunks won't have odd cutoffs EDIT While exploring more, I DID come across some large chunk errors where the terrain will just cut off and not smoothly merge with old terrain. However, the above still stands. Most terrain seems to smooth and seems to do so more than 1.20. Personally, I'm just going to make it part of my worlds lore. Strange things happen when you mess with timelines and time anyway. It almost makes sense to canon, lol.
  3. Yeah I'm wondering about if I explore new chunks with my current settings if it'll generate patches of ocean. Or if I change my world settings with commands, and explore new chunks, if there will be glitched terrain where the old chunks meet the new ones. (The patch notes mentioned chunk smoothing?) I'll probably end up just experimenting with backup worlds when it releases and report back for anyone else that might be wondering.
  4. I started my world with default exploration settings for landcover etc. so don't get any oceans. When 1.21 releases and I update, will that remain the same? I have previously made a copy of my world and manually entered commands to change the worldgen so oceans generate further out, but it causes generation errors where the old and new terrain generates. Does the chunk smoothing in 1.21 fix that? I would like oceans in my game but don't want the glitchy terrain. Thanks
  5. Thanks for the solution & just popping in to say this bug is still happening. I really hope my goats didn't despawn :')
  6. Awesome, thanks guys
  7. Looks like I'll have to go mining. Honestly not sure how I've made it to the beginning of the iron age considering I haven't even got a designated forge When you say quarrying, do you mean just mining out stone in any desired pattern? Like strip mining or tunnelling?
  8. Talking about the little stone chunks, not the full blocks. Right now the fastest way for me is to travel to a desert and just collect all the boulders and loose stones, but it takes a long time (still faster than mining for me, somehow), and I end up getting so little cobblestone and path blocks out of it. Am I doing this wrong? Is mining the way to go here even though it's initially slower with stone collection than picking up from the ground? I really want to build and am enjoying the game a lot so far but collecting materials for so little blocks is going to burn me out, I can tell. Trying to take it slow but it's beginning to bore me a lot, and I don't want that! I've just made my first iron pickaxe, so I'm solidly in the bronze age and the very beginnings of iron age. Haven't set up any windmill automation yet though because I keep getting distracted lol.
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.