Tutorial:Advanced Recipes - Revision history

Aizistral: 13 revisions imported

2025-08-21T00:17:36Z

13 revisions imported

Stan at 17:37, 5 September 2015

2015-09-05T17:37:11Z

Mystara: Corrected a recipe that converted to an incorrect link instead of showing properly.

2015-08-20T06:51:50Z

Corrected a recipe that converted to an incorrect link instead of showing properly.

Stan at 09:40, 22 September 2014

2014-09-22T09:40:50Z

Stan at 17:53, 31 August 2014

2014-08-31T17:53:35Z

Stan at 20:15, 27 August 2014

2014-08-27T20:15:12Z

Stan at 20:34, 4 July 2014

2014-07-04T20:34:26Z

Stan at 20:34, 4 July 2014

2014-07-04T20:34:13Z

Stan at 20:33, 4 July 2014

2014-07-04T20:33:44Z

Stan at 20:32, 4 July 2014

2014-07-04T20:32:11Z

@@ Line 119: / Line 119: @@
 Then it's just a matter of writing the code to fix the pickaxe:
-  recipes.addShapeless(<minecraft:stone_pickaxe>, [<minecraft:stone_pickaxe>.marked("pick"), <minecraft:cobblestone>], function(output, inputs, crafting) {
+  recipes.addShapeless(<minecraft:stone_pickaxe>, [<minecraft:stone_pickaxe>.anyDamage().marked("pick"), <minecraft:cobblestone>], function(output, inputs, crafting) {
     // the max is there to make sure that the damage doesn't go negative
     // fixes 25 damage per cobblestone
     return inputs.pick.withDamage(max(0, inputs.pick.damage - 25));
+  });
 More will come to function recipes later!

@@ Line 10: / Line 10: @@
   val stickedPick = pick.withTag({display: {Name: "Sticked pick", Lore: ["This pick", "Has been sticked"]}});
-  recipes.addShaped(damagedPick, [[pick, stick]]);
+  recipes.addShaped(damagedPick, [[pick, stick]<nowiki>]</nowiki>);
   recipes.addShaped(stickedPick, [[pick, stick], [stick, stick]]);
@@ Line 24: / Line 24: @@
   val stickedPick = pick.withTag({display: {Name: "Sticked pick", Lore: ["This pick", "Has been sticked"]}});
-  recipes.addShaped(damagedPick, [[pick, stick]]);
+  recipes.addShaped(damagedPick, [[pick, stick]<nowiki>]</nowiki>);
   recipes.addShaped(stickedPick, [[pick, stick], [stick, stick]]);

← Older revision		Revision as of 09:40, 22 September 2014
Line 98:		Line 98:

	GiveBack will usually also have the side-effect of suppressing mod item return behavior. It may thus be a handy alternative to the transformReplace modifier in those cases.		GiveBack will usually also have the side-effect of suppressing mod item return behavior. It may thus be a handy alternative to the transformReplace modifier in those cases.
		+
		+	== Function recipes ==
		+
		+	When adding a recipe, you may also supply an additional argument, which is a custom function. This function can programmatically determine the output of your recipe.
		+
		+	To demonstrate how this works, let's make a recipe that repairs a stone pickaxe when you craft it with cobblestone. The output of our recipe depends on the pickaxe that is provided (its damage), thus a regular recipe won't work in this case.
		+
		+	Let's start by adding the function to it:
		+
		+	recipes.addShapeless(<minecraft:stone_pickaxe>, [<minecraft:stone_pickaxe>, <minecraft:cobblestone>], function(output, inputs, crafting) {
		+	// to be implemented
		+	}
		+
		+	Now we need to look at the value of the pickaxe. In order to retrieve the actual values of the inputs, we need to mark them with a name, and MineTweaker will store it in the inputs list:
		+
		+	recipes.addShapeless(<minecraft:stone_pickaxe>, [<minecraft:stone_pickaxe>.marked("pick"), <minecraft:cobblestone>], function(output, inputs, crafting) {
		+	// to be implemented. inputs.pick now contains the pickaxe used as input
		+	}
		+
		+	Then it's just a matter of writing the code to fix the pickaxe:
		+
		+	recipes.addShapeless(<minecraft:stone_pickaxe>, [<minecraft:stone_pickaxe>.marked("pick"), <minecraft:cobblestone>], function(output, inputs, crafting) {
		+	// the max is there to make sure that the damage doesn't go negative
		+	// fixes 25 damage per cobblestone
		+	return inputs.pick.withDamage(max(0, inputs.pick.damage - 25));
		+	}
		+
		+	More will come to function recipes later!

← Older revision		Revision as of 17:53, 31 August 2014
Line 80:		Line 80:

	Now, crafting a grass block will return the empty crafting bucket in the crafting grid.		Now, crafting a grass block will return the empty crafting bucket in the crafting grid.
		+
		+	Sometimes mods define their own behavior when you use their items while crafting. Likewise, Minecraft will return you an empty bucket when you use it in a crafting recipe. If you don't want that, you can tell the item to not return anything at all:
		+
		+	recipes.addShaped(<minecraft:grass>, [[
		+	<minecraft:dirt>,
		+	<minecraft:water_bucket>.noReturn(),
		+	<minecraft:wheat>
		+	]]);
		+
		+	If you want to give something back, but not in the crafting inventory, you can also use giveBack. GiveBack can be used without arguments, in which case it will return the original item, or it can be used with an item, in which case that item will be given back into the player inventory:
		+
		+	recipes.addShaped(<minecraft:grass>, [[
		+	<minecraft:dirt>,
		+	<minecraft:water_bucket>.giveBack(<minecraft:iron_ore> * 3),
		+	<minecraft:wheat>
		+	]]);
		+
		+	GiveBack will usually also have the side-effect of suppressing mod item return behavior. It may thus be a handy alternative to the transformReplace modifier in those cases.

← Older revision		Revision as of 20:15, 27 August 2014
Line 33:		Line 33:

	What about the lore part in our sticked pick? Since your condition only contains the name, the lore part is ignored - when setting a condition on the data tag, MineTweaker only cares about the contents that you specified and ignores everything else.		What about the lore part in our sticked pick? Since your condition only contains the name, the lore part is ignored - when setting a condition on the data tag, MineTweaker only cares about the contents that you specified and ignores everything else.
		+
		+	'''''Note the difference between withTag and onlyWithTag. withTag is for an output and is the exact tag that will be output. onlyWithTag is for input and sets a condition. Applying withTag on an input has no effect on the recipe.'''''

	Other conditions exist too:		Other conditions exist too:

← Older revision	Revision as of 00:17, 21 August 2025
(No difference)

@@ Line 73: / Line 73: @@
   recipes.addShaped(<minecraft:grass>, [[
   	<minecraft:dirt>,
-  	<minecraft:water_bucket>.transformReplace(<minecraft:bucket>)),
+  	<minecraft:water_bucket>.transformReplace(<minecraft:bucket>),
   	<minecraft:wheat>
   ]]);
 Now, crafting a grass block will return the empty crafting bucket in the crafting grid.

@@ Line 1: / Line 1: @@
 So far we have learned about how to add or remove simple recipes. But what if the inputs and outputs also involve damage values or NBT tags?
-## NBT Tag in output ##
+== NBT Tag in output ==
 It is possible to define both damage or an NBT tag as output. Let's take a pickaxe as our toy for this tutorial:
@@ Line 15: / Line 15: @@
 Crafting the pick with 1 or 3 sticks as in the recipe will give you an item with the appropriate damage and name/lore on it, respectively.
-## Input conditions ##
+== Input conditions ==
 You can also require the input to contain certain NBT tags. Say, you make a recipe that requires our sticked pick. Let's modify our file:
@@ Line 45: / Line 45: @@
   myItem.onlyDamaged().onlyWithTag({display: {Name: "Sticked pick"}});
-## Output reuse and transformations ##
+== Output reuse and transformations ==
 Since MineTweaker 3.0.2, it is now possible to reuse items, return empty buckets to the crafting grid (or whatever item you want) or damage items upon crafting.

@@ Line 1: / Line 1: @@
 So far we have learned about how to add or remove simple recipes. But what if the inputs and outputs also involve damage values or NBT tags?
 It is possible to define both damage or an NBT tag as output. Let's take a pickaxe as our toy for this tutorial:
@@ Line 12: / Line 14: @@
 Crafting the pick with 1 or 3 sticks as in the recipe will give you an item with the appropriate damage and name/lore on it, respectively.
 You can also require the input to contain certain NBT tags. Say, you make a recipe that requires our sticked pick. Let's modify our file:
   val stick = <minecraft:stick>;
   val pick = <minecraft:stone_pickaxe>;
@@ Line 27: / Line 28: @@
   val stonedPick = pick.withTag({display: {Name: "Stoned pick", Lore: ["This pick", "Has been experimenting too much"]}});
-  val onlyStickedPick = pick.only(Condition.data({display: {Name: "Sticked pick"}}));
+  val onlyStickedPick = pick.onlyWithTag({display: {Name: "Sticked pick"}});
   val cobble = <minecraft:cobblestone>;
   recipes.addShaped(stonedPick, [[onlyStickedPick, cobble], [cobble, cobble]]);
@@ Line 33: / Line 34: @@
 What about the lore part in our sticked pick? Since your condition only contains the name, the lore part is ignored - when setting a condition on the data tag, MineTweaker only cares about the contents that you specified and ignores everything else.
-You may also have noticed the new element in this script - an import. The imported class, Condition, contains a set of standard crafting conditions - such as requiring a specific damage or tag, or having a damage value between certain bounds.
+Other conditions exist too:
-''More functionality will soon become available in the form of transformers, making it possible to reuse items and have items damaged upon used or to have custom functions define crafting output. However, it's not yet fully implemented''
+Now, crafting a grass block will return the empty crafting bucket in the crafting grid.