Skip to content

Instantly share code, notes, and snippets.

@OrionH
Forked from Querz/tips-tricks-1.16.md
Last active June 21, 2022 01:43
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save OrionH/54b0d900a77e95d32f132a1c248f6a9c to your computer and use it in GitHub Desktop.
Save OrionH/54b0d900a77e95d32f132a1c248f6a9c to your computer and use it in GitHub Desktop.
Tips and Tricks regarding Minecraft 1.16

Tips and Tricks regarding Minecraft 1.16


WARNING: The following instructions are deleting parts for your Minecraft world. Make sure to create a full backup before proceeding with any of those steps!


If you need help or have questions, feel free to join the new Discord server!

chat


Deleting chunks based on a selection

Usually, the Nether does not contain too many builds. Most of the time it's a Nether highway or some Nether mob farm. Knowing where those farms are located might help with the process, but MCA Selector should give a relatively clear overview of the Nether.

A selection can be made by left-clicking either chunks (when zoomed in) or entire regions (when zoomed out). Holding and dragging works too.

Making a selection in MCA Selector

Deleting the selected chunks

To delete the selected chunks, use Selection --> Delete selected chunks. Opening the world in Minecraft and travelling to those chunks will regenerate them using Minecraft's current terrain generation.

MCA Selector's deletion warning

Keeping the selected chunks

To keep the selected chunks and delete everything else, use Selection --> Export selected chunks. This will ask you to specify a folder where the selected chunks should be exported to. The selected folder must be empty. When the export is complete, delete the MCA files of your world from the region folder and move the files from the export to your region folder. The region folder for the Nether is located in world-name/DIM-1/.

MCA Selector's export warning

Deleting chunks based on a filter

Automatically filtering chunks is particularly useful for very large worlds, especially when you are running a server with lots of players.

A filter can be used to select, delete or export chunks based on a few conditions, for example the time players have spent in specific chunks or the blocks a chunk contains.

Opening the filter tool

Open a world and navigate to Tools --> Filter chunks. This will show an example query that will select all chunks from x/z -1600 to x/z 1600. Below the filter is a text field, where a textual representation of the query is shown that can also be used in headless mode. To use a textual query, insert it into the text field and press Enter. If the query is valid, it will parse and show it in the query editor above.

Examples: Query all chunks where players have spent more than 5 minutes in total:

InhabitedTime > "5min"

Filter tool with query InhabitedTime = 5min

Query all chunks where players have spent more than 5 minutes in total, contain a chest block and where chunk-x is smaller 3000:

InhabitedTime > "5min" AND Palette contains "chest" AND xPos < 3000

Filter tool with query InhabitedTime = 5min AND Palette contains chest AND xPos < 3000

Note xPos and zPos are chunk coordinates, not block coordinates. To convert block coordinates to chunk coordinates, divide them by 16.

The Filter window also has a few options at the bottom to either first create a selection as if using right-click to select the chunks on the map, to delete the chunks that test positive for your query directly or to export those chunks to a new empty folder.

Partially deleting chunks

A chunk is made of 28 vertically stacked sub-chunks, called Sections. As of 1.18, sections are indexed from -4 (lowest) to 19 (highest). Sections are 16 blocks vertical. Sections -4 to -1 go from blocks -64 to -1 on the Y axis and sections 0 to 19 go from blocks 0 to 319. The range for 1.16 is 0 to 15 going from block 0 to 255. This especially comes in handy when farms and highways are built above the Nether ceiling, because there is a relatively clear cut where the generated Nether ends and where the builds start.

The simplest (but also most unpredictable) method to keep builds above the Nether ceiling but regenerate everything below is to delete all Sections from 0 to 7 and setting the Status field of the chunk to empty.

Deleting sections 0 to 7 and setting Status to empty

This might have some unwanted (or wanted) effects on generated structures, such as Fungi forests or Basalt deltas. Structures from basalt deltas will generate on top of structures on the nether roof, while they will not generate below:

Basalt deltas generating on top of the nether roof while missing below

Partially importing chunks

Chunks can also be partially imported. This is more reliable than deleting and regenerating sections as described above and theoretically allows to also keep builds below the Nether ceiling, but might also result in a lot more work.

To make this work, all chunk we want to import need to have the same DataVersion as the chunks we want to merge them with. The simplest way to do this is to use Minecraft's "Optimize World" feature. The image below shows a Nether highway in our freshly upgraded 1.16 world:

Freshly upgraded nether highway

Next, we will export our highway. Use the method of your choice to make a selection, and export. Here's how the exported nether highway looks like:

Exported nether highway

Then, we open Minecraft and generate all the chunks we need to import our Nether highway. The newly generated chunks look like this:

New nether highway chunks without nether highway

After we did that, we import our Nether highway into our new chunks with the following settings:

Nether highway import settings

  • Offset: We currently don't care about an offset, so we leave it blank.
  • Overwrite existing chunks: Yes, otherwise we won't import anything because all the target chunks are not empty.
  • Apply to selection only: No, because we don't have a selection.
  • Sections: The Nether highway in this example is directly below the bedrock ceiling, so we want to import the section with index 7 and everything above. The section with index 7 starts at Y=112.

Hitting OK and waiting for a second rewards us with this:

Nether highway import successful

Alternatively it is also possible to create a selection first and only allow the chunk import to insert chunks at your selection, to make sure that that import only merges chunks into already generated chunks.


Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment