Troubleshooting Custom Crops That Don't Appear In-Game

Check the File Location and Name

The most common cause is a misplaced or misnamed file. Crop JSONs must sit directly in config/mysticalcustomization/crops/, not in a subfolder. The filename (minus .json) becomes the crop's ID, so it must be lowercase with no spaces. If you edited a file but the crop still shows the old behavior, you may have edited a copy in the wrong directory.

Validate the JSON Syntax

A single missing comma or trailing comma breaks the whole file, and the mod will skip it. Paste the contents into a JSON validator. Then check your game log — Mystical Customization logs a parse error naming the offending file when it fails to load. Fix the syntax, save, and run /reload.

Verify References Resolve

Crops point at a tier and a type by name. If either name does not match an existing tier or type file exactly (including capitalization), the crop fails to register. Confirm every referenced name exists. Also confirm any item IDs you used are correct registry names — an unknown item ID will cause the recipe or drop to be dropped silently. After fixing references, reload and search JEI for your crop's seed and essence to confirm it loaded.