Using CreativeCore's Enhanced Vanilla Recipes and Recipe System (For Pack Authors and Tinkerers)

CreativeCore ships a recipe system plus an "enhanced vanilla recipe" layer. This is what lets dependent mods add shaped/shapeless recipes that behave slightly differently from vanilla — for example recipes that accept grouped item variants rather than one exact item.

Where recipes live

1. Recipes added through CreativeCore's system are still JSON recipe files, placed in the same data/<namespace>/recipes/ structure you already know.

2. The difference is the recipe *type* declared inside the JSON. CreativeCore registers its own types that its dependents reference.

3. If you are writing a datapack, copy the recipe type string exactly from an existing recipe shipped by a CreativeCore-dependent mod. Do not guess the type name — an unknown type silently fails to load and the recipe simply will not appear.

InfoStack grouping

CreativeCore's InfoStack objects are how the mod treats a *group* of itemstacks as one unit. This is why some CreativeCore-based recipes can accept, say, any variant of a family of items without you listing every single one.

Debugging a recipe that will not load

• Check the log for a recipe parse error naming the file.
• Confirm the type field matches a registered CreativeCore recipe type.
• Confirm every ingredient references an item that actually exists in your pack.
• Reload with /reload after editing; a malformed recipe is skipped, not crashed on, so it fails quietly.