Cooking in Polylithic
Feed the camp, buff the hunt, and let the recipe generator be weird on purpose.
Cooking is the polite half of Polylithic combat. A well-fed hunter kites. A berry-only hunter becomes a story the bison tell. The 1.0 store text even boasts a recipe system that generates results with “predictably unpredictable” outcomes. This page is the reliable layer under that joke: fires, food jobs, and when to stop experimenting because a raid is walking in.
You need a placed campfire before you need a cuisine identity. Craft it, put it on the hotbar, set it near the hut, and keep twigs or wood in reach. The crafting guide covers placement. This page covers why you bother.
What food is for
Older public notes still match how players talk about food. Berries, picked from bushes, are a speed nibble and a panic snack. Roots, pulled in forests, help stamina recover. Nuts from orange-leaf trees raise the stamina ceiling. Roasted meat from a fire is the damage swing you want before a real fight. Fish, once a pole exists, is the safe protein some launch players called quietly overpowered.
Eat for the next ten minutes, not for a collection. If you are scouting biomes, berries and roots are enough. If you are opening how to hunt, roast something. If you are recruiting, cook extra, because the new mouth will not wait for your tasting menu.
Campfire versus later heat
The campfire cooks meat, handles fish, and produces cinders or ash when you burn wood. Those ashes show up in later recipes, so a fire is also a tiny factory. A stone stove, once unlocked in the building list, behaves like a fire that does not constantly eat logs. Build the stove when the village is stable. Building it before a bed is how you own a kitchen and no save point. See buildings.
Keep one cooking station as the social center. In co-op, four personal fires is how nobody knows where dinner is. The co-op guide makes that a rule for a reason.
The generated recipes
1.0 wants you to experiment. Do it on a full stomach with a bed behind you. A funny recipe that wastes the last meat before a quest hunt is not charming. Park experiments after a successful butcher, when the rack is already working and the pot is not empty. If a generated dish looks like a buff you can name, write it down. If it looks like a dare, feed it to nobody you need alive.
Companions eat too. Dogs and hyenas are not decorative. If the camp is already thin, do not run a tasting flight for a tame. Taming can wait for leftovers.
When cooking is the quest
Some story beats want you to cook, taste, or produce a specific item at a fire. If the quest ignores a roast you definitely made, you have met the 1.0 tick bug. Restart once, try the other fire, then continue. How to complete the story is the stall desk.
Cooking will not fix a bad hunt or a broken villager. It will make the next honest attempt cheaper. Light the fire you already own, roast the meat you already carried, and let the recipe generator perform after the camp is bored of being hungry.
Frequently Asked Questions
Quick answers to the most common questions.
How do I cook meat in Polylithic?
Place a campfire, interact, and roast raw meat from a butcher. Later, a stone stove does the same job with less wood.
What food should I eat before a fight?
Roasted meat for damage. Save berries for travel. Details pair with how to hunt.
Are the random 1.0 recipes safe?
Experiment when you have spare food. Do not gamble the last roast on a generated dare.
Do villagers and tames eat my food?
Yes. Cook extra before you recruit or tame. See how to form a tribe.