#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.
#example8:
#  Result: 256
#  Quantity: 6
#  Materials: {256: 1/127}
#  DataValues: abc
#  Type: Shapeless
#abc74:
#  Result: 256
#  Quantity: 6
#  Materials: {265: 1}
#  Type: Shapeless
#  ResultDamage: 251
#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.
#bla3:
#  Shape:
#  - [3, 3, 3]
#  - [3, 0, 3]
#  - [3, 3, 3]
#  Result: 4
#  Quantity: 8

# Recipes añadidos por Troll ^^
NieveaHielo:
  Shape:
  - [80, 80]
  - [80, 80]
  Result: 79
  Quantity: 1
TierraaHierba:
  Shape:
  - [351/14, 351/14]
  - [351/14, 3]
  Result: 2
  Quantity: 1
TierraaHierba:
  Shape:
  - [351/14, 351/14]
  - [351/14, 3]
  Result: 2
  Quantity: 1
Esponjas:
  Shape:
  - [287, 35, 287]
  - [35, 41, 35]
  - [287, 35, 287]
  Result: 19
  Quantity: 1
TeladeArana:
  Shape:
  - [287, 287, 287]
  - [287, 341, 287]
  - [287, 287, 287]
  Result: 30
  Quantity: 1
SandstoneaArena:
  Shape:
  - [24]
  Result: 12
  Quantity: 1
#Recipes de horno
Manzadeoroabloque:
  Result: 41
  Quantity: 1
  Source: 322
  Type: Furnace

#Another example of a shaped recipe, showing that the recipes don't have to fill in the whole grid.
#hi4:
#  Shape:
#  - [3, 3]
#  - [3, 0]
#  Result: 4
#  Quantity: 5
#  Type: Shaped
#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.
#argh33:
#  Shape:
#  - [351/1]
#  Result: 258
#  Quantity: 1
#  Type: Shaped
#  ResultDamage: 1
#  DataValues: abc
#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.
#abc99:
#  Result: 351
#  ResultData: 3
#  Quantity: 1
#  Source: 351
#  SourceData: 1
#  Type: Furnace
#CREDIT GOES TO FULLWALL, THE AUTHOR OF COOKBOOK!
#Repair recipe. Set the source data value to -1!
#ewqer8:
#  Result: 256
#  Quantity: 1
#  Materials: {256: 1/-1, 265: 1/0}
#  DataValues: abc
#  Type: Shapeless