Recipes | Premade Recipes |
Tutorial | Beginner level tutorial on cooking |
BaseEffects | Ingredient stats |
Timer Length | Detailed description of how duration is calculated (shortcut to the Table) |
Bases | Premade Bases (old style recipes) |
BaseLayers | Single Layer Bases (new style) |
Ingredient Order | Bible of New Style Cooking |
Cordon Bleu | Base designer/duration prediction | Kinniken |
Cooking Thing (direct link) | Web-based recipe designer/duration predictor (no installing needed) | Sullivan (backend), Alya (web frontend) |
Cooking Assistant | Genetic algorithm base generator | Gada |
Herb Stats Tool | Herb stats database | Chichis |
The higher your skill level in Cooking, the greater the stats you get from meals (Specific data on scaling needed). It is generally advised against making herb-expensive meals until you have the highest Cooking level available.
If you have a Gastronomy skill of 7 or higher, you can critically evaluate the dish - this uses no servings, but tells you the stats it would give if eaten and how long it would last.
Stats from each ingredient seem to be combined nonlinearly according to the amount of the ingredient versus the total size of the recipe. In practice, it is very hard or impossible to accurately calculate the stats of a recipe due to the strengths of ingredients changing constantly - an approximation of weak/medium/strong is about as good as we can do.
Recipe duration is very well understood, but requires a lot of data collection to get useful recipes (mostly done now by the Cooking Research Coordination guild). Duration depends on interactions between adjacent pairs of ingredients in a recipe. To illustrate how duration is calculated, we'll use an example recipe of: 2 perch fish, 3 carrots, 2 cabbage, 1 thyme and 1 bull's blood. The following steps occur:
Without going into the details, the duration changes of each combination are weighted by the highest quantity in the recipe (in the example above, 3) - this means that the effects of interactions of the lower quantities are reduced in comparison to those in the top end of the recipe. This is good if you have a lot of unknown interactions (normally expensive and untested herbs) and want to drown them out with strong positive interactions at the top end (the base + additives method, see below), but if you know the interactions and design the recipe to take advantage of them, it's better to have a single layer recipe (all the same quantities with interactions determined only by the sort order).
Calculating duration by hand is slow - use the cooking tools.
Many people won't be interested in designing their own recipes, though this is the best way to make use of the ingredients you have, so for those people just wanting proven recipes, see the recipes page. The rest of this section gives a brief description of how to design recipes. Those with an interest in cooking/food research may want to apply to the Cooking Research Coordination guild.
When designing a recipe to change stats, there are two methods. The first and older method is to use basic ingredients, common mushrooms, and common herbs in larger quantities to make the base (boosts duration), then use small quantities of many types of herbs as additives (boosts stats). This method was used mainly when many duration interactions between ingredients were unknown and needed isolating. It is also useful for very large numbers of servings. However, it is somewhat inefficient due to the way duration is calculated and non-optimal for stats.
The modern method, made possible by much more data on duration interactions, is to use single-layer recipes (or stacked layers if you need very high stats/higher numbers of servings) - a layer has a set of ingredients, all at the same quantity (e.g. 1 db of each), that all interact to add to duration and are positive (or neutral) for the stats required. This gives optimal duration (having all ingredients in the same quantity avoids a divisor in the duration calculation - see duration above) and maximises the stats (since there aren't large numbers of negative or neutral components from 'base' ingredients). Most of the modern recipes use layers. Some more information, examples and an explanation of how to stack layers can be found at BaseLayers
There is a couple tools which have been programmed to help automate the task of coming up with good bases. The first is Cordon Bleu created by Kinniken, which allows you to add ingredients in various amounts and predicts the duration of the recipe. The second is Cooking Assistant by Gada which uses a genetic algorithm to generate high duration bases automatically. Using one or both of these programs to come up with bases is recommended.
An ongoing research effort to fill in data describing the reactions between every ingredient continues so that we may make better predictions on recipe durations and make longer lasting recipes.
If you don't want to come up with your own bases, you can use predesigned bases from Bases.