Improved locking Fluids in Output Hatches #2686
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
fecking spotless xD
Contributor
Author
|
me stupid |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What
I've added a second way of locking fluids in output hatches, because the old one is kind of a hassle sometimes imo. Since a recipe has to be run in order to fill the output in the first place, there's no way to lock fluids before the first run of the multiblock. If the fluids then end up in the wrong hatch, you're still screwed.
Outcome
You can now place a fluid container in the input slot of the hatch and press the lock button. If the container contains a fluid, the locked fluid will be set to that one. With that option, you can filter your outputs inb4 running recipes.
Additional Information
I've left the original way untouched and put that as priority. Meaning, it will take predence over the method I've implemented.
Screenshots attached.