On the forge version, Terrain Control has a bug with the resource queue. After opening a world for the second time, TC adds an extra ":0" to the block source in biome config. After the third time, It gives an error and stops generating resources (that require block sources) in ungenerated chunks. This problem occurs in every biome config file.

Here's an example of the bugged resource:

1st opening world: Ore(DIRT:0,33,10,100.0,0,256,STONE:0)
2nd time opening world: Ore(DIRT:0,33,10,100.0,0,256,STONE:0:0)
3rd time opening world: ## INVALID ORE - Unknown material: STONE:0:0 ## Ore(DIRT:0,33,10,100.0,0,256,STONE:0:0)

I am using the recommended version of forge 1.8 (11.14.3.1450), this also happens on other versions of forge.

This problem occurs in TC 2.7.0, 2.7.1, and the latest 2.7.2 snapshot (build 91)

How to Reproduce bug
*install forge client (not server)
*install terrain control 2.7.1 or 2.7.2 snapshot
*create a new world with world type: terrain control
*open/close world twice
*check any biome config under resource queue
*notice how block sources has an extra ":0"
*if you open the world again, "## INVALID ORE - Unknown material" will appear and ungenerated chunks will not generate resources (that require block sources) anymore

Here is a thread in the forum with the same problem: http://forum.mctcp.com/t/1-8-bug-with-resources-forge/297/2