#[1.19.2] Faucets and Create containers

17 messages · Page 1 of 1 (latest)

tired bridge
#

Previously, if you left a faucet running while it was connected to a filled Create block, the liquid wouldn't transfer unless the output block had space.
For example, if I put 10 buckets of milk into a tank, then use a faucet to pump one bucket into a spout, it wouldn't add any more milk until that spout is empty. Currently, for some reason, the faucet tries to transfer even if the output is full, so leaving the tap running drains all the liquid in the tank if left unattended. Is this intentional?

azure orbit
#

so it voids liquid?

tired bridge
#

yeah it just goes away

#

this was after I refilled the tank, but when I came back to this site earlier, it was completely empty and the spout only had 1000mb in it (which is full)

azure orbit
#

does it happen with other tanks as output?

#

its been ages since I changed that logic and I'm using forge fluid api to request fluid transfers so seems weird it would break since its the target block that decides when stuff can go in

tired bridge
#

I'll give it a go

#

It does it with a tank as the output too

#

it's also not unique to milk, as my honey storage tank did the exact same thing

azure orbit
#

I can confirm that it is a create bug

#

their fluid tanks IFluidHandler::fill(amount, FluidAction.SIMULATE) does not infact simulate and fills it instead

#

wait

#

I'll do some more testing

#

maybe forge changed some contracts

#

maybe I fond a better way to do it so its on my end after all

#

good

tired bridge
#

ooh