-
Notifications
You must be signed in to change notification settings - Fork 176
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 multiple build actions per recipemap #2278
Conversation
@@ -197,7 +197,8 @@ public final class RecipeMaps { | |||
@ZenProperty | |||
public static final RecipeMap<AssemblyLineRecipeBuilder> ASSEMBLY_LINE_RECIPES = new RecipeMapAssemblyLine<>( | |||
"assembly_line", new AssemblyLineRecipeBuilder(), AssemblyLineUI::new) | |||
.onRecipeBuild(AssemblyLineManager::createDefaultResearchRecipe); | |||
.onRecipeBuild(gregtechId("default_research_recipe"), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why does this one use onRecipeBuild
instead of onBuild
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This RecipeMap does not utilize RecipeMapBuilder
, and therefore must call RecipeMap#onRecipeBuild
instead.
What
Allows multiple build actions per RecipeMap. This prevents addons having to copy paste the default ones and add to them. Also prevents addons overwriting each other.
Requires build actions to have an associated ResourceLocation to denote them. Also allows removal via this location.
Potential Compatibility Issues
Is not backwards compatible. Build actions now have a required namespace field, which cannot be inferred on our end for backwards-compatibility.