ZacSharp

Oh, I though it was target commit plus pr number, but it's pr commit plus pr number. That's way better then.

This is definitely one of the other mods causing the problem (and it's probably their fault as well). MalisisCore was already reported to cause this issue (https://github.com/cabaletta/baritone/issues/669#issuecomment-516372417) but there's likely...

@EmersonDove are you still working on this?

> Issues with this version: > * Some states (such as iron bars) are unrecognized > * In 1.12, the long array (blockstates) isn't exposed by the libraries so parsing...

For the mixin you probably want a simple mixin on `NBTTagLongArray` with an `@Accessor` for the data field. Since Baritone has the mixin classes in a separate source set you...

I've had a look at it and I think you can copy the changes from https://github.com/ZacSharp/baritone/commit/0550fe362369d12e0aefe6ffb0b8f9190f2f7f69 as is. I also had a try at loading all regions of the schematic...

I've invested some more time and used the approach from #3317 (patching the holes with air) to fix `mapArtMode`. You can find the changes at https://github.com/ZacSharp/baritone/commit/3661fea4f05755ebf285b883aabfe2abde34f76d and its parents in...

I also failed to reproduce the bug with iron bars not being loaded correctly, all 16 worked.

What's currently missing (both done on my branch but @EmersonDove hasn't done it here yet) * Read all regions of the .litematic instead of just the first * Get rid...

I think the problem of MLGs and long parkour jumps (which Baritone can't do anyway) can be avoided by making the option incompatible with ~`allowPlace`~ some setting for those movements,...