Question/Feature request: Is there a way to find out the exact coordinates a Builder Quarry is working on?

Question

Question/Feature request: Is there a way to find out the exact coordinates a Builder Quarry is working on?

Nightcaste opened this issue 4 years ago · 2 comments

Nightcaste commented 4 years ago

I'm having an issue where the builder will start reporting that the output chest is full, when it isn't. It's happening in one particular chunk of the area I set it up for, but there's nothing to even point me in a direction to go looking for the spot it's trying to mine and having a problem.

I would like to know if there is any way to find out where a builder is currently working, specifically through The One Probe or through the Builder GUI.

If there isn't a way to do this, I would like to ask that something be added that allows for this kind of diagnostics.

McJty · Answer 1 · 2021-01-23T13:13:24.000Z

Check the buttons on the builder gui. One of the buttons is for this purpose. If you enable that button the builder will give a visual hilight of the block it is working on in game

Nightcaste · Answer 2 · 2021-01-23T13:22:14.000Z

Without some kind of coordinates, it's still difficult to find where that block is located. With the range capability of the Builder, that location could be hundreds of blocks away, in a direction that isn't indicated. I did manage to find it, though. It turns out that it's a "flesh" block from one of the biome mods in the pack. It would be helpful if the feedback from the block was more accurate to the problem. It's telling me there's no room in the chest, when the problem is that it doesn't understand what to do with the block it found. Even saying "unknown block detected" would be better than "the chest is full".

…

On Sat, Jan 23, 2021, 8:13 AM McJty ***@***.***> wrote: Check the buttons on the builder gui. One of the buttons is for this purpose. If you enable that button the builder will give a visual hilight of the block it is working on in game — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#2118 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACY6J2XJBLLYXAMWWUC74ALS3LDQBANCNFSM4WPTQVLA> .

Share to