Tutorial:Basic Recipes - Revision history

Aizistral: 12 revisions imported

2025-08-21T00:17:36Z

12 revisions imported

Stan at 06:16, 21 April 2015

2015-04-21T06:16:58Z

Stan at 13:48, 23 December 2014

2014-12-23T13:48:26Z

Stan at 07:05, 28 August 2014

2014-08-28T07:05:05Z

174.97.58.5 at 16:30, 30 June 2014

2014-06-30T16:30:01Z

Stan at 08:40, 28 June 2014

2014-06-28T08:40:28Z

Stan at 08:36, 28 June 2014

2014-06-28T08:36:09Z

Stan at 08:26, 28 June 2014

2014-06-28T08:26:47Z

Stan at 09:45, 25 June 2014

2014-06-25T09:45:34Z

Stan at 18:22, 21 June 2014

2014-06-21T18:22:58Z

← Older revision		Revision as of 06:16, 21 April 2015
Line 71:		Line 71:

	Fixed! Of course, you should use the ore dictionary entry for planks, which would be even better as it would be compatible with mod-added planks :)		Fixed! Of course, you should use the ore dictionary entry for planks, which would be even better as it would be compatible with mod-added planks :)
		+
		+	If need the full name of an item, you can hold it in your hand and use the /minetweaker hand command. It will print the name and copy it to the clipboard, so you can just paste it directly in your script.

	== Other kinds of recipes ==		== Other kinds of recipes ==

← Older revision		Revision as of 13:48, 23 December 2014
Line 1:		Line 1:
		+	== Using MineTweaker RecipeMaker ==
		+
		+	If you want to create or remove recipes without having to code, you can also check out this nice mod by DoubleDoorDevelopment: http://minecraft.curseforge.com/mc-mods/226294-minetweaker-recipemaker
		+
	== Using recipe notation ==		== Using recipe notation ==

@@ Line 66: / Line 66: @@
   recipes.addShaped(<minecraft:stick> * 4, [[<minecraft:planks:*>, null], [null, <minecraft:planks:*>]]);
-Fixed!
+Fixed! Of course, you should use the ore dictionary entry for planks, which would be even better as it would be compatible with mod-added planks :)
 == Specific recipe removal ==

@@ Line 11: / Line 11: @@
   recipes.addShaped('''recipe output''', '''recipe contents''');
-This line essentially means "call the addShaped function on the recipes object". The recipes object is a special object that is available from anywhere in your code and contains all the functions related to adding and removing crafting recipes. Not that only crafting recipes are managed by the recipes object - furnace recipes, for instance, are managed by the furnace object (which you will learn about in a later tutorial) and mods machines have yet different methods to manage recipes.
+This line essentially means "call the addShaped function on the recipes object". The recipes object is a special object that is available from anywhere in your code and contains all the functions related to adding and removing crafting recipes. Note that only crafting recipes are managed by the recipes object - furnace recipes, for instance, are managed by the furnace object (which you will learn about in a later tutorial) and mods machines have yet different methods to manage recipes.
 Now, how do we call the addShaped function with proper arguments? We need to tell it what the output should be and what the recipe should be like.

@@ Line 40: / Line 40: @@
     [<minecraft:iron_ingot>, null, <minecraft:iron_ingot>]]);
-MineTweaker doesn't care about how you split your code into lines, so you could also put the recipe in a single line:
+Or you can split the line differently for readability, since MineTweaker doesn't care how you split your code into lines. You could also retrieve the iron ingot once, assign it to a variable and then reuse it, as will be described at the end of this tutorial.
-−
- recipes.addShaped(<minecraft:iron_leggings>, [[<minecraft:iron_ingot>, <minecraft:iron_ingot>, <minecraft:iron_ingot>], [<minecraft:iron_ingot>, null, <minecraft:iron_ingot>], [<minecraft:iron_ingot>, null, <minecraft:iron_ingot>]]);
-−
-Or you can split the line differently for readability.. it doesn't matter. Just
 = Basic Recipes =

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

@@ Line 1: / Line 1: @@
 = Basic Recipes =
