Hello Mr. Modular Machinery Developer!

I am working on a brand new modpack and was wondering if you would consider adding some cool CraftTweaker support. The reason I am making this request from you is that I feel it would let me use the power of CraftTweaker with the amazingness of your mod.

by the way, this would be for minecraft 1.12.2!

I would very much appreciate your consideration! Thank you and have a wonderful rest of your evening!
Darkcostco

CraftTweaker provides an approach that JSON does not. I cannot do loops, or use variables and other methods that CraftTweaker provides. In a large modpack, the more that CraftTweaker works with the better, because otherwise you run into constant inconsistencies as mods change and break names, etc.

We're already using a mix of configs and CraftTweaker and probably some JSON to do recipes and other things that require specifying an item, which has already caused issues, where CraftTweaker scripts have been far more resilient. Its one thing if I'm making the machine in JSON, its a whole other thing when I have to create all the recipes I want to use in the machines in JSON.

As a quick and easy example.. ContentTweaker adds new part items, but those Id's can be 'lost'. Think of this like back in the day when IDs were not set, and if that ID file that stored what Item was what Id, the entire modpack was broken. The safest way to use them is by using its bracket handler system, but that cannot be used outside the CraftTweaker "ecosystem".

@justinrusso
Why do you need CraftTweaker support? This mod already has it's own recipe system for it's machines.
It works simple: you just create machine via JSON file (see wiki) and just add all recipes for this machine also in JSON format.
CraftTweaker support there's senseless and useless, because this mod uses different approach for recipe system.

If you really want CraftTweaker support for this mod, please, explain why (and for which parts of mod).

I agree that some more collaboration between the two mods would be infinitely useful, although I'd probably recommend suggesting specific integrations.

Issue #54 is a very limited step forwards: If MM can nest variables and/or use variables in arrays for MM machine json recipes, then I can at the very least specify my CoT IDs in a single central place, so that when they (inevitably) get lost during development, I can simply reassign them in the one place rather than crawling through numerous files.