BuildInLayers doesn't work as expected about baritone

[Blizzen]

I have another bug with #StartAtLayer that I have a feeling is related to the above report - I will wait to submit that issue until this is confirmed as a bug.

[ZacSharp]

You have skipFailedLayers enabled so if it says it skipped a layer and then starts placing on the next that's probably working as intended. Due to how BuilderProcess works it can decide it can't build a layer if there is nothing to do locally, even if walking a few blocks over would allow it to continue on the current layer.

[Blizzen]

Its not necessarily skipping failed layers, as in my tests there were no failed layers due to it being a small schematic for testing with 100% of required blocks. For example, if my schematic is a wall 2 blocks tall, #layerorder true, the expected outcome is building (locally) the top layer first. However, the builder will place layer 1 and 2 simultaneously, rather than "bridging" along the 2nd layer (or skipping the second layer entirely due to #skipfailedlayers). Please let me know if I am misunderstanding.

[ZacSharp]

You mean it should work like this?

2024-03-10.00-48-28.mp4

(I disabled randomLooking113 because the jitter it causes annoys me, you don't need to change it)

[Blizzen]

I figured out that whenever I experience this issue, it seems like baritone isn't taking #buildinlayers into account., as it is missing the "starting layer x" text in debug/chat. But that would be a different issue, I can make a new issue when I figure out how to replicate this