Quarry Issues
NielsPilgaard opened this issue · 6 comments
Hey!
When using the RFTools Builder to quarry an area, it has a chance to throw out the block it mines into the world, if the block doesn't have an overwrite in block_overwrites. This issue has also been reported to RFTools.
toolprogression-1.12.2-1.5.1
rftools-1.12-7.51
I can't reproduce this. Neither in my dev environment, in an instance with only RFTools and TPr, AND funnily, not even in the current released version of enigmatica expert. However, I'm unfamiliar with RFTools, maybe I'm holding it wrong... ¯\_(ツ)_/¯
In each case, I quarry in the overworld. I set up an RF Builder with a clearing (silk) quarry card and a RFTools modular storage below the Builder. I select the area with the card and than place it into the builder. Give it a redstone signal and there we go. Hole in the world, but no dropped items.
*edit: Just to be clear, I even have an idea what causes this, but I'm simply not being able to see it myself.
Oh I forgot to mention, it only seems to happen 30% of the time for some reason (according to the original reporter), that could be why you can't replicate it.
I saw that video and figured the 30% was about which blocks were affected and which weren't. But even then, I tried it several times. Do I have to use another Builder? Or some other settings or what not? Judging from the video, it seems pretty reliable to drop all those coal blocks and not breaking them as supposed.
I'm genuinely confused about the fact, it seems to be so hard to reproduce.
Yeah I don't know what's up with that either.
It's not 30% of blocks that bug out, it's 30% of times you use the Builder for a specific place, I think.
okay, found it. Has nothing to do with chance. It solely depends on the blocks broken. I believe it's a wierd interaction between fake players and some blocks not working as expected...
For instance coal blocks. They have a default mining setting of null=-1, however, for some reason the default minecraft code paths think, it is not harvestable... Whatever 🤷
Will be fixed in upcoming 1.5.3