Please add a brief but descriptive title
SouthernPixel opened this issue · 13 comments
What do you need help with?
With as much detail as possible, describe your question and what you may need help with.
You keep closing the conversation before I can even reply and before the issue is even resolved.
I could'nt make a list for #blockstoavoidbreaking but now I can but i am still having the issue of not being able to prevent baritone from mining those blocks entirely. I have iron_block and beacon on that list and it still pathfinds to my beacons when i use #sel cleararea
Please this issue is not resolved yet so please stop closing it when its not resolved yet. If its a well known bug then say it dont just close the conversation without any explanation or reasoning
Not trying to be be rude im just annoyed
Final checklist
- I know how to properly use check boxes
- I have not used any OwO's or UwU's in this issue.
And by the way you can continue a conversation on closed issues. If you think an issue has not been resolved then try convincing the maintainers that it is not resolved so they reopen it.
And as for the "known bug" thing: there's plenty of issues duplicating that. If none of them is open then someone should probably make one dedicated to the blocksToAvoidBreaking problem and nothing else.
Thank you for replying. Well I did reply on a closed topic but nobody is replying back because its closed. Here is the screenshot https://imgur.com/a/rqYlMOZ
oh ok
blockPlacementPenalty 20.0
blocksToAvoid iron_block
blocksToAvoidBreaking iron_block,beacon,chest,trapped_chest,furnace,ender_chest
buildIgnoreBlocks iron_block,beacon
allowParkour true
allowParkourPlace true
blockReachDistance 5.0
maxFallHeightBucket 255
chatControl false
layerOrder true
followRadius 100
but i am still having the issue of not being able to prevent baritone from mining those blocks entirely
Oh I missed this part, the formatting is weird. This is a known bug.