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

Interface Blocking mode does not respect fluids in GTCEu Quad Hatches #162

Closed
pyure opened this issue Jun 15, 2024 · 1 comment
Closed

Comments

@pyure
Copy link

pyure commented Jun 15, 2024

1.12.2
AE2-2.6.1-r.jar
GTCEu 2.8.7-beta

To reproduce:

  • Build a GTCEu Large Chemical Reactor with a Quad input hatch
  • Connect it to an AE2 network (with discretizer etc)
  • Ensure it has access to Oxygen and Nitrogen
  • Create a recipe pattern for it to create Oxygen + Nitrogen -> Nitrogen Dioxide (requires an input buffer with circuit 3 configured)
  • Attach an interface to the Quad Input Hatch
    • Important: do not face the hatch at the interface or it may pull fluids, invalidating the test
    • Does not matter if you use a regular interface vs a dual; both will exhibit the same behaviour
  • Use Blocking Mode - Block All (Items and Fluids)
  • Put the nitrogen dioxide pattern into the interface
  • Put a random fluid into a slot of the quad interface (neither oxygen nor nitrogen)
  • Request nitrogen dioxide

Expected outcome:

  • The recipe should fail to execute because the hatch has a blocking fluid present
  • Reasoning: Item-based blocking will block execution of a recipe in e.g. an Assembling Machine even if only 1 slot is blocked and there's plenty of "room" for the ingredients. Same should be true for fluid-based blocking.

Actual outcome

  • The recipe will execute, possibly triggering an undesirable recipe with your random fluid if one such matches

Somewhat related to #116

@GlodBlock
Copy link
Collaborator

fixed by fd5fa38

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants