EMI synthetic recipe warning fix#4732
Merged
gustovafing merged 1 commit intoGregTechCEu:1.20.1from Mar 14, 2026
Merged
Conversation
YoungOnionMC
approved these changes
Mar 14, 2026
YoungOnionMC
added
type: bugfix
9 tasks
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
For custom EMI categories, the EMI recipes don't correspond to a real underlying recipe. In this case, EMI requires the path part of the recipe to start with a
/to know it's not a mistake.Right now GT registers several different synthetic recipes, some of them correctly like the Ore Vein index.
A few of them are missing the
/prefix: Multiblocks, Ore Processing, and Programmed Circuits. This causes several hundred EMI errors, drowning out legitimate issues.This PR adds the missing slashes.
This only affects the EMI recipe IDs for these synthetic pages, but not any actual gameplay, items, or recipes.
getId()here is specifically an EMI function,dev.emi.emi.api.recipe.EmiRecipe::getIdso it doesn't affect anything else.