make all variants of GTRecipeBuilder#adjacentBlock and #adjacentFluid overloads of each other#4526
Merged
jurrejelle merged 3 commits intoGregTechCEu:1.20.1from Feb 8, 2026
Conversation
…uid` use the same method name and be overloads of each other Deprecate the methods that were added in 7.2.1 for removal in 8.0.0.
jurrejelle
approved these changes
Feb 8, 2026
YoungOnionMC
approved these changes
Feb 8, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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
Deprecate the duplicate adjacency condition helpers that were added in 7.2.1.
Every
AdjacentFluidConditionsetter is now namedadjacentFluids& everyAdjacentBlockConditionsetter is nowadjacentBlocks.Implementation Details
Added even more of the same methods and deprecated the duplicates.
Outcome
No 3 different names for overloads of the same method (in the future, at least)
How Was This Tested
There's nothing to test, as it's just deprecations and renames.
Additional Information
The deprecated methods should actually be removed in 8.0.0, as they clutter the class quite a lot.
Potential Compatibility Issues
None, the old methods still exist.