ZacSharp

While that definitely helps (`buildOnlySelection` is also an option) I'd really like to know why Baritone can't handle such big schematics because it should never forget about correct positions and...

Can you maybe test https://github.com/ZacSharp/baritone/commit/74b708ec02222faf9e008896afea926dec70a9ac (build artifacts are [here](https://github.com/ZacSharp/baritone/actions/runs/1720594644))? It should prevent the loop but at the same time seems to introduce some new odd behaviour, maybe it works for...

https://github.com/ZacSharp/baritone/commit/2d9852fe9b6164fdfa624f4658b7b9a1523ade40 (artifacts [here](https://github.com/ZacSharp/baritone/actions/runs/1752867714)) should fix the weird behaviour plus another bug that happened way more often because of that fix. EDIT: the workflow artifacts are long expired, here's a manually...

The problem is not the pathfinding itself but rather the way certain blocks have to be placed and that however you fix it you inevitably have to fix more and...

Scaffolding as well

In that case we probably have to rename `BetterBlockPos.x`, `BetterBlockPos.y` and `BetterBlockPos.z` to work around https://github.com/md-5/SpecialSource/issues/72 (or whatever else is incorrectly and incompletely remapping our `public final` fields). Apart from...

> what mappings would deobf use though? would this only solve the problem for certain mappings like mcp? like this wouldn't work for a fabric mod developer for new versions...

Forgot to include in my review: The scope looks simple and small. That's good. Not sure what that `autoCraft` setting is supposed to be though. So far you don't seem...

For placing I know brute force is inefficient (very limited range if you don't want to cause a lagspike) so I'd suggest just doing something like what `BuilderProcess` uses to...

Merging master into your branch again is probably the easiest way, yes.