Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Weird behaviour from fluid annihilation planes #3899

Closed
FelixLouis opened this issue Jan 7, 2019 · 2 comments
Closed

Weird behaviour from fluid annihilation planes #3899

FelixLouis opened this issue Jan 7, 2019 · 2 comments
Labels

Comments

@FelixLouis
Copy link

@FelixLouis FelixLouis commented Jan 7, 2019

Case of an annihilation plane not working when supposed to store in a fluid interface

Describe the bug

A subnetwork containing only a fluid annihilation plane (facing an infinite water source) and a fluid storage bus (facing a tank or a fluid interface) won't consider the tank/interface as valid to recieve water from the annihilation plane (and thus the plane won't work)

To Reproduce

Copy the setup in the screenshot.

Expected behavior

Additional context

screenshot of the setup: https://imgur.com/a/U8evouG
a reddit post where I describe it: https://www.reddit.com/r/feedthebeast/comments/adjyxm/applied_energistics_how_do_annihilation_planes/

Environment

Gregblock Modpack

  • Minecraft Version: 1.12.2
  • AE2 Version: rv6-stable-4
  • Forge Version: 14-23-5-2768
@Ommina
Copy link

@Ommina Ommina commented Jan 8, 2019

#3767 -- I think?

If so, this is fixed in stable-5. If possible, try upgrading your version of AE2 and see if the issue persists.

@yueh
Copy link
Member

@yueh yueh commented Jan 8, 2019

@Ommina Nope, unrelated. Or at least a follow up bug.

Basically the flag for a configured fluid interface is not set, thus it will expose the whole network inventory and thus allow it to be completely filled.
So it just needs to behave like the item interface, once a slot/tank is set to keep a certain item/fluid, it will expose the the local inventory and no longer the network one.

@yueh yueh added the bug label Jan 8, 2019
@yueh yueh closed this in 46355a4 Jan 15, 2019
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 27, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants