Data tags
Epicurean is majorly data-driven. There a few important tags to keep in mind when designing packs.
Each flavor (Spicy, Umami, Acidic, Sweet, Bitter, and Filling) has its own tag at epicurean:<flavor>. These are the main tags for specifying what effect an ingredient will add to a meal. In order of prominence (the highest-prominence flavor in a meal will give the main effect):
- Spicy gives Resistance
- Umami gives Saturation
- Acidic gives Fire Resistance
- Sweet gives Speed
- Bitter gives Haste
- Filling gives Absorption
Each ingredient can only be in one flavor tag. Due to the current logic, if an ingredient is in multiple flavor tags, it will be assigned the flavor that is least prominent of the tags it is in.
The epicurean:dressings tag decides whether a given ingredient is counted as a Dressing or not. Dressings add extra effects on top of the prominence effect, and can be added to meal after the meal is already crafted. If an ingredient is in the Dressings tag, it is counted as a dressing; otherwise it's not. All dressings must be assigned a flavor; if an item is in the dressings tag but no flavor tag, it will not be registered as a dressing.
There currently aren't really any good foods that would count as greens in Minecraft. Because of that, I've decided to add, by default, Dandelions (since dandelion greens are edible) and small Ferns (since various types of ferns are edible) as greens. Greens are by default registered as bitter dressings.