Recipes for disks and printout contain hardcoded static items, that can't be replaced. In case of modpacks/servers wanting to tweak their recipes to be more inline with other mods it prevents from doing so (only having the impostor recipes, which changing is useless).

Solution:

• Unhardcode things such as redstone/paper/string/leather from recipes and move them to custom serializer json.
• Use custom cc-specific tags with default values pointing to current requirements

I have changed printed pages in ad70e2a.

I want to have a bit more of a think about disk drives. Ideally we'd just be able to expose these as a shapeless recipe, but I'm not sure what to do about the impostor recipes. I don't want to design a system where the impostor recipes are out-of-sync with the "actual" crafting recipe, but the only options I can see are generating the impostor recipes at runtime (a lot of extra code for something quite niche), or just removing them (loathe to do, as they're important for recipe book support).