Also, how the hell is TE so poorly designed that it registers oredict entries but does not use them?! And how is that not all automatic by design?!
Well you see, I have an item class - https://github.com/CoFH/CoFHCo…h/core/item/ItemBase.java
And it's a very trivial matter to register something as an OreDictionary item, so I do it out of habit.
However, there are these things in Minecraft called recipes. They're registered with the recipe manager. You can give them Itemstacks, or OreDict names, if you use the Forge thing. It's not automatic, you have to code the recipes in.
It's not a design issue, don't be stupid. You are better than that OM, or at least you're supposed to be. There's no fundamental "bad design" at work here, it's simply not using the OreDict recipe handler on things where it only adds to the overhead and lag to use them - i.e., there's only 1 Pyrotheum Dust, there's no point to not directly reference the version in Thermal Foundation.
If anything, the oversight was doing a registration in the first place, as there is no reason whatsoever for Greg to add Pyrotheum. Seriously man, if you like the mats, just have some crossmod compat.