v0.3.7

• Added an --output argument to allow specifying where the output directory should be. The default is still the same.
• -o is no longer the short argument name for --only-blocks-above, to reduce ambiguity (many people would assume it's for --output).
• A message is now printed at the end with the absolute path to where the output file was written.

Full Changelog: v0.3.6...v0.3.7

v0.3.6

Omit heights above 255 for compatibility with JER. Fixes issue #16.

v0.3.5

Added handling of protochunks - by default, they are skipped now. Old behaviour was to include them, which meant if you tried to scan a region that wasn't fully generated, some protochunks got mixed in into the results.
Since now there's no obvious reason not to scan all regions, made --zone optional. If omitted, all regions are scanned in all dimensions. See issue #12.

Full Changelog: v0.3.4...9eaeec3

v0.3.4

Hotfix for #11 - now blocks below the depth limit will be skipped. A proper resolution of this will have to wait until (if) JER starts supporting it.

v0.3.3

Made changes to the JER output format to fix #8.
Added a panic if the zone entered is zero-sized, making it less confusing if you mix up the zone coordinate order.
Also updated dependencies.

Full Changelog: v0.3.2...v0.3.3

v0.3.2

Introduced an option to filter out rare blocks. This is on by default with a low value. See --help for details.

Full Changelog: v0.3.1...v0.3.2

v0.3.1

After finally diving into the details of the anvil format, I realized chunks and blocks were iterated over in a suboptimal order. By iterating in the order they're laid out in the files, an increase in performance of about 5-7x was achieved. (It's probably possible to do even better by writing my own versions of some of the methods in fastanvil, but that's a job for another time.)

Also added a small sanity check - if one of the dimension names passed is invalid (resolves to a folder that doesn't exist), RegionScanner will fail immediately rather than only failing once it tries to scan that dimension.

Full Changelog: v0.3.0...v0.3.1

v0.3.0

Major version bumped because the CLI interface changed a bit (due to porting the argument parsing to latest clap).

• New feature: export to CSV. See readme for details of the format.
• Nicer, colored log messages and errors.
• Now possible to customize the number of rayon worker threads used for scanning.
• Thanks to a fastanvil update, 1.12 and below worlds are now supported - but only vanilla ones.

Full Changelog: v0.2.3...v0.3.0

v0.2.3

Dependency updates. Nothing user-facing changed.

Full Changelog: v0.2.2...v0.2.3

v0.2.2

What's Changed

• Fix world-gen.json representation for JER 1.18 by @RundownRhino in #7
  In v0.2.1, the output in 1.18 worlds wasn't actually JER-compatible and produced an ArrayIndexOutOfBoundsException when loaded by JER, as it reported actual y-levels, whereas JER for 1.18 expects them to have an offset of 64, to make all the y-levels in world-gen.json positive. Now, the file loads correctly.

Full Changelog: v0.2.1...v0.2.2