We welcome feedback about menus, toggles on menus, buttons on menus, input devices (like touch controls and keyboards), and Minecraft’s interface. How do you play? What would make it better?

← User Interface, Input Methods and Menu Options
16
Follow

"Border Blending" should be an option.

With 1.18, comes a brand new feature that almost seamlessly, as the name implies, *Blends* the terrain between previous updates and 1.18, that way you don't have drastic, unnatural-looking differences between chunks. Much like the "Biome Blending" option in the in-game menu, I think it would be cool if, when the game notices you first ever opening a previous update world in 1.18, it would ask you whether or not you want to activate Border Blending, and give you a slider to customize how well it blends.
Avatar
Registered User shared this idea

2 Comments

Please sign in to leave a comment.

Date Votes
Sorted by oldest
  • 0
    Registered User commented
    Comment actions Permalink

    But why would you not want border blending

  • 0
    Registered User commented
    Comment actions Permalink

    After updating to 1.18 i completely agree. The 1.18 blending option is really amazing from a technical perspective and I am impressed with the effort it took to do this, but the feature is half-baked and leaves a lot to be desired for the conversion of older worlds.

    We play on realms so that means a simulation distance of 4. We have entire strips of terrain that are 1 chunk or 2 chunks wide that are now blended 1.18 generation and look completely jacked up. im not very happy with the result.

    Unfortunately, the ship has already sailed so it may be too late for me and for 1.18 but for future releases, the world blending should "feather" by 1 or 2 chunks. If you open up a Minecraft world in an editor like Amulet you can see where the chunks are allocated. A simple feathering algorithm which would use 1.17 generation around existing chunks for 1 or 2 chunks before starting the new 1.18 blended chunk would've almost completely solved the challenge i am having converting my world from 1.17 to 1.18.

    Technically this should be a relatively simple thing to achieve. when a chunk is instantiated within the sim distance, minecraft should check for bordering original 1.17 chunks and decide whether it uses 1.17 gen or 1.18 gen. after it gets 2 chunks away from an original 1.17 chunk it would use 1.18 gen. relatively simple fix!