Fix ME output hatch void protection again #3594
Merged
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.
ME output hatch void protection had 4 different issues at different points:
ME output hatches gaining a limited capacity introduced bugs 1, 2, and 3.
#3585 fixed bug 1, but introduced bug 3. Bug 2 and 4 remained unfixed with that PR.
This PR fixes bugs 1, 2, and 3:
VoidProtectionHelper
in the second commitMTEMultiBlockBase
in the second commitfill()
on these hatches always claims to accept all fluid, regardless of if it actually can due to the cross-over between forge fluid api and AE2 apiCloses GTNewHorizons/GT-New-Horizons-Modpack#17711