-The most basic modifications you can perform in MineTweaker are recipe addition and removal.
+There is no visual editor, so you have to understand how to write your recipes as text.
 As a little introduction, let's consider the recipe for sticks. In vanilla minecraft, it takes 2 wood planks to make 4 sticks, and they have to put above each other. But what if we want to change that? What if, say, we find it more logical to put the two wood block diagonally instead? (this stick is diagonal, right?)

← Older revision		Revision as of 09:45, 25 June 2014
Line 47:		Line 47:

	recipes.removeShapeless(<minecraft:wool:*>, [<minecraft:wool>]); // removes all wool coloring recipes		recipes.removeShapeless(<minecraft:wool:*>, [<minecraft:wool>]); // removes all wool coloring recipes
		+
		+	== Subitems and damage values ==
		+
		+	Quite often, items have multiple subitems. A very well-known example are coal and charcoal. Both have the same ID (minecraft:coal) but have a different meta value.
		+
		+	When loading an item, you can specify the meta value for the subitem:
		+
		+	var coal = <minecraft:coal:0>; // same as <minecraft:coal>
		+	var charcoal = <minecraft:coal:1>;
		+
		+	When the subitem is not specified, :0 is filled in for the subitem.
		+
		+	If you want a recipe to match any subitem, you can use the wildcard syntax:
		+
		+	var anyCoal = <minecraft:coal:*>;
		+
		+
		+	Many kinds of items can also be damaged. When using such item as ingredient for a recipe, by default, no damage is allowed. For instance:
		+
		+	var pick = <minecraft:stone_pickaxe>;
		+	var iron = <minecraft:iron_ingot>;
		+	// upgrade pick recipe :)
		+	recipes.addRecipe(<minecraft:iron_pickaxe>, [[iron, iron, iron], [null, pick, null]]);
		+
		+	In the recipe above, a damaged pickaxe would not be accepted. This can be changed easily with the .anyDamage() modifier:
		+
		+	var pick = <minecraft:stone_pickaxe>.anyDamage();
		+	var iron = <minecraft:iron_ingot>;
		+	// upgrade pick recipe :)
		+	recipes.addShaped(<minecraft:iron_pickaxe>, [[iron, iron, iron], [null, pick, null]]);

	== Reloading and recipes ==		== Reloading and recipes ==

← Older revision		Revision as of 18:22, 21 June 2014
Line 55:		Line 55:

	Many mod machines, however, do not support such recipe removal. In that case, the recipe will be "stuck" in the game until the entire game is reloaded. For a server, this means that the recipe will be stuck in the list until the server is restarted; for a client, it means that the recipe will be shown and acted upon as if it existed, though when a crafting attempt is made, actual crafting would fail. There is no fix to such behavior; it is up to the respective mod authors to provide a sufficient API to ensure that recipe removal is possible.		Many mod machines, however, do not support such recipe removal. In that case, the recipe will be "stuck" in the game until the entire game is reloaded. For a server, this means that the recipe will be stuck in the list until the server is restarted; for a client, it means that the recipe will be shown and acted upon as if it existed, though when a crafting attempt is made, actual crafting would fail. There is no fix to such behavior; it is up to the respective mod authors to provide a sufficient API to ensure that recipe removal is possible.
		+
		+	== Using variables ==
		+
		+	Do you find yourself looking up the same item over and over again using the bracket syntax? It may be handy to remember the value for later; which can be done with the val and var statements:
		+
		+	val stick = <minecraft:stick>;
		+	val planks = <minecraft:planks:*>;
		+	recipes.remove(stick);
		+	recipes.addShaped(stick * 4, [[planks, null], [null, planks]]);
		+
		+	In this example, var can be used to:
		+
		+	var stick = <minecraft:stick>;
		+	var planks = <minecraft:planks:*>;
		+	recipes.remove(stick);
		+	recipes.addShaped(stick * 4, [[planks, null], [null, planks]]);
		+
		+	The difference between var and val is that a val cannot be modified after it is declared:
		+
		+	val stick = <minecraft:stick>;
		+	stick = <minecraft:bread>; // fails