#Each recipe has a unique id.

#Lets have a look at a shapeless recipe.
#8:  <-this is the unique ID.
#  Result: 3  <-the ID of the result.
#  Quantity: 6  <-the quantity of the result.
#  Materials: {2: 3, 6: 2}  <-Starting materials, format: "id: quantity".
#  Type: Shapeless  <-Define the type
#For data values in materials, add a DataValues node (value doesn't matter) and use the following syntax:
#{id: quantity/data, id: quantity/data...}
#To addd result data:
# Add ResultData node, set it to the needed value.
#To add result damage:
# Add ResultDamage node, set it to the needed value.
#Now a shaped recipe
#3:  <-this is the unique ID.
#  Shape:  <-do not touch this, it is a keyword.
#  - [3, 3, 3]  <-First row of the crafting grid.
#  - [3, 0, 3]  <-Second row of the crafting grid. Note that you can use 0s for free space.
#  - [3, 3, 3]  <-Third row of the crafting grid.
#  Result: 4  <-result ID
#  Quantity: 8  <-quantity of the result
#Note that by default, if no type is defined, the plugin will think that the recipe is shaped.
string:
  Shape:
  - [0, 0, 0]
  - [264, 289, 0]
  - [0, 0, 0]
  Result: 287
  Quantity: 4
Arrow:
  Shape:
  - [0, 0, 0]
  - [289, 289, 289]
  - [0, 0, 0]
  Result: 262
  Quantity: 20
seeds:
  Shape:
  - [265, 0, 265]
  - [0, 0, 0]
  - [0, 265, 0]
  Result: 295
  Quantity: 4
leather:
  Shape:
  - [4, 4, 4]
  - [4, 265, 4]
  - [4, 4, 4]
  Result: 334
  Quantity: 2
egg:
  Shape:
  - [4, 4, 4]
  - [4, 264, 4]
  - [4, 4, 4]
  Result: 344
  Quantity: 4
bow:
  Shape:
  - [265, 289, 0]
  - [0, 0, 0]
  - [0, 0, 0]
  Result: 261
  Quantity: 1
dagger:
  Shape:
  - [0, 289, 0]
  - [0, 289, 0]
  - [0, 334, 0]
  Result: 291
  Quantity: 1
blade:
  Shape:
  - [0, 289, 0]
  - [0, 289, 0]
  - [0, 266, 0]
  Result: 294
  Quantity: 1
gunpowder:
  Shape:
  - [4, 12, 4]
  - [4, 12, 4]
  - [4, 12, 4]
  Result: 289
  Quantity: 1
glowstone:
  Shape:
  - [20, 20, 20]
  - [20, 50, 20]
  - [20, 20, 20]
  Result: 89
  Quantity: 1
Nether:
  Shape:
  - [4, 4, 4]
  - [4, 263, 4]
  - [4, 4, 4]
  Result: 87
  Quantity: 1
Pumpkin:
  Shape:
  - [265, 265, 265]
  - [266, 0, 266]
  - [0, 0, 0]
  Result: 86
  Quantity: 1
Beer:
  Shape:
  - [20, 326, 20]
  - [20, 296, 20]
  - [20, 296, 20]
  Result: 335
  Quantity: 1
Bones:
  Shape:
  - [20, 4, 20]
  - [4, 289, 4]
  - [20, 4, 20]
  Result: 352
  Quantity: 3
ink:
  Shape:
  - [87, 289, 87]
  - [87, 289, 87]
  - [87, 87, 87]
  Result: 351/0
  Quantity: 12
Greydye:
  Shape:
  - [87, 289, 87]
  - [87, 87, 87]
  - [87, 87, 87]
  Result: 351/8
  Quantity: 12
#Another example of a shaped recipe, showing that the recipes don't have to fill in the whole grid.
#Example of data values in shaped recipes.
#The DataValues node's value doesn't matter - what matters is that it is there.
#It is needed if data values are involved in the recipe.
#Syntax:
# - [id/data, id/data...]
# - [id/data, id/data...]
# - [id/data, id/data...]
#If the item has no data values, use 0. e.g. [3/0, 3/0, 1/0]
#To add result data:
# Add ResultData node, set it to the needed value.
#To add result damage:
# Add ResultDamage node, set it to the needed value.
#A furnace recipe.
#99:
#  Result: 264  <-result ID
#  Quantity: 1  <-quantity of the result
#  Source: 263  <-the ID of the material to be smelted
#  Type: Furnace <-type definition
#For result data use the ResultData node (optional).
#For result damage use the ResultDamage node (optional).
#For now, source data is broken.
#CREDIT GOES TO FULLWALL, THE AUTHOR OF COOKBOOK!
#Repair recipe. Set the source data value to -1!