https://forge.gemwire.uk/index.php?action=history&feed=atom&title=Datageneration%2FRecipes%2F1.18 2026-05-01T18:23:40Z Revision history for this page on the wiki MediaWiki 1.35.0 https://forge.gemwire.uk/index.php?title=Datageneration/Recipes/1.18&diff=3170&oldid=prev 2022-06-10T07:44:11Z

<p>Copy <a href="/wiki/Datageneration/Recipes" title="Datageneration/Recipes">Datageneration/Recipes</a> to MC1.18 archive</p> <p><b>New page</b></p><div>Recipes can be generated by creating an extension of Minecraft's &lt;code&gt;RecipeProvider&lt;/code&gt; class. From there, recipes can be registered by overriding &lt;code&gt;RecipeProvider#buildCraftingRecipes&lt;/code&gt;.<br /> <br /> {{Colored box|title=Info|content=Remove the &lt;code&gt;super&lt;/code&gt; call within the method. Otherwise, you will generate all recipes from Minecraft as well.}}<br /> <br /> == Recipe Builders ==<br /> <br /> All recipes need to be formatted as an &lt;code&gt;FinishedRecipe&lt;/code&gt;. Each vanilla recipe has a static constructor builder that can be used to create a finished recipe. These can be built by passing the required parameters and then calling &lt;code&gt;&lt;nowiki&gt;#save&lt;/nowiki&gt;&lt;/code&gt;.<br /> <br /> {{Colored box|title=important|content=All recipes must have a different path. If two recipes have the same result, use &lt;code&gt;&lt;nowiki&gt;#save(Consumer&lt;FinishedRecipe&gt;, ResourceLocation)&lt;/nowiki&gt;&lt;/code&gt; instead. This will allow you to specify a different name for the recipe such that it will not override the other.}}<br /> <br /> There are six vanilla recipe builders: &lt;code&gt;ShapedRecipeBuilder&lt;/code&gt; for shaped recipes, &lt;code&gt;ShapelessRecipeBuilder&lt;/code&gt; for shapeless recipes, &lt;code&gt;SimpleCookingRecipeBuilder&lt;/code&gt; for furnace type recipes, &lt;code&gt;SpecialRecipeBuilder&lt;/code&gt; for nondeterministic logic, &lt;code&gt;SingleItemRecipeBuilder&lt;/code&gt; for stonecutting recipes, and &lt;code&gt;UpgradeRecipeBuilder&lt;/code&gt; for smithing recipes.<br /> <br /> For any recipe to be valid, a criterion must be met to obtain the recipe within the recipe book. This can be attached via &lt;code&gt;&lt;nowiki&gt;#unlocks&lt;/nowiki&gt;&lt;/code&gt;. The &lt;code&gt;RecipeProvider&lt;/code&gt; class has some basic criteria creators to check whether a player's inventory has a certain item or whether a player has entered into a specific block.<br /> <br /> == &lt;code&gt;ConditionalRecipe&lt;/code&gt; ==<br /> <br /> To specify if a recipe should be loaded at runtime, a &lt;code&gt;ConditionalRecipe&lt;/code&gt; can be used in conjunction with a recipe builder. Conditions must be added before the recipe via &lt;code&gt;ConditionalRecipe$Builder#addCondition&lt;/code&gt;. Then, once a recipe is added, all previous conditions are cleared for the next to be added. There are a few helper methods for conditions that can be implemented via &lt;code&gt;IConditionBuilder&lt;/code&gt;.<br /> <br /> <br /> [[Category:Data Generation/1.18|Category:Data Generation]]</div>

ShrimpBot