Querz/mcaselector 1.11

mcaselector-1.11

on GitHub

This release adds support for deleting and importing specific vertical sections of chunks.

This update adds new features that can be useful when migrating a world to 1.16. Here is a document with some tips and tricks regarding 1.16.

Details:

• Fixed spanish translation (thanks to @NathanielFreeman.
• Fixed some information regarding compatibility in the Readme. MCA Files were first introduced in 1.2.1, not Beta 1.3.
• Removed unused icon for a "default NBT tag" from resources.
• Improved rendering for underwater features, now showing hints of the color of the blocks and better showing the depth of the water. This can still be disabled in the settings.
• Added support for comma separated ranges when deleting chunks. The field DeleteSections now accepts ranges in the format <from>:<to>. E.g: 3:7 means "all sections from 3 to 7, inclusive". From and to can be omitted to define no upper and/or lower bounds, e.g. :7 means "all seaction up to 7, inclusive".
• Added support for custom entities with custom namespaces in the chunk filter. Defining an entity without a namespace automatically assumes the namespace minecraft:. Use single quotes to define custom entities. When using single quotes, a namespace must be defined.
• Added support to import specific sections when importing chunks:
  • The field uses the same range syntax as the DeleteSections field in the NBT Changer.
  • Merges Biomes, Entities, TileTicks, TileEntities, LiquidTicks, Lights, LightsToBeTicked, ToBeTicked and PostProcessing fields.
  • When merging into an empty or non-existing chunk, its Status is set to full.
  • Entity UUIDs are randomized to avoid duplicates.
  • Minecraft does weird things with biomes, so they might not show up correctly in game.
• Updated dependencies to use NBT 5.5.
• Updated documentation, discord badge and screenshots in the Readme.
• Fixed a crash when processing indexed but nonexistent chunks in region files.
• Fixed a memory overflow error when logging too many exceptions.
• Fixed an error that occurred when drawing chunks of an "optimized" world.

"Requirements":

• Either:
  • JRE 8+, you can get it from HERE
  • A Minecraft Java Edition installation
• A computer
• A brain

If you have Java from Oracle installed on your system

Most likely, .jar files are associated with java on your computer, it should therefore launch by simply double clicking the file (or however your OS is configured to open files using your mouse or keyboard). If not, you can try java -jar mcaselector-1.11.jar from your console. If this doesn't work, you might want to look into how to modify the PATH variable on your system to tell your system that java is an executable program.

If you have Minecraft Java Edition installed on your system

Minecraft Java Edition comes with a JRE that you can use to start the MCA Selector, so there is no need to install another version of java on your system. On Windows, that java version is usually located in C:\Program Files (x86)\Minecraft\runtime\jre-x64\bin\ and once inside this folder you can simply run java.exe -jar <path-to-mcaselector-1.11.jar>. On Mac OS you should find it in ~/Library/Application\ Support/minecraft/runtime/jre-x64/jre.bundle/Contents/Home/bin/ where you can execute ./java -jar <path-to-mcaselector-1.11.jar>.

WARNING: For macOS 10.14+ (Mojave) It is NOT recommended to use the JRE provided by Minecraft (1.8.0_74), because it contains a severe bug that causes JavaFX applications to crash when they lose focus while a dialog window (such as the save-file-dialog) is open (see the bug report here). This bug has been fixed in Java 1.8.0_201 and above.

If you are using OpenJDK

If you are using a distribution of OpenJDK, you have to make sure that it comes with JavaFX, as it is needed to run the MCA Selector. Some distributions like AdoptOpenJDK (shipped with most Linux distributions) do not ship with JavaFX by default. On Debian distributions, an open version of JavaFX is contained in the openjfx package. This or some other installation of JavaFX is required to run the .jar.

If you are using Java 11 or higher

If you are using Java 11 or higher, the JavaFX modules are not included automatically. You will need to include them by specifying the module path for JavaFX. Some examples are included below, but you may need to edit paths if your system stores the JavaFX modules in a different location.

On Windows with Oracle Java 13:

"C:\Program Files\Java\jdk-13.0.1\bin\java.exe" --module-path "C:\Program Files\Java\javafx-sdk-13.0.1\lib" --add-modules ALL-MODULE-PATH -jar mcaselector-1.11.jar

On Debian with OpenJDK 11 and openjfx:

java --module-path /usr/share/openjfx/lib --add-modules ALL-MODULE-PATH -jar mcaselector-1.11.jar

If none of these instructions work, apply "A brain" that you providently held ready after having read the "Requirements" section carefully.