OreRegistry

OreRegistry.json

This is for Registering the different chunks, pieces, dusts and ingots.

Syntax

The syntax is one large Array (Therefore enclosed by [ ... ]) followed by many comma separated blocks ({...}) for the different ores.

Example:

[
  {
    "name": "gold",
    "color": "ffff00",
    "result": "minecraft:gold_ingot:0",
    "oredictName": "TotalyNotGold",
    "translations": {
      "de_de": "THISISGOLD!",
      "zh_cn": "金"
    }
  },
  {
    "name": "iron",
    "color": {
      "r": 0.7490196,
      "g": 0.5019608,
      "b": 0.2509804,
      "a": 1.0
    },
    "result": {
      "name": "minecraft:iron_ingot",
      "meta": 0
    }
  }
]

Explation:

• "name": "NAME":
  The registry name the item will get

• "color": "hexcolor":
  The rgb color the item will have, in this context alpha is irrelevant

  1. The color can be provided in three ways, either as hexString like in html "color": "bf8040"
  2. As decimal integer color: (Not recommended)
     "color": 16777215 (for white)
  3. As rgba Object:

  "color": {
      "r": 0.7490196,
      "g": 0.5019608,
      "b": 0.2509804,
      "a": 1.0
  }

• "result": "modid:item:meta": (Optional)
  The ingot that is attached to the Ore, if none is provided the mod will create a ingot on it's own Again, there are two ways of defining it:

  1. String representing itemname and meta:
     "result": "tconstruct:ingots:1"
  2. Object with itemname and meta:

    "result": {
      "name": "minecraft:iron_ingot",
      "meta": 0
    }

• "oredictName": "ORENAME": (Optional)
  The oreDict name the Item will get, this is appended to the Base Names configured in the main config, will use Registry name if not provided

• "translations": { "lang_key": "translation", ...}: (Optional)
  A Map of different translations for different languages, will use Registry name if not provided