Describe the bug

As stated in title, annahilation planes break blocks which do not drop anything such as incomplete amethyst buds.

How to reproduce the bug

Have annahilation plane placed against a growing amethyst crystal and observe it will break incomplete crystals that don't drop anything e.g. small amethyst bud.

Expected behavior

Would be better if the annahilation plane waited until it found a state which produces drops or not break the block at all.

Additional details

Issue requested to be opened by Technici4n.

Which minecraft version are you using?

1.17

On which mod loaders does it happen?

Fabric

Crash log

N/A?

would you explain a bit more detailed how this should work?

how should one "configure" the annihilation pane to check for specific block states? There are blocks whithout any item that correlates to their block and their possible blockstates

and there are blocks that don't drop anything and that one is willing to still destroy but not letting you anymore since we now wait for "anything" that drops?! Also i am not sure if you can properly check the block drops before it actually being destroyed ...

on top all my questioning, there are blocks that only by chance drop an item at all, how should them be handled?

the only thing you can do, to work around this, is using a toggle bus to disable the anihilation pane until the block is considered "ready to harvest" by you switching the bus on imho

edit: by the way this is more an feature request than a bug report, you should have used the other template instead

I was thinking that we could have a setting in the GUI that will prevent breaking blocks that don't have any drop. Of course, this implies adding a GUI in the first place... And maybe filter slots in the GUI then :P

yeah but that still leaves open how to properly check for the drop in first place or do i seem to overlook some obvious checkable listing?! isn't items droppping still handled during the break event?!

just to be totally clear here, i want to avoid item duping or "drop optimization" by any chance, since some mod mechanics are connected to with what and or by who their blocks are broken to define the outcome

thinking about it, you could add some sort of "whitelist/blacklist" toggle, switch the device into whitelist mode, place a block in front and then add a "add current block" button that copies all required blockstate data etc. to the whitelist, which immediately breaks the block as sort of confirmation but this still would require extensions to be made later since a lot of mods still apply a lot of modifications to their blocks which might break this featuer easily later on

We already compute the drops to check if the network can accept them I think, so checking if the drop list is empty shouldn't be a problem. It's more about the implications (GUI etc).

I always thought that was an intentional challenge. just like when using annihilation planes for crystal growth automation. and automated amethyst farm was actually the first thing I made with 1.17 fabric AE2.

normal annihilation planes didn't work. final working setup had identity annihilation planes with fully grown clusters whitelisted in storage bus pointing at main network interface. breaking them up would have been another step using a formation plane instead of storage bus. these placed grown cystals could then be broken by normal annihilation plane

Oh indeed if you use silk touch you get the small bud. I didn't know that it also existed in item form. Then yeah this can be done with identity annihilation planes (i.e. silk touch annihilation planes), so I'm closing this issue! Thanks @urmet 😄