CreateTweaker Mod FAQ

CreateTweaker doesn't add items or blocks itself — it exposes Create's machines to CraftTweaker scripts. Create a .zs file in your scripts folder and use the CreateTweaker recipe methods inside it, then reload with /ct reload or restart the game.

CraftTweaker handles vanilla and generic mod recipes, while CreateTweaker adds the specific recipe types Create uses, like mixing, crushing, pressing, compacting, and sawing. You need both installed for CreateTweaker scripts to work.

The most common causes are a missing CraftTweaker install, the script being in the wrong folder, or a syntax error that silently fails. Check the CraftTweaker log for parse errors and confirm your file ends in .zs inside the scripts directory.

Use the removeByOutput or removeRecipe methods on the relevant Create recipe type, passing the item you want to stop being produced. Reload scripts afterward and confirm the recipe no longer appears in JEI.

Yes — Create's mixing recipe type supports a heated flag, so you can specify whether the basin needs a blaze burner underneath. Set that parameter in your mixing recipe call to match the behavior you want.

Create's crushing recipe accepts a list of output stacks, each with its own chance value, so you can have a guaranteed main output plus a lower-chance secondary. Define each output with its item and probability in the recipe call.

Generally yes, since it registers its own recipe types through CraftTweaker's API. Conflicts are rare but can happen if two addons try to modify the same Create recipe — remove one of the conflicting scripts if you see odd behavior.

Create's pressing and compacting recipes use a processing duration value that you can set in the recipe definition. Lower values make the machine finish faster; higher values slow it down.

Scripts are parsed once at load time, so runtime performance impact is negligible. Very large script files can slow down game startup or /ct reload, so keep scripts organized and avoid unnecessary recipe removals.

Usually you can just run /ct reload to reapply scripts without restarting. Some recipe changes may not fully refresh in already-loaded chunks, so a full restart is the safest option if something looks off.