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

Allow for Voiding Cover's functioning on Input Bus/Hatch #2633

Open
ChromaPIE opened this issue Oct 5, 2024 · 0 comments
Open

Allow for Voiding Cover's functioning on Input Bus/Hatch #2633

ChromaPIE opened this issue Oct 5, 2024 · 0 comments

Comments

@ChromaPIE
Copy link
Contributor

GregTech CEu Version

2.8.10-beta

Related Problem

This is actually related to another mod's problem but I'm not elaborating it here. But please don't ask questions like Why bother voiding items in the Bus when you can just keep them away with a Filter in Pipes/Tubes/Conduits. That's the whole point of the problem I'm facing. I have to let things go in, then void them.

TL;DR: GregTech-wise, if you can install the Voiding Cover on Input blocks, it should void things.

Its function on Input Buses now (should also apply to Fluid Hatches):

  • Does nothing when installed on an idle (no external I/O or other interactions) side.
  • Voids items coming right into the side the cover is on from external sources, which is obviously meaningless, but if you add an Item Filter in the cover's setting it will do the voiding, but also block everything else from going in, which is kind of counter-intuitive because players tend to assume that it will void the matching items, meanwhile let other items pass and go into the bus, which, yeah, do be achievable for a normal container like a Chest because you can just attach the cover to other sides, but for an Input Bus, as I said it does literally nothing on an idle side.

Your Solution

Let Voiding Covers do what they're supposed to do, delete stuff from Input components for Multiblocks

Additional Information

No response

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

1 participant