In reply to stillg0ld:

 "material" needs to be an array of materials if there is more than one material. For example:

				"material": [
					"minecraft:netherrack",
					"netherex:fiery_netherrack",
					"netherex:gloomy_netherrack",
					"netherex:icy_netherrack",
					"netherex:lively_netherrack"
				],

 It is also a good idea to add "netherex" as a dependency and because there is now more than one mod as a dependency, it needs to be an array of forge mod entries:

	"dependencies": [
		{
			"id": "netherendingores"
		},
		{
			"id": "netherex"
		}
	],

 Here is an example of the netherending ores generating within netherex netherrack variants. Please do note that obviously the textures wont match, that is an entirely different kettle of fish requiring a whole addon mod and my hands are full with the 1.4 mod release coding.

 I have actually done all the work for you, please see the test release here: https://github.com/ICannt/Netherending-Ores-Configs/releases

 Please bear the following in mind:

1. The included files are designed for the unreleased 1.4 mod version, only install ore files you want to use. This includes the project red and aether ores.
2. The quartz ore file is probably not needed as netherex seems to have its own quartz variants anyway. Also should only be used if you are using the vanilla replacer files.
3. Only install the glowing clathrate file if thermal expansion is installed and you have using the replacer files

In reply to Velocihater:

A couple of reasons

1) cofhworld is much better built and flexible than a basic worldgen function that I would otherwise code myself.

2) It would be possible to include the ore gen files in the distribution but then they are more difficult to override if you don't like what I pick for default settings and more difficult to disable/enable individual ores.

3) The more serious modpack makers like to customise their pack setup anyway. FTB Ultimate Reloaded doesn't even use my ore gen files at all, they made their own.

In reply to daniel3101:

 You need to install the configuration files. There is a link above in the ore generation description.

In reply to somenerdium:

 Smelting direct is not the ideal way to deal with it and is mainly there for compatibility as required. If you really want direct smelting then change the recipe multiplier to 1 for the ores required or use the override to change all ores to 1. I could look at smelting to more than 1 ingot instead as an alternative but it won't be the same ultimate output as grinding first is and won't be the default option.

In reply to somenerdium:

If the recipe multiplier is set to 1x the metallic ores behave much the same as their overworld counterparts and would smelt direct to items. Mineral ores usually would drop items on breaking and some xp, which is not currently supported. I am looking at doing this for the 1.4 release that I am working on.

In reply to haddocka:

There are 2 ways to stop this from happening.

1) Disable Vanilla crafting recipes

    # Enable crafting recipes to convert to oredict ores, only works with 1x recipe multiplier [default: true]
    B:"Vanilla crafting recipes"=false

2) Set the recipe multiplier mode to 0 for the ores in question

    I:"End Ardite Ore"=0
    I:"End Cobalt Ore"=0
    I:"Overworld Ardite Ore"=0
    I:"Overworld Cobalt Ore"=0

At long last new config files are available. :)

Please check the downloads page for the configs here.

Be sure to read the included readme file on how to install them.

In reply to MIckMcCaff04:

 One day perhaps. I want to finish what I started wit the 1.4 update first before I even consider it.

In reply to dragonhero68:

 Add a json file to do it.

Like this:

{
	"dependencies": "netherendingores",
	"populate": {
		"nether-certus-quartz": {
			"distribution": "uniform",
			"generator": {
				"block": {
					"name": "netherendingores:ore_nether_modded_1",
					"metadata": 9
				},
				"material": "minecraft:netherrack",
				"cluster-size": 8
			},
			"cluster-count": 3,
			"min-height": 10,
			"max-height": 118,
			"retrogen": "true",
			"biome": "all",
			"dimension": {
				"restriction": "whitelist",
				"value": [
					-1
				]
			}
		}
	}
}

In reply to dragonhero68:

 It is now included in the new config file update