Lychee Mod FAQ

Create a datapack and add a JSON file under data/ /lychee/ with a type field matching the interaction you want, such as block_clicking or item_inside_block. Lychee reads these files on world load, so /reload applies changes without restarting.

They live in data/ /lychee/ / .json, where the folder matches the interaction type (for example block_clicking, anvil_crafting, or falling_block). The namespace and file name become the recipe's ID, so keep them lowercase and unique.

The most common causes are a malformed JSON file (check your log for a parse error), a wrong type value, or the datapack not being enabled for the world. Run /reload and watch the log — Lychee reports broken recipes there instead of silently ignoring them.

You specify the block, the item held, and whether the trigger is a right-click (use) or a left-click (click) in the recipe's conditions. If the item or block doesn't match exactly, the interaction won't run.

Yes — most interaction types accept an item condition, so the action only triggers when the player holds the matching item. You can also combine it with block conditions to narrow things down further.

In your anvil_crafting JSON, define the input item and the resulting output, and Lychee handles the anvil interaction for you. Whether the input is consumed depends on the recipe's settings, so check the fields available for that type rather than assuming vanilla behavior.

Item_inside_block triggers while an item entity sits inside a specified block like water, while item_burning triggers when an item entity is on fire. Both let you define a resulting action, such as transforming the item or spawning something new.

Yes — the result section of a recipe can spawn items, run a command, or apply other effects depending on the interaction type. This is how you turn a simple trigger into a full custom mechanic.

Lychee uses its own lychee folder and doesn't overwrite vanilla recipes, so it generally coexists with other datapack mods. Conflicts only arise if two packs define the same recipe ID, so use a unique namespace.

Lychee recipes are loaded once and checked as events happen, so a reasonable number won't noticeably affect tick rate. Very large numbers of block_clicking or item_inside_block checks can add up, so keep conditions specific rather than broad.