Issue type:

• ➕ Feature request

Short description:

When using importers/exporters that support 'empty is wildcard' this would seem to make more sense to default to 'false'.

For example:

• I have lava and another liquid on the same network
• I place an interface to export liquid to the world
• I use a choice operator, where the 'false' condition is an 'empty' fluid

Currently, defaulting the world fluid exporter to 'empty is wildcard = true' in an automation setup that also places items in the world in the same block space as the fluid could choose the lava and destroy the items if the user does not change the 'empty is wildcard' setting.

I went back and forth a lot on this already. But you make a good point. I'll see to changing this in 1.13/1.14 (I don't want to be breaking existing setups)

Changed for the 1.15 update