Recipes only use the circuits as they are registered in the oredict. If you disable circuit oredict registration in the config, the recipes won't work if no circuits are registered at all - then they display fire instead of the circuits.

I think that config option is a bit of a throwback - @aidancbrady, shall we remove it, now our circuits are properly tiered?

I think the main reason people set 'B:ControlCircuitOreDict=' to false is because they don't want the Mekanism circuits to interfere with IC2's progression. Unfortunately this actually breaks Mekanism's progression by requiring IC2 circuits instead of Mekanism's own circuits, not to mention the missing recipes.

On the other hand, with this enabled, it almost completely circumvents IC2's whole rubber gathering mechanics by allowing you to use the easier to make Mekanism circuits in all IC2 recipes.

Maybe you guys should use different oredict entries for your circuits than the ones IC2 uses. Then maybe the config option could be changed to register your circuits to be usable in IC2 & allow your machines to take the IC2 circuits.

I know you have these things registered the same as IC2 for extra compatibility, but I feel like it just breaks things.

Removed the config because it's silly. Circuits are more balanced now so shouldn't be an issue.